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

271–280 of 487 posts

Re: Visual Studio Code 1.0

#271

Post by kingnothing »

jasonjei wrote: post #267
neves wrote: 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…

How do corporate developers test and debug things without the root password? In some cases, you need to be able to start Visual Studio in UAC mode, and debug an already running process...

I have no idea. I work for a very large software company and we all have root.

Re: Visual Studio Code 1.0

#272

Post by jahewson »

joeld42 wrote: 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/ ).

No, it's not based on Atom. Both VSCode and Atom are built on top of Electron but that's all they share in common. VSCode, unlike Atom, is lightning fast. In particular, it uses a very different rendering and plugin architecture.

Re: Visual Studio Code 1.0

#273

Post by klodolph »

throweway wrote: post #255
bitmapbrother wrote: post #246

Earlier quoted context omitted.

Notepad++ does work on Linux and also Mac's using WINE.

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.

Re: Visual Studio Code 1.0

#274

Post by aweinand »

bitmapbrother wrote: post #244
andwaal wrote: post #121

One of the things people does not seem to mention is the great debugging support you have in VSCode. The possibility to easy setup debugging with support for breakpoint, step through, inspection and so on. For react-native VSCode is the only IDE I have found which enables this. Previously one had to open Chrome and debug your apps from there, to have it inside the IDE makes it so more convenient. The same goes for No…

That's probably because it's using the Chromium code base. Those debug tools are from Chrome.

No, VS Code's debug support is not based on Chrome's debug tools since we try to support any debugger.

Re: Visual Studio Code 1.0

#275

Post by carussell »

avolcano wrote: post #116

When I started using TypeScript a couple weeks ago I briefly tried out VS Code, but the VIM plugin was really, really bad (worse than Sublime's was when I used it a few years ago). Now I'm on Atom, which has the best VIM support I've ever seen (haven't tried evil-mode, though) and seems to support a similar feature set. They felt about the same speed, too, on this 2013 Macbook Air. Regardless, other than that quirk,…

There is no "the VIM plugin". There are multiple extensions created by VSCode users. One of them just happens to have had the temerity to re-use the logo from Bram Moolenaar's project and slap the "Vim" label on their extension.

And it's working. Despite having messier code, performance problems, and fewer Vim features implemented, it has over 3x as many users as the next most popular one listed in the VSCode extension gallery.

Re: Visual Studio Code 1.0

#276

Post by nickjj »

I tried VSCode for the last couple of months and it didn't sell me.

It's noticeably slower than Sublime on a good workstation and it has a bunch of very minor annoyances that Sublime simply doesn't have.

When you encounter these annoyances dozens of times a day, it really turns you off from using it because a good editor should make you happy, not infuriate you.

For example, the way VSCode deals with multiple buffers and the sidebar is really poor. It tries to be cute and keep the sidebar's state in each buffer, but it's done really poorly and constantly disrupts you.

Re: Visual Studio Code 1.0

#277

Post by spdionis »

anamoulous wrote: post #137
evmar wrote: post #69

I'm your standard unix greybeard, the sort that uses org-mode to outline-structure their emacs config (that's actually what I do, not even a hypothetical), so I approached VSCode with skepticism. I have actually been really impressed. It's fast and responsive, even on Linux, and the TypeScript tooling is fantastic. I think with a bit more UI work (like vi keybindings) it could potentially become my preferred editor.

I'm chuckling (not in a bad way!) at the emacs user that prefers vi keybindings expressing optimism about a Microsoft editor written in a statically typed variant of Javascript. Progress is cool.

You made my day. Didn't even notice the irony... :D

Re: Visual Studio Code 1.0

#278

Post by JoBrad »

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.

> 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.

Re: Visual Studio Code 1.0

#279

Post by thepiwo »

anamoulous wrote: post #137
evmar wrote: post #69

I'm your standard unix greybeard, the sort that uses org-mode to outline-structure their emacs config (that's actually what I do, not even a hypothetical), so I approached VSCode with skepticism. I have actually been really impressed. It's fast and responsive, even on Linux, and the TypeScript tooling is fantastic. I think with a bit more UI work (like vi keybindings) it could potentially become my preferred editor.

I'm chuckling (not in a bad way!) at the emacs user that prefers vi keybindings expressing optimism about a Microsoft editor written in a statically typed variant of Javascript. Progress is cool.

additionally i would mention that this "Microsoft editor" runs with a web browser engine by google

Re: Visual Studio Code 1.0

#280

Post by taylodl »

crispyambulance wrote: post #149
coryrc wrote: 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?

"a few hours" ??? Come on, let's not pretend that EMACS is going to take "a few hours" to come to terms with and become more productive in than an IDE.

My 13 year old daughter came up to speed with emacs in a couple of hours. Now she's starting to realize she can make it into whatever she wants and make it work however she wants. She hadn't even thought about being able to program new functionality into an application. It's opened whole new worlds for her. Yes, emacs.
Post reply on HN