81–90 of 90 posts
I wonder how this compares to the Visual Node[1] plugin by Redgate. [1] http://www.visualnode.info/
Earlier quoted context omitted.
I do like dynamic languages for quick prototypes, but my experience on the scale of enterprise projects and their code quality, just increased my preference for static typing for production code.
TypeScript FTW. https://nodejstools.codeplex.com/workitem/291
I really like its design as a JavaScript superset.
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'm a big fan of Python Tools for Visual Studio ( https://pytools.codeplex.com/ ). Assuming Njs4VS lives up to it's predecessor, it could be a truly wonderful tool.
Earlier 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.
Earlier quoted context omitted.
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?
You don't have to use it for a website, it makes a great inter-service communication channel.
Earlier quoted context omitted.
Do you have a reference for Azure internals being written in node.js? I'd love to read about it.
A colleague reverse engineered Azure Mobile services, written in Node, to find out how it works. He blogged about it here: http://weblogs.asp.net/soever/archive/2013/07/26/azure-mobil...
Earlier quoted context omitted.
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.
I've tried having all these installed, and having them all in my %PATH%, along with msys and the platform sdk and so on, but i found I just ended up with my PATH env var being truncated because I went over the environment block size limit. I've given up pretending windows is unixy and ditched it in favor of homebrew on osx
There are other ways around it.
I wonder how this compares to the Visual Node[1] plugin by Redgate. [1] http://www.visualnode.info/
visualnode was a fork of http://pytools.codeplex.com and they've joined the NTVS project (which is also forked from the same source). Bart Read from red-gate did the npm GUI for NTVS in fact. they stated that they'll shut down visualnode.
---
Firstly, thanks for signing up for the beta of Visual Node, and trying out the tool. Your feedback has been incredibly helpful to us.
Today we have a very exciting announcement for you. Since the summer Red Gate has been working with Microsoft on a free, open source Node development environment for Visual Studio called Node Tools for Visual Studio (NTVS). We've just released the first public alpha of NTVS, which you can download from:
https://nodejstools.codeplex.com/
NTVS offers what we believe is a much richer development experience than Visual Node, including:
Various Node project types, IntelliSense and editing, Debugging, including remote debugging on Linux, Profiling, npm, Azure deployment, Support for both Visual Studio 2012 and 2013
In addition you can create NTVS projects based on existing code, making it easy to upgrade from Visual Node to NTVS. Please see https://www.simple-talk.com/blogs/2013/11/22/node-js-develop... for more information.
If you have any feedback we'd love to hear from you. You can report bugs or improvement requests at https://nodejstools.codeplex.com/workitem/list/basic, whilst support and general feedback/discussion is available at https://nodejstools.codeplex.com/discussions. Please do vote on the bugs/improvements you'd most like us to work on.
I'd like to take this opportunity to thank you again for participating in the Visual Node beta program. As I said, your feedback has been very helpful, and continues to influence the development of NTVS.
If you have any questions about anything in this email please do post to the discussion URL on Codeplex - we'd love to hear from you.
Kind regards,
Bart Read NTVS Contributor Red Gate Software https://nodejstools.codeplex.com/
This is a BIG step to make me switch to Windows. Debugging Node.js just like C# is really awesome (no brainer breakpoints and inspection: https://www.youtube.com/watch?v=W_1_UqUDx2s ). This plus a decent shell would definitely make me switch (I hate PowerShell).
thanks talles. note that you can debug from VS to Linux with NTVS. here's the debugging video: https://www.youtube.com/watch?v=-ir9ZB8lUg4