Re:I’m switching from VS Code to VS Codium
by KineticLensman on Sunday June 12, 2022 @11:22AM
(#31715172)
> I can't afford > $1000 per year for a hobby.
In the UK a year's license for Photoshop, Lightroom and Bridge is approx £110.
Re:I’m switching from VS Code to VS Codium
by stjohnswarts on Sunday June 12, 2022 @05:21PM
(#31718398)
That doesn't help him if he doesn't live in the UK though?
Re:I’m switching from VS Code to VS Codium
by KineticLensman on Monday June 13, 2022 @05:23AM
(#31723007)
No but I can't believe US prices are almost ten times more expensive. If they are, he has a point
Re:I’m switching from VS Code to VS Codium
by FireBeyond on Sunday June 12, 2022 @02:37PM
(#31717024)
> I did a lot of Photoshop a few decades ago. I can't afford > $1000 per year for a hobby.
Adobe's Photographer Plan, which includes Photoshop and Lightroom, is $9.99 a month, $119 a year. Not sure where "over a thousand dollars per year" comes from.
Re:I’m switching from VS Code to VS Codium
by blip54321 on Sunday June 12, 2022 @07:41PM
(#31719339)
CS suite subscription. I also do illustrations, edit videos, do page layout, etc.
I used to have Photoshop, PageMaker (then Quark), etc.
Price is $55/mo, which comes out to $660 per year. Apparently, I misrecalled the price.
But I can't afford $660/year either, for a hobby.
Photoshop has not withstood the test of time for me. I did a lot of Photoshop a few decades ago. I can't afford > $1000 per year for a hobby. My old Photoshop files are dead, for all intents and purposes.
I do occasionally use decades-old, unmaintained open-source tools to open old files.
> 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.
Yes, it does. Cloud-based, you have no choice. Installed, increasingly, you have no choice either, since activation servers get taken down.
> 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.
It's a check-and-balance. I fix issues maybe in 0.0001% of the tools I use, but when I do, it's really important. With proprietary, you can work 70 hours per week for five years, and invest your blood and soul into a project, and be left hanging at the end, because you're reliant on someone else.
With open-source, you bite the bullet, fix it yourself, and keep chugging along.
> you'll never have a guarantee that a tool you invest time in or money in will be the leading tool in five years.
My experience is that "leading tool" is way oversold. The difference between JQuery a decade ago and React today is important, but even a huge difference like that won't make-or-break a business or a project. Technology is easy. If I needed to write my stuff in FORTRAN, I'd be less productive, but in the end, I'd learn FORTRAN and get the job done.
It's not a reason I'd pick proprietary over open-source.
What is important is all the other stuff. If you've bought something from Oracle or Google -- who are famous for this -- and they discontinue your product or ramp up licensing costings 100x once you've built your infrastructure around them, that CAN and WILL break a business (or a personal project).
Startups have a short half-life. Big businesses have a longer one ("No one got fired for buying IBM"). Open-source is eternal.
Legacy is important. If you don't believe me, have a look at all the FORTRAN and COBOL code still running on old mainframes. If you don't take long-term into account, you're unlikely to do anything lasting.