61–70 of 90 posts
Earlier quoted context omitted.
TypeScript also uses node.
TypeScript uses npm as a package manager yes, but there is unfortunately no support for using Node within TypeScript yet on Visual Studio. There are definitions for node/express/etc, just cannot compile them directly in Visual Studio and also have debugging (unless the linked package in the OP has changed that).
Earlier quoted context omitted.
Well, they're not taking that away from you. You can still get started with the basics. But even node apps can get big. It's the debugging story I'm really digging here. Being able to just set a breakpoint and hit f5 is real exciting as opposed to having to type "debugger" in your code and then sit around for ages. It's a shame I do all my node work on a Mac. I'm guessing this won't be available for VS express?
Just like Python tools for VS it probably won't work with VS express, but it probably will work with the freely available VS shell (that is just the bare Visual Studio IDE without any existing language support in it). So you can get the whole package for free, but obviously only this node.js plugin will be open source.
Here's the work item that tracks this: https://nodejstools.codeplex.com/workitem/520
Earlier quoted context omitted.
Well, they're not taking that away from you. You can still get started with the basics. But even node apps can get big. It's the debugging story I'm really digging here. Being able to just set a breakpoint and hit f5 is real exciting as opposed to having to type "debugger" in your code and then sit around for ages. It's a shame I do all my node work on a Mac. I'm guessing this won't be available for VS express?
Just like Python tools for VS it probably won't work with VS express, but it probably will work with the freely available VS shell (that is just the bare Visual Studio IDE without any existing language support in it). So you can get the whole package for free, but obviously only this node.js plugin will be open source.
NTVS Express is a great idea, and I've opened a ticket for it already in case anyone wants to upvote: https://nodejstools.codeplex.com/workitem/520
thx
This plus a decent shell would definitely make me switch (I hate PowerShell).
This is a BIG step to make me switch to Windows. Debugging Node.js just like C# is really awesome (no brainer breakpoints and inspection: https://www.youtube.com/watch?v=W_1_UqUDx2s ). This plus a decent shell would definitely make me switch (I hate PowerShell).
Earlier quoted context omitted.
Microsoft's definitely giving NodeJS some credibility to enterprise shops
I hope they will understand when is the good case for using it. I wonder which kind of enterprise would need a high-load web site as opposed to a high-performance one?
Earlier quoted context omitted.
Sounds reasonable :). Although I dread imagining a JavaScript equivalent of a "100+ project .NET solutions" built in spirit of "rapid development".
I do like dynamic languages for quick prototypes, but my experience on the scale of enterprise projects and their code quality, just increased my preference for static typing for production code.
Wow, for an alpha release that's pretty impressive. Node seems to be really taking off at MS...parts of Azure are built with it...some really large parts of Azure. It's awesome that they didn't screw with Node either to make it run on Chakra...
I'm similarly surprised mozilla hasn't come out with an SM-powered node
Earlier quoted context omitted.
I do like dynamic languages for quick prototypes, but my experience on the scale of enterprise projects and their code quality, just increased my preference for static typing for production code.
Basically the important bit to remember when using dynamic languages in production is that you have to be extremely serious about writing (good) tests. It’s easy to get lazy when using a statically typed language as the compiler will do much of the work for you (especially if you take full advantage of the type system’s features). You can’t get away with that when writing e.g. JavaScript.
Enterprise developers don't write tests if their managers don't force them to, gets specially hairy when you have multiple consulting companies across multiple sites.
So you get JavaScript/Ruby/Python code with zero tests.
No sane people tries to refactor such code.
This is the kind of thing that makes me want to switch back to Windows. I like VS since I've been using it to develop a C# app these last two months. I miss a lot of things because I'm too deep in CLI usage (like git...help me...), but had I had it when I tried to play with Ruby on Windows 7 three years ago and discovered the pain of the windows CLI, maybe I would've stayed there. These Node.js tools are especially g…
Let me guess, you used plain cmd instead of PowerShell.