Skip to main content

Post Cease-Fire: Who won?

So the 3 week war is over (or at least there's a timeout) and the question people are asking is "who won: Hezbollah or Isreal"? Depends on who ask. Hezbollah seems to think they've won and if you look at their reasoning you can't exactly disagree outright with them. Sure Lebanon got shelled to smithereens but Hezbollah won the PR war by a huge margin. They now have way more converts and sympathizers. And all Isreal has done is made a great show of force, pushed into parts of Lebanon and are now retreating (sure their tails aren't between their legs but they are hardly victors).

On the other hand, Bush and Isreal seem to think Isreal has won. As Bush, in his most diplomatic way, puts it: how can Hezbollah claim victory when it used to be a state within a state and now will be replaced by a UN force?

Personally, I think it's more of a question of who lost, not who won. The hundreds of Lebanese and Isreali civilians killed are the losers. The Lebanese state, who will have to repair dozens of civil infrastructure destroyed by Isreal, also lost. And Bush also lost. He might not realize it now but unless he turns things around dramatically in the middle east, his presidency will be remembered as one that brought the most strife to the middle east.

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply