4 ms·
State of ECMAScript 4
"I think it's fascinating to note that there's 3 implementations that already have over 25% of all the new features in the language implemented." -John Resig
- tlrobinson 19y ago1) The spec isn't even finished, and won't be for about a year. 2) Once the spec is finished, it will be years before browsers fully implement it and it's widely deployed. Do we really need this? I think the focus should be on making current browser JS implementations a) less buggy (i.e. IE's ridiculous memory leaks) and b) faster. That would at least help all the existing JavaScript applications and users of such applications, right now.
- michaelneale 19y agoWhat about ECMAScript beyond the browser? ie server side?
- tlrobinson 19y agoPerhaps... a few people are already doing it (Steve Yegge's alleged "Rhino on Rails", AppJet, and I'm sure others), but there's no overwhelming de-facto standard that I know of. Anyone know of any good server-side JS frameworks?
- michaelneale 19y agohttp://helma.org/ http://helma.org/ is one.
- axod 19y agoI'd say IE is pretty much a lost cause. I doubt it'll be years before it's implemented/deployed. As you see a lot of it is supported already and it's not even finalized. I think that's pretty good going. IE users are always going to have a massive disconnect with the current innovations and technologies, I think the best thing to do is to make them fully aware of what they are missing out on.