Post a Comment
So use a toolkit like Dojo to abstract out the IE vs. Rest-Of-The-World issues.
IMO one of javascripts big problem is its name. Its called java, it looks like java, but it is a dynamic, not a strongly typed language. If you treat it as a strongly typed language, it is going to be hell to work with. If you treat it as a dynamic language, it is actually incredibly powerful and expressive.
I also think that it doesn't help that Javascript is often used for tasks that are better-suited to server-side scripting languages. If I just need to run a search-replace on a text string, or truncate a string to a specific number of characters, I'll use Javascript (of course, if users need to be able to dynamically expand/collapse the truncated string without a page reload, then I'll use JS).
http://280slides.com/
http://www.sproutcore.com/
We are seeing some seriously impressive stuff being done on the front end. sproutcore actually has a data layer that can hook into either stuff like google gears, or a web service for persistence.
I agree with the comments about using a compatibility library to smooth the differences between the browsers, personally I use Prototype, but others mentioned are at least as good.
There's so much more to javascript, though. Take property getters and setters as an example:
http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Guide:Crea...
Really, really cool stuff, contrast this to exploder, where they haven't even bothered to implement constants! (i.e. the const keyword - in IE6 at least)




