I personally use a ThinkPad Z13 (all AMD; it's nice but pricey), but I'd recommend getting a Framework (which wasn't an option for me back then). I think modular and repairable laptops are cool, plus they seem to be well supported by the Linux community.
Samsung midrangers like the A15 / M15 / A25 etc have both the jack as well as an sdcard slot. There's also the Motorola G34 and the G84. And finally, there's also a flagship - the ASUS ROG Phone 8 Pro. And a whole bunch of Chinese phones which I won't bother mentioning.
Considering that predicting the next word from context is the one thing LLMs are really good at, I just don't understand how none of these developments have found their way into predictive keyboards.
The problem is that LLMs require a considerable amount of computing power to run, unlike the simple markov chain predictions that keyboards use. You could use a cloud-based service like ChatGPT or something, but most people wouldn't want their keyboards to send all their keystrokes to a remote server... and even if they didn't know or care, the response time wouldn't be good enough for real-time predictions.
Now smartphone SoC makers like Qualcomm have started adding NPUs (neural processing units) with their latest chips (such as the SD8 Gen 3, featured in the most recent flagship phones), but it's going to take a while before devices with NPUs become commonplace, and it'll take a while for developers to start making/updating apps that can make use of it.
But yeah the good news is that it is coming, it's only a matter of "when" - I suspect it won't be long before the likes of SwiftKey start to take advantage of this.
Does Guix have a Nix Home Manager + nixpkgs equivalent? I currently use them to install packages on other distros, but with nixpkgs maintainers leaving in droves, I'm looking for alternatives.
You might be interested in these things called mouse jigglers, they range from a tiny USB dongle that simulates a mouse, to motorised movement pads that you can place under a real mouse, which would be undetectable by software.
PS: You're welcome. ;)
Usually setting the cache mode to "none" gives the best performance, assuming you're using the virtio interface, instead of SATA/SCSI. This is a common mistake most newbies make when installing Windows, because virt-manager defaults to the latter, which gives poor perfomance. The same goes for the network btw, you'd want to use the virtio network interface instead of the emulated NIC. So before you install a Windows guest, make sure you change both those interfaces.
After changing the hardware interfaces, what you'd need to do (with Windows guests) is you'd need to supply the [virtio drivers](https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md, which you'll need to provided to the Windows setup (via the virtio driver ISO) when prompted.
But if you've already installed Windows, you'll need to install all the virtio drivers first and then update the interfaces after you've powered off the VM.
And in case you were wondering, this isn't an issue with Linux guests, since virt-manager defaults to virtio hardware, and drivers aren't an issue either.
This is a known issue with TF2, you'll need to switch to OpenGL to fix it. However, you may also need additional launch options as listed here (but try just the OpenGL switch first).
That 240W is only for SuperVOOC. PD however goes only upto 65W. Plus, being that big and single-port only makes this thing completely pointless for everyone except VOOC users.
Agreed, this is a nice inclusion. I also hate sudoers with a passion - I already use
doasbut it's not standard (in the Linux world anyway), but with systemd providing an alternative means that it'll become a standard which most distros would adopt, and I hope this means we can finally ditch the convoluted sudoers file once and for all.