Earlier quoted context omitted.
> 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 them are They just aren't, I would not switch to Jetbrains from VSCode even if it was free. It's not a question of pricing and Jetbrains themselves started to realise it since they are building some VSC clone (forgot the name right now)
Their new VSC alternative name is fleet and I don't think they confirmed it will be free like VSCode though.
I’m switching from VS Code to VS Codium
211–220 of 343 posts
Re: I’m switching from VS Code to VS Codium
#212Earlier quoted context omitted.
> Maybe you are the exception but I find that 99.99% of the people who use the "it's open source so I can modify it" argument never so much as look at the code let alone consider making modifications. It's about having the option. It shouldn't be the case that you have to modify your editor's source code, but if it's open source, at least you can do that. With a proprietary editor, you're screwed.
How are you screwed? If you don’t like something, switch editors. I don’t understand why some people self-flagellate and don’t just pick the right tool for the job. I’m very pro-open-source but that doesn’t mean proprietary software is all evil, you’ll drive yourself crazy if you take that to its logical end.
As an emacs user: One does not simply switch editors.
If you can just switch from emacs to vscode, you likely were using it at a very surface level.
Put another way one could switch from Java (jetbrains) to Scala(emacs), but still be writing Java code.
I think that there are users that treat IDEs and editors as a lowest common denominator where switching would be easy and others who build workflows on editor-specific features.
If you are the former, switching isn't a big deal.
Re: I’m switching from VS Code to VS Codium
#213What 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…
Some of us reassess spending patterns over time (and even there some do it more frequently than others).
So you have this spread where a part of the population is still very frugal and some part is almost price insensitive and then everything in between.
Love to hear what other folks think.
Re: I’m switching from VS Code to VS Codium
#214What 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…
Re: I’m switching from VS Code to VS Codium
#215What 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…
Re: I’m switching from VS Code to VS Codium
#216> I was increasingly getting upset about their extension marketplace, where there is an increased number of extensions starting to sell pro versions of the extensions we used for free. This is actually great news. Some extensions, especially language ones, are very poor, and paying for them (if someone makes a commercial version) is the only way to guarantee a good development experience. Ruby is an example, and swit…
The reason we do open source and free software is to make life easier for everyone, including your job. It standardizes practices and prevents mudball codebases comprised of black box libraries and tools.
Not to mention that selling of extensions is like selling of game mods. There's tons of stolen code.
Re: I’m switching from VS Code to VS Codium
#217What 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…
> 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 them are After a particularly bad tooling week (js supply chain problems, plugin problems and more than the usual amount of DB changes) Our dev team made the unanimous call to move require all developers to use Jetbrains IDEs instead of the…
Wow, it'd be time to look for a new job.
I think having a blessed option and understanding of "use what you want but don't let it affect deliverables" is best.
Re: I’m switching from VS Code to VS Codium
#218> I was increasingly getting upset about their extension marketplace, where there is an increased number of extensions starting to sell pro versions of the extensions we used for free. This is actually great news. Some extensions, especially language ones, are very poor, and paying for them (if someone makes a commercial version) is the only way to guarantee a good development experience. Ruby is an example, and swit…
reminds me when Bethesda tried to introduce paid mods on Steam. I was greatly excited about that for the reasons you state. But the gaming community being physically or mentally at an age of 14 prevented that with quite an outreach. Would've thought someone with enough braincells to learn programming would look at this differently, but there you have it.
Mods work better in an open and free environment that lacks monetary incentives.
Re: I’m switching from VS Code to VS Codium
#219What 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…
Re: I’m switching from VS Code to VS Codium
#220Earlier quoted context omitted.
I think most of us value our freedom more. Most people don't think of it in terms of freedom, but freedom it is. With proprietary software: - You don't know when it will disappear or be discontinued. Even your paid-for existing version stops working when the activation servers go down. - You might be forced into an "upgrade" which breaks something you rely on - That's not to mention issues like being able to fix bugs…
Most of your points also apply to open source software, and aren't strict requirements for proprietary software. - discontinued: Atom just got discontinued. It's open source. Photoshop on the other hand has withstood the test of 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. - Being able to fix your own bugs is…