For many of us it already is.
also used different web servers including apache and tomcat.
We use Ant, Maven, MSBuild, Powershell, all without UNIX assumptions.
You can configure workstations via Active Directory.
Microsoft is not to blame if developers still insist in having .exe installers instead of adopting .msi packages.
In python I use pip.
In ruby I use rubygems.
In java I use maven for dependencies.
in node.js I use npm.
So really, even in ubuntu or macosx you will use theses tools.
There are other ways around it.
This plus a decent shell would definitely make me switch (I hate PowerShell).
As I mentioned, but didn't elaborate on, in my first post I had an urgent need to fix a production problem as quickly as possible. But the service giving us the problems was opaque, and encumbered by these massive 100+ project .NET solutions that had grown unwieldy for rapid development.
Being able to kick VS+TFS and their ceremony to the curb and hack out a solution with Node and Sublime Text was liberating. But it wasn't really VS I had a problem with, it was paying the price for years of technical debt. That's why I'm excited, I still think VS is a great IDE for my .NET work.
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.
No sane people tries to refactor such code.
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 great. I spend a lot of time on CLI running my app, installing a module, watching my dev logs,... I couldn't ever imagine anyone using node.js on windows. Now I can and it looks great.
Edit: WebStorm from the same company (JetBrains) is cheaper if you don't need all the java tools support.
How about a little golang love in Visual Studio?
Firstly, thanks for signing up for the beta of Visual Node, and trying out the tool. Your feedback has been incredibly helpful to us.
Today we have a very exciting announcement for you. Since the summer Red Gate has been working with Microsoft on a free, open source Node development environment for Visual Studio called Node Tools for Visual Studio (NTVS). We've just released the first public alpha of NTVS, which you can download from:
NTVS offers what we believe is a much richer development experience than Visual Node, including:
Various Node project types,
IntelliSense and editing,
Debugging, including remote debugging on Linux,
Support for both Visual Studio 2012 and 2013
In addition you can create NTVS projects based on existing code, making it easy to upgrade from Visual Node to NTVS. Please see https://www.simple-talk.com/blogs/2013/11/22/node-js-develop... for more information.
If you have any feedback we'd love to hear from you. You can report bugs or improvement requests at https://nodejstools.codeplex.com/workitem/list/basic, whilst support and general feedback/discussion is available at https://nodejstools.codeplex.com/discussions. Please do vote on the bugs/improvements you'd most like us to work on.
I'd like to take this opportunity to thank you again for participating in the Visual Node beta program. As I said, your feedback has been very helpful, and continues to influence the development of NTVS.
If you have any questions about anything in this email please do post to the discussion URL on Codeplex - we'd love to hear from you.
Red Gate Software
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?
Here's the work item that tracks this:
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
for a lighter weight solution, check out: http://channel9.msdn.com/Series/Visual-Studio-Online-Monaco/...
Yeah, instead of introduction Node this way, they should have specified this was an introducing to node.js Tools for Visual Studio.
What's cool about it, IMHO (I wrote the post above) is that it takes the V8 profiling stuff and feeds it into the VS visualizer...as it should.
It's awesome that they didn't screw with Node either to make it run on Chakra...
Just correct me if I am wrong.