Specter

Oh yeah you’re right, my bad, haha. Same, I cared so much for him that I forgot he survives Helgen smh.

Agreed, also because it doesn’t matter.

“Ralof” dies almost immediately upon meeting him so I feel like the hassle of naming him wasn’t even worth the time spent thinking about it.

I feel them giving him a name was a way to humanize him a bit and try to give him personality but there just wasn’t even time between knowing him and his death to make anyone care.

On another note, I think allowing to skip the intro and even the tutorial sections in games should become standard. Yes I’m sure studios put a lot of effort (lol) into that initial hook, but when you go through it for the third or fourth time it’s just annoying.

Are frameworks made in the US? Last I saw they are made in Taiwan.

In any case I’d rather fund China than the US lol are you kidding.

It’s insane how much tech fleeces Europeans, but it’s also always been like this. We don’t get the insane discounts USians get either. Never seen a Thinkpad 50% off around these parts like they do over there.

They cost an arm and a leg. We definitely need our own version of Framework home grown.

Right XD what a dogshit way of writing that title.

The “systemd devs” are anyone with the cashe to contribute to it. Yes, you need to be competent dev for your merges to be accepted, unlike in the virus-infested AUR.

But systemd can be forked if you don’t trust said devs. You’d be in the minority though because the majority of distros out there chose to adopt systemd, because it is that good.

Omg shut up. Nobody controls Systemd, it’s open source.

Another one that will weight 300g with a 60% screen to body ratio so that I can stare at the horrible bezels on that thing, I assume?

Thank you for the thorough technical explanation, it is clear there are challenges for devs and I understand why the pushback exists now.

As an end user these are things I haven’t felt, are essentially invisible to me so I never felt the need to run away from systemd.

Thanks again.

I’m aware, I just don’t care enough about this particular beef.

Systems works well for me, and in order to get my configuration up to what it is today on NixOS (what I need it to be) I’d have to install multiple proprietary/non-free software/drivers on Guix anyway.

In a roundabout way I’d end up in the same spot.

It’s not really mandatory, but I take your point.

I guess it’s the choice between many minor programs running in tandem, potentially only held together by a few maintainers, or an init system that unifies all those programs under one flag, with multiple maintainers including corporations, but the chance for it to get enshittified.

I personally have no choice of init system since I use NixOS. But I also don’t necessarily think the death of the personal computer will come from an init system, it will sooner come from hardware becoming unavailable/too expensive for individuals to buy (basically what we are seeing happen now).

Okay, other than “I believe it’s against the Unix Philosophy” and “hypothetically it will become bloated”, is there anything else worth knowing?

I should have clarified that the list above only makes sense if you just want your machine to work because atomic distros aren’t great to tinker with (except NixOS), but let’s face it, moist people are not tinkerers do what they need is exactly what atomic distros offer.

Waiting for Motorola compatibility to come out! I had a pixel before and I didn’t like it, too heavy, horrible body-to-screen ratio, huge phone too. Plus it’s Google.

I don’t get it, what about the gitignore reveals he’s vibecoding?

That’s a round about way of saying RTFM, but even less welcoming. Probably not the kind of thing anyone should be told…

Uh… is the NixOS documentation “one of the best around” or have you never checked it? It really can’t be both.

Understand, I’m not trying to criticize NixOS. I use NixOS exclusively and it’s my daily driver. But the documentation really isn’t all there, and it’s not centralized. The best solutions you find across forums, blog posts, random wikis, and by checking other people’s configs like you said.

But yes, the fact you can test things without fear of breaking your system allows you to make hundreds of mistakes stress-free. That’s one of the best features about NixOS.

I am talking from experience here. Some of the documentation is out of date, some is meant for Channel NixOS installs and not so appropriate for Flake-based installs.

Most of the fixes for my issues I find across NixOS discourse forum posts, or in the subreddit of the other platform. The Wiki/official documentation is not enough.

I’m glad you switched to NixOS (welcome!) but this is gap in documentation is something that will become more apparent over time. The NixOS official wiki ironically often links to Arch wiki to explain certain concepts further.

I like this. I think paying people to develop FOSS is fine, we’re also all better off for it.