Live data from Hacker News

Node.js Tools for Visual Studio

blogs.msdn.com

21–30 of 127 posts

Re: Node.js Tools for Visual Studio

#21

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

It's super cool for people wanting to do node on Windows. I used the beta while doing a small side project at my last job, and they worked well for that project.

My issue isn't necessarily azure and VS. It's the state of node on Windows. It's a second class citizen compared to the versions for posix compliant OSes. There are things that just don't work on Windows without installing VS, which is undesirable for deployment, and that's assuming they work even after VS is installed.

I'd rather spin up a local Ubuntu VM and write code in WebStorm, and that's what I do. I get debugger support, test runners, code completion, etc. Plus, I can then just deploy to cheaper VPS providers (DigitalOcean, Vultr, etc).

Re: Node.js Tools for Visual Studio

#22

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

node.js has been used heavily inside Microsoft for quite some time so even if they created this for internal use only it wouldn't be a waste of time. Microsoft employee here.

And I think you vastly underestimate how popular Visual Studio is among enterprise developers - they're doing web development as well.

Re: Node.js Tools for Visual Studio

#23

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

Lots of .Net companies dabble in Node.js and other alternatives to .Net and any competent developer is capable of creating sites on any operating system with a little bit of time and patience to learn.

I've been doing .Net development for over 5 years and my newest site is based in Node.js hosted on AWS. I am currently using Web Storm, which is great, but this plugin is definitely something I'll check out and is probably created for people like me: Someone who is a .Net developer, already has VS, but has a need for Node.js code.

Re: Node.js Tools for Visual Studio

#24
post #12

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

The people writing nodejs code are all using vim and unix No they aren't, that's just your perception because you are surrounded by those that are. AFAIK Windows Node developers are still a minority, but that doesn't mean they're not a sizable group of people. A lot of code is written in corporate environments in C# and Visual Studio - adding Node to that mix is a sensible bet on Microsoft's part.

Completely agree with you , But even all node.js dev's are user of unix/vim/emacs (I am emacs user though) this does not mean Microsoft should not develop tools for its users.Microsoft try to attract developer to its own platform , which is OK , at least I think it is ok. Every Company doing same thing.

Re: Node.js Tools for Visual Studio

#26
post #24
post #12

Earlier quoted context omitted.

The people writing nodejs code are all using vim and unix No they aren't, that's just your perception because you are surrounded by those that are. AFAIK Windows Node developers are still a minority, but that doesn't mean they're not a sizable group of people. A lot of code is written in corporate environments in C# and Visual Studio - adding Node to that mix is a sensible bet on Microsoft's part.

Completely agree with you , But even all node.js dev's are user of unix/vim/emacs (I am emacs user though) this does not mean Microsoft should not develop tools for its users.Microsoft try to attract developer to its own platform , which is OK , at least I think it is ok. Every Company doing same thing.

I wasn't ever trying to say this is a bad effort or anything. I think it's a relatively good thing. I just don't see azure as sustainable.

Re: Node.js Tools for Visual Studio

#27

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

Based on a totally-not-statistically-significant-survey our team conducted, we are seeing that yes - many node devs are deploying to Linux, but developing on Windows. We support this scenario through remote debugging to any OS. Azure not required :)

This appears to be consistent with npm's data as well (see this infographic - % devs accessing npmjs.org http://blog.modulus.io/growth-of-npm-infographic).

We also try very hard to make sure that NTVS works well with people's existing tools and packages - so if you run into an issue, please let us know (or better yet, make a PR!)

Re: Node.js Tools for Visual Studio

#28
post #24

Earlier quoted context omitted.

Completely agree with you , But even all node.js dev's are user of unix/vim/emacs (I am emacs user though) this does not mean Microsoft should not develop tools for its users.Microsoft try to attract developer to its own platform , which is OK , at least I think it is ok. Every Company doing same thing.

I wasn't ever trying to say this is a bad effort or anything. I think it's a relatively good thing. I just don't see azure as sustainable.

Why not? Azure is platform agnostic at this point, it isn't just a home for .NET code.

Re: Node.js Tools for Visual Studio

#29
post #6
post #3

Earlier quoted context omitted.

Great work, looks very nice. Will give it a whirl when I get home. In the meanwhile, I noticed that you support intellisense. What are the limitations to this? What patterns will get correctly picked up? I assume prototypal inheritance will work fine (of course), but will any of the BaseClass.extend()-style inheritance mechanisms that some frameworks seem to favour (e.g. Backbone) work? While we're at it, is the stat…

> While we're at it, is the static analysis tools you built for this public? maybe this? http://nodejstools.codeplex.com/SourceControl/latest#Nodejs/...

Looks like it, yeah. Thanks!

Re: Node.js Tools for Visual Studio

#30

Dev here - happy to answer any questions you have :)

Is this going to make it easier to deploy NodeJs apps to Azure then? Love Azure, but had a hard time getting my NodeJS stuff up to Azure without some major issues.

Same, and I gave up trying to get Node to work with SQL Server. Ended up at Heroku because of this.
Post reply on HN