Live data from Hacker News

Node.js Tools for Visual Studio

nodejstools.codeplex.com

21–30 of 70 posts

Re: Node.js Tools for Visual Studio

#21
Until they can address the problem with building certain NPM modules on windows (ie `node-gyp` related ones), this is a bit of a non-starter.

Sadly the only reason I keep my windows based desktop around these days is PC gaming is still very much windows based.

Re: Node.js Tools for Visual Studio

#22
post #5

Perhaps I'm paranoid but I'm seeing a lot of tentacles extending around a few ecosystems from Microsoft. I see lots of praise but some rational analysis and caution might be worth considering. For ref, I deal with Microsoft a lot and wrote a ton of c# over the least decade (more than anything else probably) so I'm not biased against necessarily but all-encompassing announcements like the ones over the last couple of…

This is as insightful comment and the points you raise may be important for a startup, SAAS or software product company to consider. A lot of organizations use and develop software but aren't software companies.

"A fully heterogenous system with a sole vendor mediating your access" is a good thing for these companies.

I do a lot of contract work for state and local governments. They are already fully invested in SQL Server, IIS and Active Directory. For both these organizations and myself as a contractor to them I see the increased openness of Microsoft as only a good thing.

Re: Node.js Tools for Visual Studio

#23
post #6

It's an attempt to bring back developer to windows platform. I personally don't know a single serious web developer using windows unless they are coding in .NET.

What? This is an attempt to sell Visual Studio by making it relevant to what developers are using!

Re: Node.js Tools for Visual Studio

#24
post #6

It's an attempt to bring back developer to windows platform. I personally don't know a single serious web developer using windows unless they are coding in .NET.

What? This is an attempt to sell Visual Studio by making it relevant to what developers are using!

yeah possibly that too.

Re: Node.js Tools for Visual Studio

#25
post #20
post #19

It's better late than never. It's just easier to say 'I quit' because it's likely none of Node.js developers will switch to using Visual Studio rather than give it a try. Though I probably will never use Visual Studio for writing my Node.js project, kudos for MS not being the old MS. So what's next for MS? I think they are getting the direction right for opening up for external MS product users, and now it's time to…

I think msft building this kind of tooling around exciting tech like node gives node more credibility in a big enterprise type of shop...will only be a good thing for node,

Exactly. This is a play for the next tier of developers, which will mostly be enterprise, mostly use Windows, and be much larger.

Re: Node.js Tools for Visual Studio

#26

Until they can address the problem with building certain NPM modules on windows (ie `node-gyp` related ones), this is a bit of a non-starter. Sadly the only reason I keep my windows based desktop around these days is PC gaming is still very much windows based.

I keep hearing this meme but I use node on Windows and don't have any issues with this. You have to have Visual Studio and Python installed, but most of us have that anyway.

Which node modules are problem children?

Re: Node.js Tools for Visual Studio

#29
post #6

It's an attempt to bring back developer to windows platform. I personally don't know a single serious web developer using windows unless they are coding in .NET.

What? This is an attempt to sell Visual Studio by making it relevant to what developers are using!

Now they just need to port it to *nix platforms. Well, perhaps Visual Studio Online is their way of doing that...

Re: Node.js Tools for Visual Studio

#30
I tried the alpha a few months back, and found it to understandably be lacking, My biggest frustration with it was trying to profile the performance of a complex piece of code with a number of callbacks and such. NTVS would only look at the first iteration, and not tell me anything useful (at the time I was tracing a memory leak). There were a few other inconveniences which I noticed that issues were raised for, hopefully most were fixed.
Post reply on HN