Yup, it’s definitely not a money thing. There’s plenty of tooling I do pay for, but I like hacking on my editor.
Sure, you need to go deep sometimes to tune things how you want, but hey, that’s what we do, right?
The important point is that people have different priorities and will make different trade offs. For me I like lean, fast and hackable. For others it’s that they don’t want to have to understand or configure it. That’s totally fine.
You're right that it's a totally different mindset. I was going to post a comment along the lines of "anytime I need to hack my editor, it's a waste of my time". That's where IntelliJ shines. It's so mature and functional out of the box, that I don't need to hack it. I came from Emacs where, once the initial fun of hacking it wore off, it was just a drag.
Re:I’m switching from VS Code to VS Codium
by sureglymop on Sunday June 12, 2022 @09:40AM
(#31714409)
I also like that Microsoft has made it incredibly easy to create an extension for VS Code. Most of the functionality usually doesn't even require code, just modifying the package.json file to add UI elements and such.
> 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.
IntelliJ IDEA Community Edition is open source under Apache License 2.0:
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!