Earlier quoted context omitted.
Let me guess, you used plain cmd instead of PowerShell.
True. I had used cmd for about 15 years before that, so while using "cd" or "dir" and the classic lingo was okay, doing everything rails-related in CLI just felt..clunky: "why would you have such a bad interface? EasyPHP does everything just fine with a GUI!". Had I known CLI could be more intuitive (hello pipes!), I'd have looked up for a better alternative sooner =)
Node.js Tools for Visual Studio
71–80 of 90 posts
Re: Node.js Tools for Visual Studio
#72Earlier quoted context omitted.
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?
Just like Python tools for VS it probably won't work with VS express, but it probably will work with the freely available VS shell (that is just the bare Visual Studio IDE without any existing language support in it). So you can get the whole package for free, but obviously only this node.js plugin will be open source.
Re: Node.js Tools for Visual Studio
#73Seems 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.
Re: Node.js Tools for Visual Studio
#74Seeing 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....
Re: Node.js Tools for Visual Studio
#75Earlier quoted context omitted.
windows is a first class os for web development. what is it lacking? i have coded in ruby, python, java and go for the web. also used different web servers including apache and tomcat.
For me the lack of many unix tools is a killer and cygwin doesn't cut it. Many build scripts assume a unixy environment and windows is flat-out not supported. Lack of a proper package manager also makes installing and configuring workstations a hassle.
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.
Re: Node.js Tools for Visual Studio
#76Seeing 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....
ConEmu [1] has made CLI on Windows much more tolerable for me. [1] http://code.google.com/p/conemu-maximus5/
Re: Node.js Tools for Visual Studio
#77Re: Node.js Tools for Visual Studio
#78Earlier quoted context omitted.
ConEmu ( https://code.google.com/p/conemu-maximus5/ ) + Quake Mode = Awesome :)
THIS. ConEmu + Scoop ( http://scoop.sh ) has made using Windows much much much more productive for me.
Re: Node.js Tools for Visual Studio
#79Earlier quoted context omitted.
For me the lack of many unix tools is a killer and cygwin doesn't cut it. Many build scripts assume a unixy environment and windows is flat-out not supported. Lack of a proper package manager also makes installing and configuring workstations a hassle.
I don't think the package manager matters to be honest. 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.
Re: Node.js Tools for Visual Studio
#80Edit: WebStorm from the same company (JetBrains) is cheaper if you don't need all the java tools support.