I totally agree with you on the Linux side. However, I first got into Linux by using it in Virtualbox on Windows. In the Windows world, as far as I know, it’s the easiest-to-use free-as-in-beer^1^ hypervisor, so long as UEFI support has improved since I last used it.
1: I say this because of the non-libre extension pack.
As I have learned the hard way, it truly is.
I agree with Mint. I think Ubuntu has kind of devolved though, and PopOS is the better way to go. Fedora's good too these days.
My recommendation is to try out a few distros in VirtualBox before switching - this was my process, and it can be very gradual.
I don't use Mint, but I would guess that you could change your repos in /etc/apt/sources.list, run sudo apt update, and then sudo apt full-upgrade. Just make sure the full upgrade isn't doing really dumb stuff like deleting a bunch of programs.
I could be completely wrong and this could be terrible advice, but this has become the wisdom for me when I use Debian Testing. Of course, I just did straight sudo apt update after Bookworm was released and the upgrade to Trixie went mostly fine. I have never upgraded between stable versions, so I may not be one to say.
I installed Pop in a VM (I use Debian usually) and was surprised how usable it was sans-graphical acceleration. Ubuntu is pretty much unusable these days in a VM - it can literally sometimes take 30 seconds for a button press to register where it works instantly in VM Pop or Fedora.
While some of this can be a problem, I feel like using podman automatically disqualifies you as a regular user.
I think the more accurate title is “Linux is harder for medium power users who are already used to an operating system.”
I honestly feel I am unqualified to say how easy Linux distros are, as I often think to do things that a normal user wouldn’t, thus breaking my system in a way that doesn’t mirror what a regular user would experience.
True. Industry entrenchment would be a big issue. I can think of two ways to try to fight it. The less viable option would be trying for PSD support, which would be a lot of work. The other option would be to write a Photoshop plugin to allow working with the new file format in Photoshop. This might be annoying to end users having to deal with the format, but also easier developer-wise because you could make sure Photoshop handles rendering right; you'd just need a way to warn about operations in Photoshop that can't be converted to the new FOSS program's native format.
Not exactly “full of” - it was more like 3 classrooms with 30 each. Still a lot of Macs, but keep in mind this was a high school of 2000 students. Also, I’m pretty sure the Macs were paid for with grants for the visual arts programs rather than standard public funding.
In some ways this is true. However, I feel like in the case of Adobe, someone needs to take another shot at a good FOSS image editor. Adobe is really starting to mess itself with generative AI; knowing many artists, they hate generative AI image tech as a threat to their job, so I find it weird that Adobe is alienating one of their largest user bases. I find it weird how Inkscape is really good and has evolved (I actually switched to it from Adobe Illustrator and don´t regret it), while GIMP has barely changed in 10 years.
I get that some parts of an image editor are complex, but at some point, it's just a chain of mathematical operations. Maybe I'm wrong, but when I get the time, it's almost tempting to take a stab at the issue.
I think it depends. If a school has a laptop for each student, it is most certainly a Chromebook. However, a lot of schools also have a mix of systems. In elementary school, I was taught to use Microsoft Office on Windows, for instance. At my high school, all the students had Chromebooks, but there were also some labs with Windows machines; graphic design, photography, and film classes had labs full of 5K iMacs.
I added an apt repo someone had created. I've checked how it works, and it's just a CI routine pulling the latest Discord package for the website and throwing it in a repo.
According to the repair manual, my Wi-Fi card is actually replaceable, at least physically. I don’t know if Lenovo still does BIOS whitelists of cards like they used to (I think they did remove it a few years back.), but their OEM parts website has a diverse selection if this fix were ever to break.
I’d say other than the bottom being a bother to remove (and the keyboard not being designed to be replaced, though after some research, it seems possible), this is a surprisingly repairable laptop for how recent it it. It has dual SSD bays and a DIMM slot.