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

Visual Studio Code 1.0

code.visualstudio.com

Post reply on HN
Print view View original

301–310 of 487 posts

Re: Visual Studio Code 1.0

#301

Post by falcolas »

Pxtl wrote: post #248
falcolas wrote: post #245

Earlier quoted context omitted.

To me (not OP), Python mode means syntax highlighting, code linting, code completion, and unit test integration from within the editor. There's a few other nice-to-haves, but those are the big ones.

In a simple text editor? My requirement would just be that copy/paste does intelligent things with indents.

Well, I can do this in vim, so... yeah. If it can't do these things (more specifically be extended to do these things), it's a text editor I'd quickly put down for one which can.

Re: Visual Studio Code 1.0

#302

Post by Skinney »

JoBrad wrote: post #278
Ace17 wrote: post #222

Earlier quoted context omitted.

Because the low-level modularity of Vim and Emacs gives you more control, by letting you choose the combination of tools you use ; instead of tying together the language(s), the compiler, the tag/completion engine, the build/project system, the debugger, the profiler, like many IDEs do. The sole concept of IDEs specialized for one language makes me cringe.

> The sole concept of IDEs specialized for one language makes me cringe. Can you explain this a bit? I don't see that Sublime, VS Code, Atom, etc. were made for one language, at all. As a little background, I've used vim for a while, then switched to Sublime Text, and am just trying VS Code. I find Sublime/VS Code/Atom to be far easier to customize than vim.

I'm pretty sure he is referring to Eclipse, Visual Studio and the like.

Re: Visual Studio Code 1.0

#303

Post by yoz-y »

Ace17 wrote: post #222
ngrilly wrote: post #197

Earlier quoted context omitted.

Why?

Because the low-level modularity of Vim and Emacs gives you more control, by letting you choose the combination of tools you use ; instead of tying together the language(s), the compiler, the tag/completion engine, the build/project system, the debugger, the profiler, like many IDEs do. The sole concept of IDEs specialized for one language makes me cringe.

I am a long time Vim user but I have never ever managed to get c++ tag completion work consistently there. At some point I just stopped trying - went to Qt creator and turned on Vim plugin there. The experience (for C++) is just vastly superior. The IDE integrates with CMake natively, the debugger is graphical and works, the symbol navigation over all project is blazing fast, I have real refactoring etc...

I still use Vim a lot, for JavaScript, for text, for remote sessions... But when a tool with real semantic highlighting and understanding of code is available (with a Vim plugin) then I'll take that.

Re: Visual Studio Code 1.0

#304

Post by Skinney »

dimgl wrote: post #295
Mikeb85 wrote: post #50

Earlier quoted context omitted.

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

While I do agree that VS Code is nothing revolutionary, suggesting Vim and Emacs are superior at this day and age makes no sense. Becoming effective at using these editors is very hard and not practical when there are so many other things any engineer worth their salt has to worry about. Most plugin systems for these tools are a nightmare. Vim has about three or four different plugin solutions and they all have diffe…

While I agree with regards to Vim, I don't really see how Emacs is hard and impractical. It doesn't have modal editing, you just open a file and write, and the plugin system is built-in.

I do, however, agree with you. Mostly because you can customize Atom and VSCode to have all the same benefits as Emacs and Vim. Except for running them in the console, which I know some people like having the option of doing.

Re: Visual Studio Code 1.0

#306

Post by 0xmohit »

toffeklang wrote: post #238
0xmohit wrote: post #220

This is not nice -- https://github.com/Microsoft/vscode/issues/5275

It's now an optional install: https://code.visualstudio.com/updates/vFebruary#_languages-c...

The link says: "or if you already have a project with C# files, VS Code will prompt you to install the extension as soon as you open a C# file.". As a matter of fact, it doesn't.

Re: Visual Studio Code 1.0

#307

Post by Skinney »

imtringued wrote: post #250
dubdubbub wrote: post #190

Earlier quoted context omitted.

> Try building a large webapp in vi and then comment. I've built several using mostly vim as the editor. > These days what you do is more important than what you use to do it, use vi or emacs or some shitty text editor I mean that's a cute opinion, but both vim and emacs are much more powerful and flexible than eclipse, intellij, visual studio or other similar crap. > but it isn't the thing to be used for a large web…

>vim and emacs are much more powerful and flexible than eclipse, intellij, visual studio or other similar crap. Nice claim, now do you have data to back up your claim? Meanwhile let me ask you a few quick questions. Okay, how do you automatically organise imports in emacs? Can you jump to the declaration of an expression with just pressing one button? How do you extract functions or values quickly without having to f…

Yes. There are plugins for all of this. When I was using Emacs, I could use omnisharp to navigate files using, yes, one button. There are refactoring tools for emacs as well, though I'm usually fine with just using multiple cursors (also a plugin) so I haven't tried them out.

All my billable work the last 3 years have been with Emacs (ok, except for the last month, that has been Atom). I have never missed the functionality of an IDE.

Re: Visual Studio Code 1.0

#308

Post by varjag »

dom96 wrote: post #202
thewhitetulip wrote: post #175

Earlier quoted context omitted.

I am fine with it taking as much memory as it took. It is a great replacement for notepad, but that's what it is. wrong tool otherwise for a large project.

How much memory did it take? I assume that gedit would be very lightweight in terms of memory usage, maybe you hit a memory leak?

Oddly enough, on my machine a fresh gedit instance had bigger memory footprint than modestly tricked out emacs24.

Re: Visual Studio Code 1.0

#309

Post by gcr »

klodolph wrote: post #273
throweway wrote: post #255

Earlier quoted context omitted.

Seriously try gvim. Not vim where you need a long ass cheat sheet just to create a new tab or move between splits. But gvim where you can be productive and use the mouse and menus when necessary.

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?

Re: Visual Studio Code 1.0

#310

Post by jhasse »

jessegreathouse wrote: post #223

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?

Post reply on HN