May 092006

I’m mostly finished with my first rough-cut draft of a document outlining the new features in JavaScript 1.7. Once I get responses to a couple of emailed questions, I hope to wrap it up and send copies to select people so they can point out that it’s all wrong and that I need to rewrite most of it.

This tends to happen a lot when documenting brand new technologies. Existing proposal and spec documents tend to be out of date by the time the technology is actually implemented, leaving the technical writer in the position of making educated guesses and then letting the engineers point out how it’s all wrong.

All in a day’s work.

Fortunately, in this case, the guys know good and well that the specs and proposals are out of date and are ready for this. That makes life easier.

Still duking it out with the cable company over my cable connection. My little app indicated several outages overnight, but at the moment, it’s been online since around 6:30 AM. However, packet loss is starting to climb again and is now at around 50%, so I expect the connection to fail sometime in the next 30-60 minutes.

Good times.

 Posted by at 11:41 AM

  6 Responses to “JavaScript 1.7”

  1. there is a way to participate for the wishes-list ? What will be include in this new version ?

  2. To be honest, I’m so new at Mozilla I don’t know how to propose features or changes to JavaScript.

    The new features haven’t been fully set in stone just yet, so I hesitate to spout off too much until I get my draft document read over by all the right people. Until then, I’d just be shooting my mouth off. :)

  3. OK, I understand.
    Just a last question. Did you envisage a function to import JavaScript files automatically (like @import in CSS) and (but that would be more complicated) a manner of precompiling the Javascript files so that they are less heavy and that the navigator spends less time to execute the code?

  4. Well, I’m just writing about this stuff — I’m not designing it. :)

    Precompiling the JavaScript files sounds more like a runtime engine implementation issue than an actual language syntax issue though.

  5. Will this draft also be available to the public?

  6. Yes, it will be soon. I’d like to get it reviewed once by the guys in the know first though. It’s based on my reading through a lot of discussions about syntax, and odds are good that some of it is woefully inaccurate. No point inflicting that on people.