Earlier quoted context omitted.
I gave up on deploying my node.js app to Azure after finding that several modules I was using were simply not possible to run on Windows. Wasn't worth the trouble to refactor and avoid these dependencies. Windows is not a priority for most node.js devs, so unless you're doing something pretty simple/mainstream, you're likely to run into trouble.
Azure supports OSes other than Windows.
Node.js Tools for Visual Studio
11–20 of 127 posts
Re: Node.js Tools for Visual Studio
#12How 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…
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.
Re: Node.js Tools for Visual Studio
#13How 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…
I've worked with some of these people on the web agency end of the spectrum. They're good at what they do, but they're absolutely not interested or specialized in anything sysadmin-related. For them, Unix is a hairy old beast and Microsoft is the company whose solutions are imperfect but accessible, and that has allowed them to concentrate on their job for the past 20 years.
As Microsoft adds new technologies to their palette, these users will pick it up. They'd never do it on their own as long as it involves steps like "just spin up a virtual Linux box on AWS"...
On HN, it's easy to start assuming that everyone speaks Bash as a second language, but that's very far from the truth.
Re: Node.js Tools for Visual Studio
#14Dev here - happy to answer any questions you have :)
Re: Node.js Tools for Visual Studio
#15How 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.
I see it ultimately as damage control. With the overwhelming majority of developers on unix, you're not going to see microsoft hang out in the server market for very long. I think they'll hang onto the office crowd, but nothing on the backend.
This, of course, is just the opinion of a 20 year old unix nerd, who became one because his father is a microsoft fanboy. I rebelled in my teenage years by infuriating my father and installing linux. I still think I raise some valid points.
Re: Node.js Tools for Visual Studio
#16Dev here - happy to answer any questions you have :)
How do you handle the super-long paths npm is so fond of? On Windows I often run into issues when searching or trying to manipulate a solution containing anything npm due to too-long paths.
Re: Node.js Tools for Visual Studio
#17How 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…
Re: Node.js Tools for Visual Studio
#18How 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…
There's a web based console that's sadly not that well known. Here's a screenshot: http://i.imgur.com/Lrw7lL1.png
Here's a video showing more of the features (it's from 2013, it looks better and more has been added since then, but it shows the idea): http://channel9.msdn.com/shows/azure-friday/exploring-the-su...
Re: Node.js Tools for Visual Studio
#19How 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.
Re: Node.js Tools for Visual Studio
#20Dev here - happy to answer any questions you have :)
Also - any way we might get "break on exception" like with C#?
Also - any plans to support debugging promises better?