It seems like some person with a bot just asked to maintain a bunch of orphaned packages, abusing the 2-week waiting period. Right?
Thats why they used npm; off the shelf, almost “standard practice” credential harvesting malware. Nothing too fancy.
No.
Even the biggest open weights models are trained on pennies compared to OpenAI and Claude. They just don’t have the hardware to be so wasteful.
In fact, the Nvidia GPU ban was the best thing to ever happen to “small” AI devs. It made them thrifty.
Yeah.
It’s not even about efficiency, really, but independence from corporations, privacy, and principle. Kind of like Lemmy.
Or Artix. Or many others!
https://wiki.archlinux.org/title/Arch-based_distributions
I guess there’s a need to maintain existing systems, but I struggle to imagine a niche where recommending Manjaro to a “distro shopping” user makes sense.
I am open to criticism here… but when’s the last time y’all saw anyone defend Manjaro on a forum? It’s been years for me.
Before? It was the prominent “ergonomic” Arch Linux. But I’ve been burned by Manjaro enough that it would take a miracle for me to touch it again.
My experience is a few years out of date, but “more tested” was not the experience. It felt like they took the worst of Ubuntu and brought it to Arch: holding back packages enough to be annoying and tempt me to roll them forward/maintain stuff myself for fixes. But without any stability benefits of doing so. Stuff would break all the time and require manual intervention.
Manjaro got me to realize the Arch base is more “held back” than its reputation would suggest. The Arch maintainers do not roll out updates until every package works with every other package, and it turns out that ethos is incredibly hard to re-invent… which is what Manjaro ostensibly tries to do.
And yes. I can’t remember if AUR was a hard dependency, but it was certainly front-and-center. On Arch, you do not use AUR unless the package is self-contained (and therefore can fail to update without consequence) or if your system cannot function without it; and Manjaro didn’t exactly foster that caution. What’s more, many AUR packages were straight up broken since the base packages are different.
Thanks for the subscriber free link!
used to take 1 minute just to display a single raw photo
See, that’s a great example!
RAW processing (at least in that context) hasn’t really changed in 10 years. It’s probably the same code doing all the heavy lifting.
But most software doesn’t have that benefit.
If you’re wondering about Fedora vs CachyOS, it comes down to what you do on your PC. And what you’re used to.
If you want better “preconfiguration” for graphics stuff, CachyOS is the way to go. With Fedora you will end up referencing and maintaining a whole lot more yourself, while the CachyOS maintainers basically do all that maintinance and config optimization for you.
But Fedora might be better for a less GPU-focused “workstation” type system.
Generally, I’d look at the “style” and interests of distro maintainers. CachyOS is built by a collective of linux gaming/compute enthusiasts that snowballed into popularity, though it does inherit all the work from Arch. Fedora is a long standing workstation/server workhorse, a “pre release” for Red Hat enterprise linux.
It’s not! Use SonoBus; it’s dead simple, and superior to Discord. It’s far lower latency, with customizable filters, peer-to-peer; and totally free.
Now if you want emojis and video and rambling channels and stuff, you will have to go elsewhere.
Yeah, I’m not against the idea philosophically. Especially for security. I love the idea of containerized isolation.
But in reality, I can see exactly how much disk space and RAM and CPU and bandwidth they take, heh. Maintainers just can’t help themselves.
I find the overhead of docker crazy, especially for simpler apps. Like, do I really need 150GB of hard drive space, an extensive poorly documented config, and a whole nested computer running just because some project refuses to fix their dependency hell?
Yet it’s so common. It does feel like usability has gone on the back burner, at least in some sectors of software. And it’s such a relief when I read that some project consolidated dependencies down to C++ or Rust, and it will just run without shipping a whole subcomputer.
I used to write a few things for HardOCP, and we always made fun of Tom’s for clickbait, chum, and straight up groveling to Nvidia. We straight up weren’t allowed to cite them, and had no desire to.
That was like a decade ago.
…Maybe they were alright when Tom was still with them, but that was a loooong time ago. Too long for me to even know.
I’d do CachyOS. It’s a very new GPU. They even have packages specifically optimized for that CPU, and fixing stuff (other than simply rolling back) isn’t such a pain.
But I’m biased, as I like CachyOS.
Fedora if he’s not gaming.
Bazzite if he’s gaming. Or CachyOS.
I’ll give you the secret to easy linux: stick with defaults! Stick with distros aimed at whatever you’re tying to do, and you get a whole army of very experienced developers preconfiguring it all for you, for free. Instead of having to maintain breakage youself.
For example, do you want to learn all about debugging AMD drivers? Do you want to get into the intricacies of performant Proton setups, and environment variables, and kernels stuff?
You could just not, and get all that prepackaged!
Here’s just a sampling of some pre-configured stuff in my distro:
cachyos/protonplus 0.5.14-1
A simple Wine and Proton-based compatiblity tools manager for GNOME
cachyos/protontricks 1.13.1-1
Run Winetricks commands for Steam Play/Proton games among other common Wine features
cachyos/protonup-qt 2.14.0-1
Install and manage Proton-GE and Luxtorpeda for Steam and Wine-GE for Lutris
cachyos/umu-launcher 1.3.0-2
This is the Unified Launcher for Windows Games on Linux, to run Proton with fixes outside of Steam
cachyos/vkd3d-proton-mingw-git 3.0.r0.g6d97b022-1
Fork of VKD3D. Development branches for Protons Direct3D 12 implementation
cachyos-znver4/mesa-git 26.0.0_devel.216300.02cfc61cc93-1
an open-source implementation of the OpenGL specification, git version
Do I know a thing about how Proton works? Nope. Do I know anything about maintaining an upstream AMD driver for some kind of bug fix? Absolutely not. And I don’t have to! It’s just there, in sync with the rest of my system through some maintainer’s magic.
Mmmmm. Pure “prompt engineering” feels soulless to me. And you have zero control over the endpoint, so changes on their end can break your prompt at any time.
Messing with logprobs and raw completion syntax was fun, but the US proprietary models took that away. Even sampling is kind of restricted now, and primitive compared to what’s been developed in open source.
If you think of LLMs as an extra teammate, there’s no fun in managing them either. Nurturing the personal growth of an LLM is an obvious waste of time. Micromanaging them, watching to preempt slop and derailment, is frustrating and rage-inducing.
Finetuning LLMs for niche tasks is fun. It’s explorative, creative, cumulitive, and scratches a ‘must optimize’ part of my brain. It feels like you’re actually building and personalizing something, and teaches you how they work and where they fail, like making any good program or tool. It feels you’re part of a niche ‘old internet’ hacking community, not in the maw of Big Tech.
Using proprietary LLMs over APIs is indeed soul crushing. IMO this is why devs who have to use LLMs should strive to run finetunable, open weights models where they work, even if they aren’t as good as Claude Code.
But I think most don’t know they exist. Or had a terrible experience with terrible ollama defaults, hence assume that must be what the open model ecosystem is like.
Ah yeah Fedora does not support Nvidia. But third party repos should have a dkms version of the driver you should install instead.
On distros that do support Nvidia, the Nvidia driver is always paired to the kernel they provide, updating together.
Otherwise you literally do have to rebuild it every time. That’s what dkms automates, heh.
Heh. Sounds like you basically invented dkms?
If your distro doesn’t ship Nvidia drivers in sync with (and built against) your kernel, you’re supposed to install dkms versions that rebuild the driver automatically after every kernel/driver update. Not that this is obvious or anything, it took me a while to figure it out.
What distro are you using?
I’m surprised people think $1,100 is expensive for a gaming PC, even outside the crazy memory market now.
Same with the $500 Commodore phone.
These are not the 2000s. The dollar has inflated. Technology is expensive. I think cheap junk has desensitized folks to that, but you pay an externalized cost for that stuff.
And of course salaries haven’t gone up so anyone can actually afford it, but… that’s a distinctly separate problem. They should have, as corporate revenue and profit per worker has certainly gone up.