Earlier quoted context omitted.
Quoted post unavailable.
My experience with CLion was that it was agonizingly slow to do anything. It stuttered scrolling through even a small C project. I don't know exactly what it was doing in the background, but it constantly had fans running. Long after it made sense for it to be indexing. In fairness, though, this was probably four or five years ago. But it sure colored my opinion of the software. Also this isn't exactly unheard of as…
I’m switching from VS Code to VS Codium
241–250 of 343 posts
Re: I’m switching from VS Code to VS Codium
#242I went backwards, from VS Codium to VS Code, because VS Codium does not support all extensions, like PyLance or Remote - SSH/containers. I like freedom, but I like getting things done more.
Re: I’m switching from VS Code to VS Codium
#243Earlier quoted context omitted.
> 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 proprie…
> 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. This is technically true, but in 99% of the cases is not realistically true. Most developers who use said FOSS external dependency do not want to actively maintain it themselves.
Re: I’m switching from VS Code to VS Codium
#244I went backwards, from VS Codium to VS Code, because VS Codium does not support all extensions, like PyLance or Remote - SSH/containers. I like freedom, but I like getting things done more.
It might be worth contacting these extensions' creators. If you already have the `.vsix` file for the VSCode marketplace, publishing to open-vsix is really super simple (create an account once, get a token, add a few lines to your publish script, e.g. https://github.com/prisma/language-tools/blob/94e4cd612d03ef... ). Some just do not know about it.
Re: I’m switching from VS Code to VS Codium
#245Earlier quoted context omitted.
I agree with you for the most part, I write this while running Matlab simulations in the background. Having tried to reach similar levels of productivity with Julia or Python, I find the FOSS environments always fall short in the tooling environment. Not to mention the importance of documentation. However, I can't help but take exception to Vivado and SOLIDWORKS being good software... While powerful, they are both in…
The only use case I can think where matlab beats Python or Julia is when one has a lot of legacy code. It's funny that you mention documentation, the amount of documentation found around Python is typically much better than matlab. Matlab toolboxes are really hit and miss, some are very good, but there are some really crappy ones. If you actually need to include more traditional programming features matlab becomes a…
https://docs.scipy.org/doc/scipy/reference/generated/scipy.s...
https://www.mathworks.com/help/signal/ref/pwelch.html
Maybe my bias is showing, but I find the Matlab documentation to be superior. However, that is nothing compared the quality of the IDE which is critical when doing scientific compute. When I was re-evaluating our simulation environment at work, we looked at PyCharm. The plotting capabilities alone made it easy to stick with Matlab, even at the orders of magnitude higher cost.
N.B. This is my experience in an Optical Communications R&D environment.
Re: I’m switching from VS Code to VS Codium
#246> 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…
Re: I’m switching from VS Code to VS Codium
#247> 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…
> 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. So, "I'm a professional developer, but I don't like other programmers getting paid for their extensions (that I do, nonetheless, find valuable, and want to use)"?
Truly a sight to behold!
Re: I’m switching from VS Code to VS Codium
#248Earlier quoted context omitted.
That's paying for convenience which is a different behavior.
What is the convenience?
- you don’t have to stock ingredients for food/drinks you may not like or prepare often
- you can’t make a din without annoying the neighbours
- you don’t have to rent a space just to play loud music or dance
- you don’t have to make a music selection
- you don’t have to invite large numbers of people who don’t know each other to help make new connections
- you don’t have to clean up every time anyone pukes
Re: I’m switching from VS Code to VS Codium
#249What 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…
> 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…
So by your definition, a stable salary writing software is a form of “rent seeking” in open source, but totally acceptable as a job?