E4RLAT
42.5K posts

固定されたツイート
E4RLAT がリツイート
E4RLAT がリツイート

@grok @HSVSphere is this valid Go? I don't know that language, I can't confirm. Grok is so smart.
English
E4RLAT がリツイート

@HelmerVA At this point, most gun owners assume that anyone saying "common sense" in a discussion of gun control is lying about their intentions and pushing towards total confiscation.
You aren't doing anything to make us doubt this.
English
E4RLAT がリツイート

@hasanthehun You abuse animals and support terrorism. There is no moral equivalency.
English
E4RLAT がリツイート
E4RLAT がリツイート
E4RLAT がリツイート

\✨入荷しました✨/
STEINS;GATE 牧瀬紅莉栖15周年記念イラストver. 1/7 完成品フィギュア[アルマビアンカ]
⇒amiami.jp/top/detail/det…
#シュタゲ



日本語

There is considerable merit in your argument, Devon.
On the other hand, I've found myself being significantly impeded by Ubuntu's long release cycles and want to get rid of that source of drag.
So I have a choice: continue living with the drag, or go to a rolling release and risk that I'll have more pain from occasional breakage combined with the administrative effort required to do rollback when things break.
There are costs either way. No perfect solution.
I guess it comes down to this: I'm rather neophilic, and then the presence of a trade-off like this I prefer to lean forward rather than backwards.
So I'm willing to give the new thing a try. It's quite possible that in a month or three I'll decide that was a bad idea. If so, so be it.
English

Question for the X hivemind:
I'm seriously considering switching my main machine from Pop!_OS (a reskinned Ubuntu) to Arch, probably CachyOS.
The reason is I'm attracted to the rolling-release concept. Getting really tired of waiting 6 months for my development tools to upgrade after they ship.
I understand the downside: Arch doesn't protect me from upstream breakage. The plan to deal with that is to install snapper so I can revert to an earlier, working version of my system if things go badly awry.
If you think there are any reasons this is a really bad plan, tell me now.
English
E4RLAT がリツイート
E4RLAT がリツイート
E4RLAT がリツイート
E4RLAT がリツイート
E4RLAT がリツイート
E4RLAT がリツイート
E4RLAT がリツイート


In response to my previous thread asking about the feasibility of switching to Arch, several people recommended NixOS instead.
That's not going to happen, and I'm sad about it. Because technically I'm extremely attracted to the Nix model. How could I not like declarative system specification with guaranteed safe rollback? That would be ideal.
As an old Lisp-head, I probably would have opted for the Guix variant that uses Guile/Scheme as an extension language.
Unfortunately, I have a friend who was a long time NixOS user who bailed out last year. He's given me a detailed and hair-raising report on why. I'll get back to that.
He says the design of NixOS is very Eric-shaped. He knows how much I like substituting declarative specifications driving simple engines for ad-hoc procedural logic (see for example loccount), and NixOS do be like that.
Unfortunately, he also says the NixOS developer community has become dysfunctional and insane. By his account, the woke mind virus took hold, drove away a lot of capable people, and addled the brains of most of those who remained. That's why he bailed out.
I have no reason to disbelieve him about this. It's a movie I've seen before.
He has a secondary technical criticism that Nix has a bad case of not invented here and builds a lot of bespoke machinery that would be unnecessary if it were willing to take full use of Linux's native namespace and containerization hooks. But they want to be fully portable to things like *BSD, so that hasn't happened.
The technical choice is defensible, and could be fixed. The mind-rot in the developer community probably isn't fixable. All you can usually do in cases like that is ignore the project and let it die.
So, no NixOS for me. Dammit. Communists ruin everything they touch.
English

















