I feel like most people who use Nvidia on Linux just got their machine before they were Linux users, with a small subset for ML stuff.

Honestly, I hear ROCm may finally be getting less horrible, is getting wider distro support, and supports more GPUs than it used to, so I really hope AMD will become as livable ML dev platform as it is a desktop GPU.

Assuming she hasn’t bought it yet, please research that Yoga first. It might work fine, but it could also end up being a miserable experience.

You can check https://linux-hardware.org/ for the model or a similar one.

Reminds me of when I threw Debian Trixie on my freshly decommissioned high school Chromebook - with Bcachefs. Luckily, it wasn’t a daily driver, just a toy; the thing had an AMD Stoney Ridge APU that you had to use special compiler flags on to get working.

I think good, truly easy video editors are a dying breed. I loved Windows Live Movie Maker - rest in peace.

These days, I think it’s worth it just to learn a video editor. A lot of the skills transfer; I haven’t used DaVinci before, but I’ve used other major proprietary professional video editors like Adobe Premiere and Final Cut Pro - the skills transfer. Just search how to do a thing you want to do a few times, and you’ll find it gets easier.

As others have said, I think KDEnlive is quite good; I haven’t had a huge amount of stability issues. From what I remember (granted, I may be out of date), OpenShot felt really jank in general; I used Shotcut for a while but had stability issues and UI annoyances. Comparatively, I enjoy KDEnlive.

You can self-sign and self-enroll secure boot keys. Can’t say it’s an easy process, though - I had a lot of misery with it on my Surface Go 1st Gen. Might be better on my Thinkpad.

As I’ve commented elsewhere on this post and others have said, this is a change that affects pretty much no one. I didn’t even know MBR (legacy BIOS) partition tables on UEFI boot was possible, honestly.

By no longer putting in the effort to maintain this bit that no one uses, work can be put to something someone uses.

Also, with Linux, specific distros can get encrapified (kind of happened to Ubuntu), but as others have said, there’s usually always another distro to jump to at worst.

For those panicking about it, this is not something you need to worry about. Here’s what this actually does:

Enforce the use of GPT partition tables for all UEFI-based Fedora installations for x86 architecture. This removes support for installing Fedora in UEFI mode on MBR-partitioned disks on x86 systems

You probably have already been using GPT on your UEFI system since you had a UEFI system. Even if you somehow were using MBR, this probably;

1. Won’t break existing installations, as it’s merely support for installs of this type
2. Would not be a problem even if somehow the broke existing installs, as it’s not difficult to convert MBR to GPT.

As much as I resonate with the issues, in this case, this isn’t what they’re doing at all.

This drops support only for UEFI on the MBR partition scheme typically used by a BIOS setup, which I honestly didn’t even know was possible.

This ends support for no hardware - almost all distro installations on UEFI have defaulted to GPT partition tables for a long time.

That’s not what this is saying.

It’s only support for UEFI on the old MBR partition table - GPT partitioning has been the default for ages now.

Honestly, I rather like the default XFCE terminal. In fact, I was using it even before I used XFCE back when I was just playing with the default GNOME in VMs before I daily-drove Linux.

Is this xfce-winxp-tc? I ‘ve played with it before and it’s awesome.

However, I don’t use it because while the XP start menu replica is cool, I need a Win7-style search bar, and Whiskermenu sticks pit like a sore thumb here.

I think a 7 replica would be awesome, but I think some parts of Aero can only truly be replicated with a new WM and DE, such as the color changes in the taskbar for different applications. Many themes just fall short - proportions and effects are slightly off and such.

I think the main other distro I used in that VM at that time was Fedora 37 at that time, which should have also been using Wayland. I had made the VMs because I was working on Debian packaging for an application I liked and wanted to make sure the modifications I made didn’t break it on other distros.

I’m not necessarily a “Wayland is the embodiment of evil” kind of guy, but I love XFCE and pretty much won’t leave it unless it dies, meaning I’m on Xorg until they port XFWM4.

Not really, but I switched from Qwerty to Workman years ago, though I can live with Qwerty if I have to when it’s on someone else’s machine.

I use Workman because I found Colemak rather hard to learn, mostly because of the position of S being one over from where it was on Qwerty.

In order for them to be allowed on exams, I ghink they’re required to have a non-QWERTY layout.

Linux (and I think maybe even macOS) can do Ctrl+Shift+U, and then you type the Unicode hex number.

Discord also has an app from Linux - you can get it as a Flatpak (an official one) or as a native package, although they don’t provide a repo for native packages and expect you to manually download a package file every time there is an update.

For the native packages issue, someone created an apt repo on Github, and if you look in the CI routine, you can tell they’re using the official Discord packages and not modifying them.

Honestly, I should probably be sandboxing it more.

It’s annoying to use a proprietary service, but the This Might Be a Wiki community is rather enjoyable.

It’s not just packages. Ubuntu performance is terrible - it runs so much worse than other distros in VM. I don’t know about spins, but main Ubuntu takes 30 seconds to respond to some button presses whereas it’s nearly instant in other GNOME-using distros given equal or less resources.

I swear Ubuntu does something - I have run different distros in equally-specced VMs, some with GNOME, and Ubuntu by far performs the worse. Sometimes, it’ll actually take 30 seconds to respond to a simple button click.

When I have to test builds with what’s in Ubuntu repos, I usually avoid using Ubuntu directly and opt for a derivative like PopOS (which has unfortunately fallen behind on getting to Ubuntu 24.04).

Firmly agree with you on that.

I would agree calling it a web crawler is inaccurate, but disagree with the reasoning; I think it’s more in the sense that calling an LLM a web crawler is akin to calling a search index a web crawler; in other words, an LLM could be considered a weird version of a search index.