Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
Programming Microsoft Open Source

Microsoft Adds Node.js Support To Visual Studio 197 197

shutdown -p now writes "Coming from the team that had previously brought you Python Tools for Visual Studio, Microsoft has announced Node.js Tools for Visual Studio, with the release of the first public alpha. NTVS is the official extension for Visual Studio that adds support for Node.js, including editing with Intellisense, debugging, profiling, and the ability to deploy Node.js websites to Windows Azure. An overview video showcases the features, and Scott Hanselman has a detailed walkthrough. The project is open source under Apache License 2.0. While the extension is published by Microsoft, it is a collaborative effort involving Microsoft, Red Gate (which previously had a private beta version of similar product called Visual Node), and individual contributors from the Node.js community."
This discussion has been archived. No new comments can be posted.

Microsoft Adds Node.js Support To Visual Studio

Comments Filter:
  • Stop with JavaScript (Score:2, Interesting)

    by sanosuke001 (640243) on Thursday November 21, 2013 @03:28PM (#45483917)
    Please, for everyone's sanity, stop it with the JavaScript crap; it's a terrible language, a terrible platform for applications, and supporting it is just prolonging it's Reign of Terror. (this is why we still have flash).
  • by Anonymous Coward on Thursday November 21, 2013 @04:07PM (#45484335)
    The performance and capabilities of these browser applications feel like they're from 1993, but yet they require 100x the resources of a modern desktop program.
  • by shutdown -p now (807394) on Thursday November 21, 2013 @04:47PM (#45484703) Journal

    Sure, karma is a bitch. In fact, part of what we're trying to do as a team is to turn it around, both the external perception as well as internal company understanding on openness - not just open source, though that as well, but generally working together on common things, and purging the NIH and the "we must be in charge" syndrome.

    It's not just us, too - it has been a growing thing in the developer division, in general, with a lot more stuff being open sourced, and a broad change of attitude from a single monolithic take-it-or-leave-it stack, to going where the people already are and supporting what they already do. You might have noticed some other glimpses of that if you've been following the general news on MS dev story, e.g. with a renewed effort on C++ standard conformance, or a lot more attention to JS and HTML5.

  • by shutdown -p now (807394) on Thursday November 21, 2013 @06:23PM (#45485619) Journal

    My own personal take on software patents (which is obviously my own only, does not represent the opinion of my employer in any way, blah blah etc) is that they can play a useful role, but they should be significantly scaled down in terms of what you can patent. Complicated algorithms, like, say, MP3 or H.264 or other compression stuff - probably yes, since that takes real time and effort to develop. But I'd love to see the "one click" patents die a fiery death. Some laws that would require non-discriminatory licensing for useful patents for interoperability and standards compliance purposes would also be great.

    So EFF gets part of my paycheck every year. Ironically enough, it qualifies for MS donation match program, so they match it dollar for dollar. ~

The generation of random numbers is too important to be left to chance.

Working...