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

Visual Studio Code is now open source

code.visualstudio.com

Post reply on HN
Print view View original

161–170 of 403 posts

Re: Visual Studio Code is now open source

#162

Post by spleeder »

lewisl9029 wrote: post #80
tapoxi wrote: post #6

As an Atom user that's only dabbled with VS Code when it was announced, what are its advantages? Last time I tried Code it seemed like a fork of Atom with Microsoft branding.

Long time Atom user here as well. When I first tried VS Code, the first thing that I noticed was how much better the performance was compared to Atom. From general snappiness of basic editing tasks to startup times to working with large files, VS Code simply outperformed Atom across the board according to my brief unscientific observations. At the time, I ended up sticking with Atom mainly because VS Code wasn't open…

This is my experience as well. I am really impressed at how VS Code as no problem working with large and minified files.

Re: Visual Studio Code is now open source

#163

Post by mixmastamyk »

bluejekyll wrote: post #89

This is pretty amazing from the company that was trying to kill Linux just a few years ago and is now adopting that mentality for developing and delivering software. While I don't want to be negative; this and other recent moves by MS, seem to be an effort to lighten the overladen ship that is the MS super-tanker. Will moves like this prevent them from sinking? Personally, I switched away from MS products in 1996 and…

True, but the company is still schizophrenic, so I continue to be wary of them. While there have been many positive steps like this one, the other side of the company continues to double-down on the data collection and relationship with spy agencies.

Re: Visual Studio Code is now open source

#166

Post by bigtones »

hasenj wrote: post #65

The name of the "VS Code" product makes the title a little mis-leading. I thought the code for "Visual Studio" was open sourced. Turns out it's just this stripped down editor called "Visual Studio Code".

Microsoft have never been good at product naming. Just today they renamed 'Visual Studio Online' to 'Visual Studio Team Services' because people thought it was an online version of Visual Studio.

They need a VP of Product Names, someone that actually cares what their products are called. '.Net' for example is a stupid name because it is practically un-googleable.

Re: Visual Studio Code is now open source

#167

Post by mschuster91 »

gtaylor wrote: post #111
azinman2 wrote: post #105

Earlier quoted context omitted.

Honestly none of those are very good. The UX, speed, stability, etc is lacking. Eclipse is ok if you're only doing Java (and was good 10 years ago, but the UX is irrelevant today), but sucks for everything else. IntelliJ is the only one do better support other languages but it too is quite clunky, and I use it regularly. Sublime is not on the verge of becoming an IDE, nor any of those other ones. There are way too ma…

Jetbrains IDEs are highly regarded and run very well under Linux.

Jetbrains stuff eats up nearly as much RAM as Eclipse. If you're not on an 8+GB machine, prepare for your SSD life being massively reduced due to swap.

Re: Visual Studio Code is now open source

#168

Post by spankalee »

I wonder how VSC works with node APIs?

One thing I really dislike about Atom is it's complete reliance on and lack of abstraction over the node APIs, making it nearly impossible to port to run hosted (which really confuses me, as I'd think that Github would love to have a great online editor integrated right into repos).

If VSC only uses async APIs, it might be easier to get running in a browser.

Also, Atom's security model is very weak. Extensions have direct access to node APIs (as do iframes! but that's an Electron issue). Sandboxing extensions would be a huge deal for me.

Re: Visual Studio Code is now open source

#170

Post by ehaughee »

plexicle wrote: post #139
lewisl9029 wrote: post #80

Earlier quoted context omitted.

Long time Atom user here as well. When I first tried VS Code, the first thing that I noticed was how much better the performance was compared to Atom. From general snappiness of basic editing tasks to startup times to working with large files, VS Code simply outperformed Atom across the board according to my brief unscientific observations. At the time, I ended up sticking with Atom mainly because VS Code wasn't open…

This is spot on for me as well. I always wondered how VSC was so much faster given that they are both on top of Electron. In either case, this is all great news.

Electron, iirc, is just the UI layer. Atom actually has a lot of code written to render, edit, and rerender text (they were initially using React at one layer of the process). I can't find it now, but there was a good blog post from the Atom team that discussed their efforts in detail. So I guess I'm trying to say that I believe the code handling the slow parts is predominantly unrelated to the UI layer. Also, iirc, VSCode's editor is based on Monaco (http://www.zdnet.com/article/microsofts-browser-based-dev-to...).
Post reply on HN