Your best bet would probably be to get a used office PC to put the card in. You’ll likely have to replace the power supply and maybe swap the storage but with how much proper external enclosures go for the price might not be too different. Some frameworks don’t support direct GPU loading so make sure that you have more ram than vram.

An arm soc won’t work in most cases due to a lack of bandwidth and software support. The only board I know of that can do it is the rpi5 and that’s still mostly a poc.

In general I wouldn’t recomend a titan x unless you already have one because it’s been deprecated in cuda, so getting modern libraries to work will be a pain.

I really like the simplicity and formatting of stock pacman. It’s not super colorful but it’s fast and gives you all of the info you need. yay (or paru if you’re a hipster) is the icing on top.

It does a little bit worse than v0.1 on all benchmarks which isn’t ideal. That doesn’t really say much about the finetuning potential though.

Don’t buy a Chromebook for linux. While driver support usually isn’t an issue, the alternative keyboard layout is terrible for most applications. To even get access to all of the normal keys that many applications expect you need to configure multi-key shortcuts which varies in complexity based on your DE. In most cases it will also void your warranty because of the custom firmware requirement.

This is big if true, but we’ll have to see how well it holds up at larger scales.

The size of the paper is a bit worrying but the authors are all very reputable. Several were also contributors on the retnet and kosmos2/2.5 papers.

Koboldcpp should allow you to run much larger models with a little bit of ram offloading. There’s a fork that supports rocm for AMD cards: https://github.com/YellowRoseCx/koboldcpp-rocm

Make sure to use quantized models for the best performace, q4k_M being the standard.

The ~400USD price tag is really impressive, but the big thing with these folding phones is the reliability of the hinge. It will be interesting to see how it fares when proper reviews come in.

It’s not open source it’s weight available(for now). As of now there’s nothing you can do with it publicly because it lacks a license and is known to be stolen.

Almost everything has been done already. Most new app ideas are just gimmicks thrown onto existing concepts.

FAIR has existed for over 10 years now, I’d hardly call that fickle.

Just introducing them to it is probably enough. Show them different desktop environments and applications to get them used to the idea of diverse interfaces and workflows. Just knowing that alternatives exist could help them break out of the Windows monoculture later. Enable all of the cool window effects.

Dropping support after only 25 years? I can’t believe Linux is contributing to planned obsolescence.

Smaller communities aren’t necessarily a bad thing. Compared to reddit I rarely feel like I’m commenting into the void.

Not another one

From what I’ve heard they’re competitive for English but I’ve never used Deepspeech myself. Whisper has much more community support so it’s probably easier to use overall.

I’ve used the tplink ones that they’re using and they’ve been pretty solid. I can’t say how they’d fare in a 24/7 setup though since they’re not really intended for that.

Whisper is your best bet for FOSS transcription. This is the most efficient implementation AFAIK: https://github.com/guillaumekln/faster-whisper.

Not even remotely. It requires custom firmware which often requires physical disassembly to install. From there you can install any distro, but you will continue to have many small issues and inconveniences often due to the nonstandard keyboard.

There was a Chromebook targeted Linux distro called eupnea that could be installed without custom firmware via depthboot, but it’s dead now and the original repo got deleted after the Dev got hacked, so the build scripts don’t work anymore.

There are 2 ways to do it, either via depthboot(software only, no custom firmware, lots of manual OS prep, 0 risk) or custom firmware(maybe physical, model dependant, no os prep, small risk). For custom firmware you usually have to either bridge an internal jumper, unplug the battery, or build a custom cable, depending on your model.

While it is allowed it’s not supported by google.

I would never recommend buying a Chromebook with the intention of replacing the OS unless you’re looking for a project or you’re getting it for cheap.

As someone who has owned a Chromebook for several years, I can tell you that you shouldn’t. Hardware wise it’s hard to beat Chromebooks at their price points, but the complete lack of control over the system is a deal breaker. I don’t have time to list all of the issues I’ve had. In many cases what would have been trivial fixes on a normal Linux system required full reinstalls on chromeOS. Like the time I accidentally filled up the fairly modest system storage. The system refused to allow me to delete anything, requiring a reset just to get local file management abilities back.

I ultimately ended up installing full Linux on it, which ended up being a whole other ordeal due to all of Google’s “security” features.