I’m switching from VS Code to VS Codium

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

- Worse performance

- Worse plugin ecosystem

- No LSP support

Also, their stance on supporting other ecosystems. While I completely understand their standpoint as a business, I prefer VSCode team's approach to this.

https://intellij-support.jetbrains.com/hc/en-us/community/po...

https://discuss.kotlinlang.org/t/official-support-for-visual...

> Why are so many resistant so other people earning a living particularly when the payoff (ie time-saved) is so easily quantifiable?

Is it, though?

Flashbacks?

> Does this affect existing features? > > No, the introduction of GitLens+ has no impact on existing GitLens features, so you won't lose access to any of the GitLens features you know and love. In fact, we are heavily investing in enhancing and expanding the GitLens feature set. Creating an account simply gives you access to a subset of new features that will enable you to get even more out of Git in VS Code!

I haven’t used it and only heard of it last week, but the extension’s page you linked to seems decent enough for me to try it out.

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

We're not resistant to paying, we're resistant to rent-seeking. I would, and have, happily buy a piece of software I use regularly.

What I will not do is a pay a monthly fee in perpetuity for a piece of software that I cannot truly own, where features I need can be removed on a whim and where I am prohibited from adding features I want. I also find the massive amount of tracking and general disregard for privacy appalling, but that's a missive for another day.

The subscription model that's become predominant is a nightmare and is increasingly user-hostile. Why is it so surprising that a lot of folks don't like it?

So in summary, I will gladly pay for software when:

1. I can pay up front an actually own it

2. I can see the source code and modify it

3. It does not track or otherwise monitor me

None of these things are a big ask.

I used VScode for 2 years then bought Jetbrains for 3 years, now I'm switching back to VScode. I feel vscode is getting better plus it is open source.

Does open source matter a lot? maybe. For example, Jetbrains' Teamcity is still under investigation for Solarwinds hack which is a concern, plus I think a while ago the core developers are mostly from Russia at Jetbrains. Those combined with an improved vscode made the switch for me. I mainly use vim in practice but I do need a GUI IDE once a while.

> discontinued: Atom just got discontinued. It's open source. Photoshop on the other hand has withstood the test of time.

But if I want to use Atom I can fork it, or keep the source around. It doesn't go away from my environment until _I_ say it does. And Photoshop has become more and more user hostile over time.

> Audacity's 3.0 update removed a feature I relied on. I wasn't forced to update to it, sure, but proprietary software doesn't force updates either.

It is impossible for libre software to force updates, and quite possible for proprietary software to do so. It's part of what pushed me away from Windows in the first place, and other apps (especially web, but also other stuff) also do so.

> Being able to fix your own bugs is a great part of open source! But not something most professional software developers really expect to do for their IDE.

While it isn't expected, it's definitely a nice-to-have.

> open source formats are probably more resilient than closed source, but I would argue many proprietary formats are also pretty resilient. Code is also based on plain text at it's core, like latex, so it's always going to be pretty resilient.

But with libre software, I don't have to wonder. Even if a project uses an obtuse, obfuscated binary format I know I'll still be able to read it (with a little prep work). With code this is less of an issue - as you note - but you did mention Photoshop earlier, so I'm assuming we're talking about software in general.

> you'll never have a guarantee that a tool you invest time in or money in will be the leading tool in five years.

I don't need it to he leading, I need it to be around and functional. Pretty confident Emacs/(n)vim will be here a couple decades longer at least. I believe this was GP's point - that it's better to worry about what will work best in 10 years, not what's standard now.