Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

21–30 of 487 posts

Re: Visual Studio Code 1.0

#21
post #15

> Can we build a code editor fast enough that it doesn’t feel like you’re typing in a browser? Is this a jab at Atom? I like this.

Funnily enough I just installed VS code and there is lag as I type things in. Also bad font rendering compared to the rest of my interface.

smooth as butter on my macbook.

Re: Visual Studio Code 1.0

#22
Visual Studio Code could serve as a solid base for VS.NextGen. Following previously unheard-of paradigms (Unix) for Microsoft, Visual Studio could actually become modular, with each component becoming useful on its own.

Visual Studio Code would be the editor, Omnisharp the Intellisense platform, I think they were also developing some sort of common debugging interface, etc.

It would be a lot nicer than the current Visual Studio setup, where the installation drags in 6GB of cruft.

Of course, this would involve an internal power struggle between Visual Studio Code and Visual Studio proper, and I hope VS Code wins :)

Re: Visual Studio Code 1.0

#23
post #21
post #15

Earlier quoted context omitted.

Funnily enough I just installed VS code and there is lag as I type things in. Also bad font rendering compared to the rest of my interface.

smooth as butter on my macbook.

But you shouldn't need high end hardware to run a text editor.

Re: Visual Studio Code 1.0

#24
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, code writing feels amazing again, not the functional part, but the actual manual part.

I do not like vi because I primarily was learning web dev and I didn't really get my head around using vi effectively and still learn the web dev, so I am not a emacs/vi superstar as I have heard that both of them are fine text editors.

but for the people like me who don't or can't use terminal based editors, VSCode is quite literally the best.

The new Che project of Eclipse does seem promising, but the last time I tried installing it, it took around an hour, consumed GBs of my bandwidth and still nothing.

I am still Waiting for the day I'll be able to program in its entirety on my android device.

I used Atom but it is too slow, it is surprising that VScode and atom share the same ancestor but one is blazingly fast and Atom is so damn slow.

Edit: yep vscode didn't transform coding on unix, it merely changed it to some extent, and why the downvoting? point out where I am wrong, I'll get to learn!

Re: Visual Studio Code 1.0

#25

Earlier quoted context omitted.

There is an extension for vim mode: https://marketplace.visualstudio.com/items?itemName=vscodevi...

There are several actually, with different subsets of Vim. Sadly, none are as good as Atom's.

Link to the Atom module?

I'll take a look at making something similar.

Re: Visual Studio Code 1.0

#26
post #23
post #21

Earlier quoted context omitted.

smooth as butter on my macbook.

But you shouldn't need high end hardware to run a text editor.

I have a pretty generic Lenovo running Linux. VSCode is way more responsive (as OP says, smooth as butter) than Atom on it.

Re: Visual Studio Code 1.0

#27

Earlier quoted context omitted.

There is an extension for vim mode: https://marketplace.visualstudio.com/items?itemName=vscodevi...

There are several actually, with different subsets of Vim. Sadly, none are as good as Atom's.

Hello - one of the team members from VS Code here.

We built this extension sample to show the capabilities of the extension API - https://github.com/alexandrudima/vscode-vim.

We've done some work to improve the API for the extensions. We'd love your feedback. https://github.com/Microsoft/vscode/issues/3600.

Re: Visual Studio Code 1.0

#28
post #18
post #11

Earlier quoted context omitted.

You're asking for VS Code to be a completely different product. VS Code is a GUI text editor like Sublime and Atom. There's no reason for it to run in a terminal. Vim and Emacs are classical CLI based text editors. Are you asking for an alternative to those?

First you say: >completely different product then call them both >text editors emacs and (g)vim have a gui mode.

Yes, they're both text editors, but they're completely different classes of text editors. MS Word is also a text editor, but it would be ridiculous to fault it for not having a CLI. It's nice that Emacs and Vim have GUI modes, but I doubt they're the primary way users use those editors. Emacs/Vim and VS Code/Sublime/Atom fulfill different needs and preferences.

I'm curious about your answer to this: would you argue that MS should combine Word and VS Code into one text editor?

Re: Visual Studio Code 1.0

#29
post #20

Are there any emacs/vim users here who moved to GUI editors like atom or VS code? I would like to know what potential gains could come from using a GUI text editor.

I'm a longtime Emacs user and I dabble with atom and code. The main thing that I get out of GUI editors is that extensions generally just work. I spent a lot of time debugging emacs extensions to the point that I kind of expected extensions to not work right when I install them - especially ones related to autocompletion. Nowadays I use spacemacs to keep my package management sane, but it's inflexible and complicated.

I miss things from Emacs sometimes so I keep it around. I miss macros, I miss some of the more stellar Emacs packages (Tuareg for OCaml and Cider for Clojure in particular) but I do a lot of editing nowadays in Atom and Code.

Re: Visual Studio Code 1.0

#30
post #22

Visual Studio Code could serve as a solid base for VS.NextGen. Following previously unheard-of paradigms (Unix) for Microsoft, Visual Studio could actually become modular, with each component becoming useful on its own. Visual Studio Code would be the editor, Omnisharp the Intellisense platform, I think they were also developing some sort of common debugging interface, etc. It would be a lot nicer than the current Vi…

I have a gut feeling that this is in fact the plan. People keep asking "When can we have Visual Studio on OS X/Linux?", but I don't think that's ever going to happen: VS is so tightly coupled with COM and Win32 that they'd basically have to write it from scratch, or write an entire Windows emulation layer. But what they can do is gradually add features to VSC until it does most of the things you wanted full VS for: Intellisense, deploy-anywhere frameworks and debugging being the main ones. Doing it that way will probably be more performant too.
Post reply on HN