Eugenia

Linux Mint is actually fast, and uses half the RAM of Fedora (see shots: https://files.mastodon.social/media_attachments/files/114/653/604/229/121/661/original/6d60399683784c13.png and https://files.mastodon.social/media_attachments/files/114/761/028/826/681/916/original/32f1c276089be277.png ). With a bit of tweaking, and using the Cinnamenu menu instead of the default one, it feels really good. On Fedora KDE I got updates every couple of days to the excess of 1 GB. I’m on 50mbps internet, and that was too much for me.

I hope they support the Orange Pi RV2. It’s the best middle of the road, affordable, consumer-based risc-v sbc right now.

There is nothing like CapCut for Linux. There’s Resolve, LightWorks, Shotcut, Kdenlive and the less evolved, Openshot. That’s it, all the other editors found online or suggested here are nowhere near completion. Also, none of them have the feel of Capcut with its AI and advanced automatic features. If you want to go open source, I’d suggest you learn to use kdenlive. It’s good enough with manual workarounds, as long as you don’t shoot in 10bit or in RAW. If you really require automatic AI stuff like in Capcut, stay with Windows/Mac or a tablet. That’s the reality.

I run mint on 4 gb ram without issues. Sure, I’m careful to not open too many apps or too many tabs, but they all work fine. Only 4k video editing is undoable on such a machine. I also have a 4 gb swap partition, but I’m careful to lay off programs when I see it get hit.

My mom uses xfce on a 2 gb laptop. For her is enough, because she only knows how to open a single tab on a browser (mostly fb or yt).

I think this already bites people, it has started, it’s not in September but now?: https://x.com/rogerioperdiz/status/1946873449537798582

You think it’s the screen/hdmi at fault, but it might not be. I’ve had the problem with two laptops in the past (the bug was with all distros I tried), and in one case it was a BIOS that Linux didn’t like, and the second one was the internal wifi that its linux driver was buggy. For the first laptop there was nothing to be done, so I disabled sleep completely in the bios, while for the second one, I disabled the wifi modules in the kernel’s blacklist, and then used a usb wifi that I knew it worked better. Both cases were appearing as a dead screen, but it wasn’t the screen/hdmi/gfx card to blame. In yet another case, with a thinkpad laptop, the wake up was working, but it would wake up 30 seconds later than anticipated. In that case, it was the fact that its thunderbolt was dead (hardware had gone bad), and only when I disabled it in the bios completely the laptop would wake up correctly and fast.

In all those cases, I had to look at the kernel logs to see what was the issue. There were traces of the problem of which hardware exactly was creating the problem. It might look like a screen/hdmi problem, but most of the times, it’s not.