Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

91–100 of 487 posts

Re: Visual Studio Code 1.0

#91
Probably a good option for newbies, but anyone that's been coding for any length of time will already have too much muscle memory to warrant a switch. For me it's Emacs for editing and Visual Studio Pro for "project administration" and in the rare situation, interactive debugging. I've not yet made the leap to OmniSharp, but that's what is next.

Re: Visual Studio Code 1.0

#93
post #62

Earlier quoted context omitted.

> Atom was around before VSCode Nope. Visual Studio Code was created before Atom.[1] Although both VS Code and Atom are based on Electron[1] and are both Chrome-based. VS Code does seem to be stealing Atom's thunder as what they say [1] [1] https://discuss.atom.io/t/atom-seems-to-be-lossing-contribut...

Electron (formerly called Atom-shell) was created for Atom. The source you cited even says this!

Read this particular comment in that link.

https://discuss.atom.io/t/atom-seems-to-be-lossing-contribut...

Re: Visual Studio Code 1.0

#96

VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…

[deleted]

Re: Visual Studio Code 1.0

#97
post #49

Isn't this based on Atom (or at least similar design)? It really makes me sad that people are making editors with so many features and nice things, but ignoring the fundamentals like latency. https://pavelfatin.com/typing-with-pleasure/ I'm eagerly awaiting a mac version of 4coder ( http://www.4coder.net/ ).

Did you actually try it?

Re: Visual Studio Code 1.0

#98
It certainly looks from the extension API docs that this is a thing the world needs - a modern GUI shell that allows arbitrarily complex extensions to be written in a language people seem to like. Having looked around the docs as a very heavy emacs user, I am not totally discouraged - every keypress seems to point at a command, and if everything is rendered as HTML, I assume it is effectively infinitely customizable (would love to hear opinions from experienced extension authors). If, on top of that, it solves a lot of emacs' foibles, like threading issues, performance edge-cases etc, then I plan to keep an eye on it.

That said, the available extensions seem pretty bare. I don't see many mentions of REPL interaction, and there are no extensions for many languages. I'm glad it's getting attention, but I suspect it'll take a decade of loving care to bring up to the level of most people's emacs configuration. I see no reason that couldn't happen more quickly, though.

Re: Visual Studio Code 1.0

#100

I switched from Atom to VSCode for Go development on OSX a few weeks ago while Atom's Go plugin was going through a rough few days, and haven't been able to go back. The patterns of use take a little getting used to coming from Atom or Sublime, but VSCode gives me real static-language IDE features that "just work" simply by installing the Go plugin. Comparable functionality in Atom requires multiple plugins and I nev…

I never switched to Atom (from WebStorm), but I've made the switch to VSCode and I like it!

It just works. The workflow is fine for me, git integration is a plus. Compared to Atom, I don't need to try plugins to get descent functionality.

Actually, it's the first MS product I use in like... 10 years?

I used to be an emacs fan, I used to be an Eclipse plugin developer, I used to be a WebStorm user... now I prefer VSCode.

I love how it makes the best of screen real estate compared to WebStorm

Post reply on HN