Despite the lack of a beard, Anders Hejlsberg is a guy you should respect – he came up with two of my favorites, Turbo Pascal and C#. But while the language looks great – as an ActionScript programmer, it’s easy to love it – I see two issues with this approach.
Second, and maybe more importantly, this is Microsoft, and I can’t help but seeing them taking the language to the direction they want (even though it’s an “open standard”) rather than bringing them closer to ECMAScript 6, or following it strictly (
they don’t actually mention ECMAScript anywhere in their website, so even thinking they’re gonna follow it loosely is optimistic they do mention that TypeScript is “closely aligned” with ECMAScript 6 on the language’s specification PDF). I’m not aware of their full policy on that, and maybe I’m being too harsh on them, but similar things have happened in the past.
Unfortunately, so far, I don’t see that happening. But that’s the future we bought, so it’ll have to do.
Hi, thanks for the pingback. Couple of things: the language specification for TypeScript does reference ECMAScript 6 by name for the class syntax; and there is experimental support for source maps in the compiler which will enable browser-based debugging (in Chrome and Firefox; IE doesn’t support source maps yet). I presume the VS2012 tooling will eventually provide TypeScript-source debugging, too.
Mark: thanks. Color me corrected. I’ve searched for ECMA on their specification PDF and couldn’t find it, and didn’t see it anywhere on the website, hence why I assumed they were intentionally leaving it out. I did a search in their PDF again and *did* find several instances, so I guess I screwed it up before (maybe the PDF wasn’t fully downloaded). Oops.
Comments are closed.