Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

321–330 of 487 posts

Re: Visual Studio Code 1.0

#321
post #310

I can't find the option to open a terminal in the editor. Am I missing something? Needs a terminal pane.

You can run commands via the task runner. If you need a real terminal - why not simply open one and split it next to Code using your window manager?

Why not simply add a terminal pane to the editor so I don't need to?

Re: Visual Studio Code 1.0

#322
post #281

Earlier quoted context omitted.

>> and both have non-terminal interfaces. > I don't need an instruction manual to figure out how to close VSCode. To close GVim, you click the 'x' in the upper right/left corner, like any other window.

And how do you install extensions for GVim?

You put extensions into the proper folder, or use a tool like 'Vundle'. Yes it's slightly more difficult than using Atom, but anyone who can use a tool like Git or Cmake should have no problems figuring it out.

Re: Visual Studio Code 1.0

#323
post #50

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,…

Ummm, no. VS Code is a decent editor, nothing more. It certainly doesn't transform the way code is written on Unix/Linux. Vim and Emacs are still superior if you want to put the time in, and both have non-terminal interfaces. They can also be both customized to be whatever you want them to be, there's not really a limit to their functionality except what plugins are already written. Ditto for Atom, though of course,…

> Vim and Emacs are still superior

I think the parent was talking about modern text editors such as Sublime, Atom, Brackets etc.; Vim and Emacs are completely different beasts (note: I love both).

Within the category of modern text editors, VS Code is in my opinion revolutionary in several ways - I will give you three examples

The first feature that I find "disruptive" is the way VS Code offers a standardised interface for debuggers, hence debugger plugins are much easier to create - and you can see that VS Code already has debugger plugins available for many languages: https://marketplace.visualstudio.com/vscode/Debuggers?sortBy... the availability of such plugins for Atom and Sublime Text is not nearly as good.

The second aspect where VS Code changed the game is the clever way it leverages Electron (the framework it's made with, Atom is made with Electron too) - while creating clever workarounds to known Electron bugs - e.g. VS Code, unlike Atom, does not suffer from this bug https://github.com/atom/atom/issues/10720

The third aspect is the git integration - since Atom is sponsored by Github, you would think it has the best git integration out there - but VS Code has gone the extra mile by giving you a great user-friendly UI interface for staging and committing (yeah, I know, anything more complicated than git add -A requires the command line - the fact is that nearly 50% of all the git commands I type are git add -A, LOL).

PPS I totally agree with you about the importance of tooling. But e.g. if you have a debugger that does not have an interface to your editor it becomes hard to set breakpoints. So the editor needs to integrate with your tools and VS Code is great at that.

Re: Visual Studio Code 1.0

#324

Earlier quoted context omitted.

Please, elaborate how VSCode changed the way we write code on Unix? I mean, repeat your statement out loud and ask yourself how big statement you just said. No way in hell how VSCode change the way we write code as much as you stated, no way even Atom did that. Like it or not TextMate came first, and soon after that Sublime Text took over. Yeah, like it or hate it, ST with it’s very well known default monokai theme c…

At work I write Scala and the IntelliJ Scala support is simply unbeatable. It's refactoring engine etc. is fully Scalafied -- when you paste Java code, there's even a "translate to Scala" function offered. I use a "vim mode" plugin that allows me to hope around with 25j and such. For my personal project (which is in Rust) I use Atom, which is new for me, but I find to be really impressive. Both its plugin system (whi…

Have you tried this plugin: https://marketplace.visualstudio.com/items?itemName=savioris... ?

Re: Visual Studio Code 1.0

#325
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 use vim, but Atom now primarily. Atom because of plugins: Beautify, Minimap, Markdown Preview, Convert css-to-inline, editorconfig, easy to split windows, and easy to search for text in whole directory. VSCode can't split windows horizontally but it has a nice node debug. However I usually just "node debug" in the terminal. Atom also has a Racer plugin which is nice for Rust.

Re: Visual Studio Code 1.0

#327

Does anybody else use several editors all the time? I use Emacs, Vim, Eclipse, Atom, and Intellij. I don't stick to one. I wish I could stick to one editor but there is always some editor that does a way better job at a particular task. Each editor has its killer feature. I have tried turning emulation of emacs/vim on many editors to provide consistency and its never been really good. Thus I have several "default" ke…

I'd wager a lot of people (myself included) who prefer one editor really do this because it's just easier to mentally handle. Because of that I wouldn't necessarily believe them (or again, me) if they told you they're more productive this way. I don't think It's necessarily true.

It's pretty much required to keep CUA hotkeys in your head in some form. So I find switching between Emacs/Eclipse tolerable and kind of necessary if I'm doing Java.

I think switching between Emacs and Vim is a good idea but more a question of keeping your hand/mind coordination flexible for different input paradigms. I'd be skeptical that they're really that different in terms of efficiency for a task, but I'd say learning both really well will make you more efficient in general.

Re: Visual Studio Code 1.0

#328

Earlier quoted context omitted.

> SCode 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 I mean, its okay if you don't have experience with vim or emacs, but why spew uninformed bullshit when any semi-knowledgeable linux/unix dev knows that vim and emacs run laps around vscode, sublime, etc.

Try building a large webapp in vi and then comment. These days what you do is more important than what you use to do it, use vi or emacs or some shitty text editor, but eventually you need a real IDE with a GUI, vi is great, I love it, but it isn't the thing to be used for a large web app. >ut why spew uninformed bullshit when any semi-knowledgeable linux/unix dev knows that vim and emacs run laps around vscode, subl…

I've built large web apps in vim.

Honestly you sound very misinformed. Vim is capable of pretty much everything that VS code is capable of and then some.

Re: Visual Studio Code 1.0

#329

Earlier quoted context omitted.

Just wanted to say I find Notepad++ to be an excellent tabbed editor, especially for XML or SQL. I use it on windows all the time and really miss it on OS X where I find Textmate to be a bit awkward.

I've been a long-time fan of Notepad++, but it's a text editor. You can extend it to make it work better with specific programming languages (e.g. here's a post I wrote 10 years ago about adding language support http://weblogs.asp.net/jongalloway/creating-a-user-defined-l... ) but it's fundamentally a text editor. VS Code is a code editor. It has IntelliSense (not text-matched autocomplete, IntelliSense), debugging s…

Notepad++ is very useful but I wish some features would be updated. The dialogs are awkward to use at times. The XML for defining custom syntax highlighting is atrocious. It's like they took a pre-XML config file and shotgunned tags into it without planning a rational format. Keywords are specified using long strings delimited by CR/LF entities for no good reason other than to destroy readability. It would be nice if an more modern hightlighting engine could be inserted as an alternative to the clunky ad-hoc design it currently has.

Re: Visual Studio Code 1.0

#330
post #130

VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…

"I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me" Sounds like an undeserving environment for a developer. Why not vote with your feet?

Just because SV is an employee's market that doesn't mean that everywhere is, or that everybody has a lot of mobility in their personal life.
Post reply on HN