1. If using new frameworks to create classes instead of the usual prototype BS, you will thoroughly disappointed that you will have no compile time checking.
2. Thus if you have an error in your class you will never know until you run the app.
3. console.log doesnt work in IE 8.
Thus from my deduction the only logical approach to this is the fact that you must use prototype to create your classes and not rely on strong typing.
Even then, if you use prototype to create a class AND then use another class within that class all compile time checking goes out the window.
This slows development time down tremendously and is the primary reason I think developers like Google are going with alternate solutions like Dart.
I really think Adobe should have waited for the announcement. I think Adobe should have made the announcement WHEN they had a solution. It makes developers now flounder as a whole. You dont announce the big issue when you have no alternative.
Can you get the error detection as awesome as flex builder?
The amount of millions of dollars wasted in no compile time checking is at stake here and I think that managers need to know the alternatives to development.
Just look at this article about js 1.8 whereby instead of implementing ECMAScript 4 enhancements that include packages, namespaces, classes. They implement CLOSURES – shorthand code for methods that make code a lot more unreadable.
I think it’s a backwards move and I think Google sees this too which is why Google Dart is being developed.