Hacker News new | ask | show | jobs
by adastra22 1068 days ago
What is this speed you speak of? I developed in vim for a decade, then eMacs for another decade, before finally moving to VS Code. I’ve never been as productive with vim/eMacs as I am with Code, or Visual Studio proper / XCode when I have cause to sue them.
4 comments

Editor speed (i.e. responsiveness), not developer speed (i.e. productivity).
Having used all three myself I bounced off VS Code hard because getting a usable Ruby setup with all the fixings like irb integration and sorbet ls was multiple days of frustration and still not working right compared to it just working out or the box with Doom Emacs. What’s the happy path that made VS Code work so well for you? I’m curious in case I did it wrong.
The ruby stuff for vscode isn't quite up to quality and I find I turn a lot of it off. I've had a good time with the fuzzy LSP https://marketplace.visualstudio.com/items?itemName=Blinknli...

I think sorbet hasn't got the critical mass of devs using it so tooling is hit or miss. And I personally don't like it even though I'm well onboard with typescript.

What is irb integration? I tend to avoid that kind of thing and just do it in the terminal regardless of which editor I'm using.

> What is irb integration

Stuff like having code locations in irb hyperlink back to the code buffer in another window.

May I ask what makes you more productive with vscode? Coming from decades of emacs I'm always wondering if I should try it. If anything because emacs is a huge time sink. You can get lost customizing it to your needs and forget that what you needed in the first place was get the work done.
It's basically all the benefits of an expertly configured and finely tuned emacs setup, except maintained by other open source developers so competently that your only time spent configuring your editor is clicking "Install Plugin" the first time you open a file written in the language/framework you use. Sensible defaults, batteries included.

The only downside is that as a web tech app it can have some noticeable latency. But on a beefy dev laptop or workstation the difference shouldn't be noticeable.

Surely you jest, Visual Studio proper is absolute garbage
Maybe for your needs. When I worked as a game developer was amazing for visual debugging gigabytes of runtime data generated by a game engine with millions of lines of code. I could endlessly click through class hierarchies to see what interconnections arise at runtime, and setup all kinds of complicated breakpoint conditions. Obviously you can do all this with gdb or lldb as well, but in my experience it never approached the productivity boost of a graphical debugger.

Visual Studio is a bit shit outside of games, .net, or windows desktop software though.