Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js Tools for Visual Studio

hanselman.com

Post reply on HN
Print view View original

31–40 of 90 posts

Re: Node.js Tools for Visual Studio

#31

Post by jbigelow76 »

_random_ wrote: post #24
jbigelow76 wrote: post #5

I like this. I smuggled Node into our company to suplant a very difficult to test/debug WCF process and it's slowly been creeping out into bigger use cases. I've tried using VS for managing my Node scripts but it just wasn't a very elegant fit given VS's concept of projects and solutions so I kept falling back to Sublime. I'm excited to see if I can finally maintain just a single editor for both my .NET and Node code…

Why not Web API and SignalR?

I like Web API a lot and would have no problems using it more. I've never messed around with SignalR, I had already started playing with Node at that point.

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.

One other final reason I wanted to use Node was because I felt for someone that considered himself to be a "web developer" I was abnormally shitty at javascript and wanted to know it better :)

Re: Node.js Tools for Visual Studio

#33

Post by fro »

int_19h wrote: post #20
fro wrote: post #19

Seems like overkill. Part of why Node is great and so easy to get started with is that all you need is a browser, a text editor, and the terminal. I suppose for people that already use VS this is good, but maybe we should encourage them to write Node apps outside of that environment instead of shoving Node into a giant IDE.

There's more to development than a text editor, though. Sometimes you do want debugging. And maybe you want syntax highlighting in your REPL. And, perhaps, you'd like some profiling to figure out how to make your Node app run faster.

Yes, and most of those things are already available as modular open source tools that fit well in the Node ecosystem. Encouraging people to use one giant, closed, monolithic program for all of those purposes is not a good step forward for Node.

Re: Node.js Tools for Visual Studio

#35

Post by weavie »

fro wrote: post #19

Seems like overkill. Part of why Node is great and so easy to get started with is that all you need is a browser, a text editor, and the terminal. I suppose for people that already use VS this is good, but maybe we should encourage them to write Node apps outside of that environment instead of shoving Node into a giant IDE.

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?

Re: Node.js Tools for Visual Studio

#36

Post by jbigelow76 »

fro wrote: post #33
int_19h wrote: post #20

Earlier quoted context omitted.

There's more to development than a text editor, though. Sometimes you do want debugging. And maybe you want syntax highlighting in your REPL. And, perhaps, you'd like some profiling to figure out how to make your Node app run faster.

Yes, and most of those things are already available as modular open source tools that fit well in the Node ecosystem. Encouraging people to use one giant, closed, monolithic program for all of those purposes is not a good step forward for Node.

I think you are failing to make the distinction that the Node community isn't encouraging devs to use Visual Studio; Visual Studio is helping its community to use Node.

Re: Node.js Tools for Visual Studio

#37

Post by _random_ »

jbigelow76 wrote: post #31
_random_ wrote: post #24

Earlier quoted context omitted.

Why not Web API and SignalR?

I like Web API a lot and would have no problems using it more. I've never messed around with SignalR, I had already started playing with Node at that point. 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 unwiel…

Sounds reasonable :). Although I dread imagining a JavaScript equivalent of a "100+ project .NET solutions" built in spirit of "rapid development".

Re: Node.js Tools for Visual Studio

#38

Post by _random_ »

taude wrote: post #32
Touche wrote: post #6

Very nice, will help Node break into the enterprise.

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?

Re: Node.js Tools for Visual Studio

#39

Post by mmgutz »

I'll admit I'm one of those who whined about nodeJS targeting Windows. Windows is starting to look more and more like a first-tier nodeJS platform with help from Microsoft! Can't wait to try this out.

How about a little golang love in Visual Studio?

Re: Node.js Tools for Visual Studio

#40

Post by pjmlp »

gum_ina_package wrote: post #13

Seeing things like this gives me hope that one day Windows will be a first class os for web development. Now if I could just maximize the command prompt window....

> Seeing things like this gives me hope that one day Windows will be a first class os for web development.

For many of us it already is.

Post reply on HN