Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:Um... (Score 1) 277

I switched long ago. Flex was just an personal exploratory activity, not a long term commitment. Sure, I thought about buying it a promise ring, but backed out before I was in too deep. All joking aside, I was pleasantly surprised with the environment built around Flex, and thought that it was much superior to the applet. Why Adobe thought developers would pay for the right to build application effectively on it through FlexBuilder licenses is a New Coke type of decision.

GWT may be great, but Google is too fickle in it's long term support of anything. If I build a significant application around a technology, I want something with longevity. No offense but I hesitate to plug into anything Google for this reason. Just yesterday it seems that Google Wave was going to overtake the world -- and it was cool actually. I'm actually surprised they didn't continue to back it in the form of android or HTML5 technologies aimed at mobile devices and tablets.

Comment Re:Yay. (Score 1) 277

I once designed a database which used small business acronyms to associate lines of business with their associated profiles. It grew to support 40 million or so customers give or take. Marketing, acquisitions, more marketing has renamed each entity an average of 5 times over the last 15 years. Being a young programmer at the time, I lacked the experience to foresee the amount of corporate churn. It's a mess :-) and we're all idiots and clever at some time or other.

Comment Re:Um... (Score 1) 277

Despite the demise or imminent demise of Flex. It did have a superb integrated debugging environment that I have yet to find in the Javascript world. Firebug, however, is getting there but I still find it clunky compared to the other integrated IDEs I have worked with in the past.

The trouble with doing something right the first time is that nobody appreciates how difficult it was.