They came, they saw, they shot and what do we do now???

Well they came by sea and this has been confirmed by Govt. of India. They killed 100s and I strongly believe that the number given by Govt of Indiais highly deflated one. Great bloggers like Nitin Pai and GreatBong have written at lengths about this carnage(I am sorry for those who call it tragedy). It was nothing more that cold blooded massacre of people in India. The suggestion and thoughts by both these bloggers have been bang on target. But then, this stupid Congress government is not expected to be able to achieve anything.

So here are my suggestions(well when everyone has one, why should I not chip in)

There are three ways to deal with the situation.

1. Pseudo-Gandhian way -- Take out rally and protest creating havoc for the people who are already suffering at the hands of the government. The candle lights protest as well as going at lengths of giving memorandum to the political brasses all fall in this category. I hail from the city known of late more for protests than anything else and I strongly believe that this hardly rings bells for anything good. Its the tool of the political opportunists. This is definitely going to be the favored mode of protest for most people. A fine example is of a person who was searching for media contact after a gruesome rape of his/her friend's maid.

2. Gandhigiri way -- These guys will follow something like this, send a bouquet and a condolence  card to Mr Rahul Gandhi, regretting the death of her mother Mrs Sonia Gandhi during the terror attack. Probably if sent in millions it will open the eyes of the Congress loyalists who only care about money and Gandhi family.

3. Gandhi way -- What Mahatma Gandhi would have had done probably is that he would have had marched with all his followers to the terror camps and the LeT offices. Next thing to be done would be to ask them to kill them right away, if he had guts.

I dont know what to do frankly. But if I am sure of anything, its that the Pseudo Gandhi way is not the way forward. There has to be another way to wake up this sleeping government. I am not sure which of the Indian would be able to rise up to the challenge and come up with the perfect answer.

BTW I am still pondering over any kind of fatwa being issued in this regard.

End of all rants about 26/11

Comments

Anonymous said…
Give it back...
December 18, 2008 12:46 AM
100rabh™ said…
what is that supposed to mean???
December 19, 2008 1:31 AM
franknose said…
Its calle BS...
January 25, 2009 8:58 PM
Post a Comment

Popular posts from this blog

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more

[15th December 2024] Interesting Things I Learnt This Week

Image
1. Why you should never use !! in Kotlin - Using double-bang operator(!!) is a bad practice; multiple alternatives cover every other possible case. Using it is a hack and a shortcut that will backfire while not saving you much time at the time of writing using it. You shouldn’t use it unless you're writing a short personal script. My Take : The double-bang operator (!!)  which throws null pointer exception in Kotlin might very well be considered " Billion Dollar Mistake ." While it offers a concise way to assert that a variable is not null, I believe it's preferable to have slightly more verbose code that explicitly handles nullability and avoids potential runtime exceptions. Null pointer exceptions have plagued programmers for decades, and introducing a feature that can easily lead to them seems counterproductive. I'm uncertain whether all Kotlin linters currently check for excessive or inappropriate use of the !! operator, but if yours don't, I strongly re...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more