> With the start of a new season of Game of Thrones, folks are sitting on the edge of their seats waiting to see what’s coming. Unlike the Khaleesi who seems to be going nowhere fast, Node.js Tools for Visual Studio (NTVS) has made some moves recently.
Shots fired!
But really, excellent job on the release! Microsoft has been producing a lot lately, and that's awesome to see!
First, thanks so much for this, I love being in Visual Studio!
A few things I've noticed:
- when typing '.then' (for promises) intellisense seems to think I want '.attach' and that means I need to hit Esc and type it out manually. What's up with that?
- Performance seems to degrade over time, and the IDE just gets sluggish.
- After I made intellisense -not- use the disk and instead go in-mem (.ntvs_analysis.dat was getting huge!) I have almost no intellisense for any custom modules I loaded. (Things like lodash still seem to work)
Many, many thanks on making Visual Studio once again my place to live in all day!
They forked. There has been talk of reconciliation but it seems to me that many of the iojs folks are not really on-board with the idea. As far as which to use, take it from some guy on the internet, I say use iojs.
I have an impression that TypeScript (and docs) are somehow separated in its own. E.g. for Windows Store app development there are docs for C#, VB and JS. Also WinJS. So as a someone learning Node.js, it would be great to start directly with TypeScript, be it common patterns, OO, static typing or just plain syntax. Same goes for e.g. Windows app development.
Shots fired!
But really, excellent job on the release! Microsoft has been producing a lot lately, and that's awesome to see!