Actual TypeScript Roadmap??

Topics: General
Nov 15, 2012 at 7:53 PM
Edited Nov 15, 2012 at 8:34 PM

Yes, I know there's a joke of a roadmap here:

http://typescript.codeplex.com/wikipage?title=Roadmap&referringTitle=Home

 

When are you guys going to release actual updated plans for what you're planning for this language? It's been a month and a half since you announced TypeScript and there's yet to be any update on what additional public releases are going to contain or when they will happen.

I've looked at the develop branch, and all the checkins since the public release have been bug fixes from what I can tell (without diving in too deeply). It would really help organizations adopt TypeScript if we had a firm commitment from MS on developing and supporting this language and the almost total radio silence is not helping. Yes, Jon Turner has escalated many requests to Issues in the Issue Tracker, but not a single one of these have been comments, priorities, or ETAs assigned yet.

When will generics be added? Where are we with source map support in VS? Is async/await likely to happen or is not going to happen? Open source projects ideally entail more than just a source code dump. 

For a comparison on how to quickly respond to community feedback, Mads Kristensen's great team has had 7 releases of VS Web Essentials 2012 in the last month and a half.

In summary, I think TypeScript is fantastic so far, but a tighter feedback loop would be really helpful.

UPDATE:

Possibly as I was writing this, 8.1 was released. As I posited, it looks like mainly bug fixes. Some feedback about planned features and release timelines would still be super helpful.

Nov 16, 2012 at 10:55 AM
Edited Nov 16, 2012 at 10:58 AM

I rather think that the approach taken by the TypeScript team is the right one.

There are still a number of bugs in the implementation of the language as it stands, and this is probably not the time to slap on new features. Consequently, I think it is important to stabilise the existing feature set and ensure everything is working before anything new is introduced.

It would be great if we had generics, const etc. but even without such features TypeScript is a tremendous asset to web development. IMO the argument for adopting the language is already won - when set against life before TypeScript: JSLint and "too many var statements"!

Of course if Microsoft wants to stop everything else and have everyone working on TypeScript, I for one will be cheering them on!

In the meantime, I vote for the TypeScript team to not cave into pressure for new features and instead keep the bug fixes coming.

Noel

 

PS:  Incidentally (and ironically), there is no corresponding Web Essentials release for TypeScript 0.8.1, which means I've had to turn off the preview window and compile on save.

Nov 16, 2012 at 11:17 AM
nabog wrote:

I rather think that the approach taken by the TypeScript team is the right one.

There are still a number of bugs in the implementation of the language as it stands, and this is probably not the time to slap on new features. Consequently, I think it is important to stabilise the existing feature set and ensure everything is working before anything new is introduced.

They already mentioned numerous times that they're actively working on generics. So they are already implementing new features.. They just don't tell the community anything.

Nov 16, 2012 at 12:52 PM
nabog wrote:

I rather think that the approach taken by the TypeScript team is the right one.

There are still a number of bugs in the implementation of the language as it stands, and this is probably not the time to slap on new features. Consequently, I think it is important to stabilise the existing feature set and ensure everything is working before anything new is introduced.

It would be great if we had generics, const etc. but even without such features TypeScript is a tremendous asset to web development. IMO the argument for adopting the language is already won - when set against life before TypeScript: JSLint and "too many var statements"!

Of course if Microsoft wants to stop everything else and have everyone working on TypeScript, I for one will be cheering them on!

In the meantime, I vote for the TypeScript team to not cave into pressure for new features and instead keep the bug fixes coming.

Noel

 

PS:  Incidentally (and ironically), there is no corresponding Web Essentials release for TypeScript 0.8.1, which means I've had to turn off the preview window and compile on save.

I'm advocating for transparency about where they're planning to go, not for them to focus on features vs bugs. Dumping a project on the web and then going almost totally silent about future plans for a month and a half does not give a strong impression of commitment. Especially given how MS has such a nasty habit of unveiling a new technology and then killing off said technology not long after. they need to be more transparent with what the process is going to be.

Nov 16, 2012 at 1:01 PM

TypeScript is Open Source. You can't really 'kill' an open source project.

Nov 16, 2012 at 1:08 PM

If it stops being supported it will likely die.

Scenario: Future versions of ECMAScript come out. TypeScript does not comply with the syntax of these versions because it's no longer being supported. The community may try and rewrite the compiler, but what about editor support? The VS extension is not open source.

Once a language has been abandoned by its creators, who is going to take the risk of trying to start something new with it?

Nov 16, 2012 at 1:27 PM

I already complained about this, but I only got a half hearted answer:

http://typescript.codeplex.com/discussions/400934

Nov 25, 2012 at 7:10 AM

And exactly this is what we meant.. No response in over a week.

Coordinator
Nov 26, 2012 at 4:27 PM

Apologies for not putting the roadmap up/assigning dates sooner.  We've been collecting feedback from the community on what needs to be fixed and then prioritizing based on the biggest needs first.  Many of the requests in the issue tracker do have milestones we're targeting, but I just haven't done the work of adding that info to each issue, yet.