Live data from Hacker News

I’m switching from VS Code to VS Codium

ruky.me

21–30 of 343 posts

Re: I’m switching from VS Code to VS Codium

#21
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

Actually, I recently had to switch from CLion to VSC b/c I could not figure out how to enable rust-analyzer in the latest version of CLion. Also platform.io support is better in VSC. I love UX of interllij tho. I should say that I do agree with your main point.

Re: I’m switching from VS Code to VS Codium

#22
post #17

Earlier quoted context omitted.

Because some people don't necessarily want to tinker with emacs or vim for days just to get their perfect setup going

days? Surely, you jest, dear Sir. Proud emacs user for 21 years, still have to get some overlay function going just the way I like it. One of these days, I am going to get it just right.

Joking aside, I think that’s one of the great things about emacs: years will go by and i won’t touch my config. Then a new project or something will inspire me to get back into it. But since switching about a decade ago, i’ve never had the itch to move to a different “editor”

Re: I’m switching from VS Code to VS Codium

#23
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

> I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way.

Yeah, no. Don't get me wrong, Jetbrains IDEs are great. But they're not as easy to extend, its proprietary nature makes it hard to debug when writing extensions.

I use neovim primarily, but I've got licenses for a bunch of other editors (Nova, Sublime, used to have IntelliJ). I do sincerely try them, but I keep going back to open source, extensible editors like vim, emacs, vscode... because I invariably need to tweak something in the editor, and doing so in the proprietary editors can be so damn painful.

Now, you do make a solid point though. I guess I probably should donate to neovim. Guess I'll go do that!

Re: I’m switching from VS Code to VS Codium

#25
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

I use and pay a subscription for entire jetbrains suite. That said - vscode is miles better for JS/TS development IMO. In that world I don't want the full fat IDE experience because :

- it's slower - even some basic things like terminal rendering feels better/faster in vscode

- ecosystem is developing independently and so fast that IDE support can't keep up

- everyone else is using CLI centric workflows so it's maintained and tested

Re: I’m switching from VS Code to VS Codium

#27

Luckily, contrary to what the Microsoft hoard will tell you, there are countless respectful alternatives that were around before and will be around long after Microsoft turns it into some kind of pay to win thing with achievements.

Nitpick: s/hoard/horde/g

Nitpick: g flag not necessary here ;)

Re: I’m switching from VS Code to VS Codium

#28
post #16

I started using vim 13 years ago. Editors come. Editors go. Vim remains.

Yes. Learning Vim has had the best ROI for my time of any other tool I've learned over the years (git comes close though). Not only is it a great general-purpose editor, but it's available on every machine I interact with.

Re: I’m switching from VS Code to VS Codium

#29
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

I think it's an issue with some tools being "good enough" (majority of the free ones) + the feeling where you paid for something and it feels meh (or maybe it asks for paid upgrades, etc)

I tried Sublime Text once and then never bothered later. There wasn't anything that exciting about it that I couldn't do one way or another anywhere else.

The barrier to payment is higher if the comparison with a free tool is mixed. If there was one big thing the free ones couldn't do or they were much worse then there would be a case for paying for your tools

Re: I’m switching from VS Code to VS Codium

#30
post #20

What I find truly bizarre is how many software engineers, who are aware of how much they earn and how long it really takes to make software, are so resistant to paying anything for tools that make their job easier and faster. It blows my mind. Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way. For individual use, most of…

> but the Jetbrains IDEs are simply better and more mature in every single way

That's just not true.

I have access to the full Jetbrains suite for free, yet I still opt to use Neovim or VS Code/Codium for most languages.

Jetbrains IDEs are great in many ways, but are objectively worse on several metrics:

* slow startup times

* slow initial operations until the JIT is warmed up

* even once warm, you always eventually do something that lags or blocks the UI, maybe barely enough to consciously notice, maybe for several seconds; and it really affects user experience if you care about latency - it drives me crazy each time

* plugins: VS Code has a wide range of great plugins, many more than the Jetbrains ecosystem and especially when it comes to more niche languages or functionality, Vim/emacs but also VS Code are much more extensible in general

* keyboard warriors: the Vim plugin is fine, and you can configure the Jetbrains IDEs to do almost anything with the keyboard, but you need way more arcane knowledge in the form of memorized context-specific bindings, and you always eventually forget something and need to switch back to the mouse. Vim and emacs are just much better there. VS Code is actually also better, because the interactions are significantly more customizable.

* Wayland / tiling WM / input lag: Jetbrains products really suck on tiling window managers like i3 / sway because they use native windows for dialogs. They also don't support Wayland natively, so they run through X server emulation which hurts input lag and brings plenty of bugs like weird dialog behaviour. In general the input lag is quite bad on Linux, it seems to be much better optimized on Mac OS

There are plenty of valid reasons why you wouldn't want to use their IDEs, even if they provide more integration and superior refactoring.

Post reply on HN