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

Node.js Tools for Visual Studio

nodejstools.codeplex.com

Post reply on HN
Print view View original

61–70 of 70 posts

Re: Node.js Tools for Visual Studio

#61

Post by NicoJuicy »

jw2013 wrote: post #19

It's better late than never. It's just easier to say 'I quit' because it's likely none of Node.js developers will switch to using Visual Studio rather than give it a try. Though I probably will never use Visual Studio for writing my Node.js project, kudos for MS not being the old MS. So what's next for MS? I think they are getting the direction right for opening up for external MS product users, and now it's time to…

There's a reason why Visual Studio continues to impress you.

I once saw a presentation of the Visual Studio lead in Belgium, where he claimed that there were over 1200 people involved in the Visual Studio project. If that's true, i don't think there is any IDE that can top that number and it explains why Visual Studio is the best tool for (almost any) job.

People should realize that Visual Studio is not solely C#, it's NodeJS, PHP, Mono, Python, javascript and so much more in one environment (with a good autocompletion). If you have Windows and are a developer, i suggest you to install one of the Express editions, just to try it out.

I must admit, not everything is "as awesome as it is" in the express versions because of some limitations on extensions, but in my experience, you can do everything you need in the Express editions. But i don't think visual studio wouldn't be as good as it is, if it was free or opensource. (replacing 1200 developers would be very hard).

PS. Can anyone confirm my statement of 1200 developers/freelancers? I really think that's the number the Visual Studio lead developer mentioned.

Re: Node.js Tools for Visual Studio

#62

Post by NicoJuicy »

jw2013 wrote: post #19

It's better late than never. It's just easier to say 'I quit' because it's likely none of Node.js developers will switch to using Visual Studio rather than give it a try. Though I probably will never use Visual Studio for writing my Node.js project, kudos for MS not being the old MS. So what's next for MS? I think they are getting the direction right for opening up for external MS product users, and now it's time to…

There's a reason why Visual Studio continues to impress you.

I once saw a presentation of the Visual Studio lead in Belgium, where he claimed that there were over 1200 people involved in the Visual Studio project.

If that's true, i don't think there is any IDE that can top that number and it explains why Visual Studio is the best tool for (almost any) job.

People should realize that Visual Studio is not solely C#, it's NodeJS, PHP, Mono, Python and so much more in one environment.

If you have Windows, i suggest you install one of the Express editions, just to try it out.

I must admit, not everything is "as awesome as it is", because there are some limitations on the Express versions considering extensions. But i don't think visual studio wouldn't be as good as it is, if it was free or opensource. (1200 developers (don't think fulltime though) to replace would be a very hard thing)

Re: Node.js Tools for Visual Studio

#63

Post by teacup50 »

jw2013 wrote: post #19

It's better late than never. It's just easier to say 'I quit' because it's likely none of Node.js developers will switch to using Visual Studio rather than give it a try. Though I probably will never use Visual Studio for writing my Node.js project, kudos for MS not being the old MS. So what's next for MS? I think they are getting the direction right for opening up for external MS product users, and now it's time to…

> I think they are getting the direction right for opening up for external MS product users, and now it's time to recruit top talent again. There are just too many great hackers think MS is old ...

I don't know who you think the "great hackers" are that Microsoft should hire, but Microsoft is overflowing with top talent. They don't need to "recruit top talent again", because they already were and long have been.

The research division of Microsoft was created in 1991 and employs computer scientists, physicists, engineers, and mathematicians, including Turing Award winners, Fields Medal winners, MacArthur Fellows, and Dijkstra Prize winners. These 1,100 scientists and engineers collaborate with academic, government, and industry researchers to advance the state of the art of computing, and solve difficult world problems through technological innovation.

http://en.wikipedia.org/wiki/Microsoft_Research

Microsoft's problem is management, not talent. They already some of the best talent money can buy.

> 2) buy early-stage companies through acqui-hire.

Why would Microsoft benefit from hiring inexperienced teams out of startups on the acquihire market?

Re: Node.js Tools for Visual Studio

#65

Post by likeclockwork »

ivanca wrote: post #54
likeclockwork wrote: post #44

Earlier quoted context omitted.

That's a search trend. It includes people searching for help. I'm not surprised Windows leads it for Node, it's a pain to work with most *nix software (especially that which doesn't have a point and click interface) on Windows.

Keep telling yourself that, specially when the spikes are the same than in Linux.

"nodejs linux" as a search string is also partially redundant.

Re: Node.js Tools for Visual Studio

#67

Post by outside1234 »

teacup50 wrote: post #63
jw2013 wrote: post #19

It's better late than never. It's just easier to say 'I quit' because it's likely none of Node.js developers will switch to using Visual Studio rather than give it a try. Though I probably will never use Visual Studio for writing my Node.js project, kudos for MS not being the old MS. So what's next for MS? I think they are getting the direction right for opening up for external MS product users, and now it's time to…

> I think they are getting the direction right for opening up for external MS product users, and now it's time to recruit top talent again. There are just too many great hackers think MS is old ... I don't know who you think the "great hackers" are that Microsoft should hire, but Microsoft is overflowing with top talent. They don't need to "recruit top talent again", because they already were and long have been. The…

Honestly, we are getting a lot better at management too. The tech leaders are starting to move to the front (see Scott Guthrie). In the past, it would have been the beancounter (see Kevin Turner).

Re: Node.js Tools for Visual Studio

#68

Post by ivanca »

likeclockwork wrote: post #65
ivanca wrote: post #54

Earlier quoted context omitted.

Keep telling yourself that, specially when the spikes are the same than in Linux.

"nodejs linux" as a search string is also partially redundant.

Indeed, mostly because is redundant for any OS thanks to npm:

    npm install anything

Re: Node.js Tools for Visual Studio

#70

Post by balls187 »

jahansafd wrote: post #55
outside1234 wrote: post #26

Earlier quoted context omitted.

I keep hearing this meme but I use node on Windows and don't have any issues with this. You have to have Visual Studio and Python installed, but most of us have that anyway. Which node modules are problem children?

I had trouble with bcrypt

Our project uses bcrypt as well, and could not easily be npm'd on Windows.
Post reply on HN