Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

311–320 of 487 posts

Re: Visual Studio Code 1.0

#311

Earlier quoted context omitted.

"Vim and Emacs are still superior if you want to put the time in, and both have non-terminal interfaces." I don't need an instruction manual to figure out how to close VSCode.

You also won't need an instruction manual for a lot of other things, because you won't be able to do them at all .

It's open source, I could do it.

Oh but that's needlessly hard and annoying? Well so are Vim and Emacs.

Re: Visual Studio Code 1.0

#312
post #309

Earlier quoted context omitted.

The one thing that kills gvim for me is the inability to have one session with multiple windows. I use it anyway.

How would that be better than opening multiple gvim processes?

I want to type :wa in one window, not four windows. I don't want to get an error message when I try to open a buffer that's already open somewhere else, I want it to just move the buffer to the new window (or alternatively, raise the window containing the buffer). I want to move buffers across windows and keep undo history and register contents. TextMate / Emacs / etc. have this capability, but I can't figure out how to do it in vim.

Re: Visual Studio Code 1.0

#313
post #90

Earlier quoted context omitted.

https://en.wikipedia.org/wiki/Atom_%28text_editor%29 Atom = 2014 https://en.wikipedia.org/wiki/Visual_Studio_Code VSCode = 2015 Am I missing something? Sure, MS had some preview online IDE thing before VSCode came out, but that's not the same thing obviously.

Yes you are. Please read the original blog post. [1][2] Visual Studio code was originated from "Monaco" team, dated back in 2013. Eletron (formally Atom-shell) was dated in Feb-March 2014.[3] [1] http://code.visualstudio.com/blogs/2016/04/14/vscode-1.0 [2] http://arstechnica.com/information-technology/2015/04/micros... [3] https://en.wikipedia.org/wiki/Electron_(software_framework)

So VS Code is based on Electron, but Electron came out the year after it?

That makes sense. I use things from the future all the time. /s

Re: Visual Studio Code 1.0

#314
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?

If the developer needs access, the product will suffer for a lack of it, and customers will eventually leave. If not, then it's just a petty complaint.

Re: Visual Studio Code 1.0

#315
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…

> Atom: [...] must install a column mode extension

Atom has Sumblime-Text-style column selection using (on Win) CTRL-ALT; it works very well and feels familiar for people coming from Sublime Text (which has been very popular for years now).

Actually, column selection is one of the things where I prefer Atom to VS Code (I love both editors for different reasons).

But maybe you needed some particular style of column selection?

Re: Visual Studio Code 1.0

#316
post #141

Earlier quoted context omitted.

Why spend a few hours over the course of 60000+ working hours to learn how to use more effective tools?

Because I don't need them, and would rather focus my attention on the part of the job I actually care about. The simplest tool which doesn't waste my time is the best. I have found that I would rather use a simple editor with no features that I never have to think about, and automate repetitive tasks using the same tools I already use for automating repetitive tasks: programming languages.

That just sounds like a self rationalization to me. "I don't need them" is something you say after you tried something and realized you actually don't need them. It doesn't carry any weight when you haven't even tried. Because when you do, it's just saying you don't want to try new things. I'm not saying you must learn these, I'm just saying you shouldn't lie to yourself.

Re: Visual Studio Code 1.0

#317
post #124
post #81

Earlier quoted context omitted.

What, exactly and without sweeping generalities, does it do that is a transformative step over Sublime Text or Atom? Or, hell, even Kate?

For example the Git integration is awesome and even better than Atom's (you can commit, push, ...). Of course you can do a lot with extensions, but at least in Atom's case they break a lot for me.

This is something I really do not understand. I can switch to my terminal, build, run, stage, commit, push all in like 5 seconds. As well as anything else I need to do in the terminal.

The only 'plugins' I use are a keyboard shortcut (cmd+space) which puts me in a terminal window and rupa/z[1] for jumping into a project directory.

[1] https://github.com/rupa/z

Re: Visual Studio Code 1.0

#318
The two highest rated comments in this thread make the little vein in my forehead pop out.

Microsoft is doing some very cool stuff these days so props to them. "VSCode has done the thing that nobody expected MS to do, change the way code was written in Unix/Linux" though? I believe the term irrational exuberance applies. Let's not get carried away here.

Re: Visual Studio Code 1.0

#319
It's interesting to see how VS Code / Monaco deals with long lines like hex data without slowing down. It kinda cheats by wrapping the line even when not in line wrap mode. There's a setting editor.wrappingColumn that controls the wrap length.

However, even after setting wrappingColumn to an arbitrarily large number, VS Code greatly outperforms Atom. The click accuracy within a long line is off by several characters in my quick test, but good enough.

I was never comfortable using Atom because it would grind to a halt whenever I accidentally opened any files with long lines. VS Code just may be the first MS product that I'll use on my Mac on a daily basis. Looking forward to testing it out on a couple projects.

Post reply on HN