Yeah, this one is on Kent… again.

He posted on Patreon that there’ll be a DKMS module. In my opinion, this should have been the option from the very beginning and upstreaming at a later point in time. It would have avoided a lot of drama. And now bcachefs is kind of tainted. The only way I ever see it back in mainline is there is an independent downstream of Kent’s kernel that has no connection to him whatsoever.

Shame because I had very good experience with the filesystem. Definitely better than when btrfs was new. But Linus is unfortunately right; Kent is unable to follow agreed collaboration rules.

Unfortunate situation that could have been avoided entirely. Though I don’t want to be too harsh on Kent. He spent a lot of time and work on bcachefs and it’s his most important project. As such, he’s more passionate about all of this. But the same can be said for Linus and the kernel on the other side.

PipeWire my beloved 😍

Yes, these are unrelated

Allows you to scroll through / view a text file in the terminal.

Admirable dedication to the cause

Godspeed, keep the hacking spirit alive

Yup just need to pick it up from your local rescue shelter

The issue is not only complexity, though it does play a role. You can also run into issues with pure text parsing, especially when whitespace is involved. The IP thing is a very classic example in my opinion, and while whitespace might not be an issue there (more common with filenames), the queries you find online in my opinion aren’t less complex.

Normal CLI output is often meant to be consumed by humans, so the data presentation requirements are different. Then you find out that an assumption you made isn’t true (e.g. due to LANG indicating a non-English language) and suddenly your matching rules don’t fit.

There are just a lot of pitfalls that can make things go subtly wrong, which is why parsing general CLI output that’s not intended to be parsed is often advised against. It doesn’t mean that it will go wrong.

Regarding Python, I think it has a place when you do what I’d call data set processing, while what I talk about is shell plumbing. They can both use JSON, but the tools are probably not the same.

It’s a cool shell, I like ita lot more since I found out you can use ? to mark a field optional

It’s true that compared to the other utilities, it’s rather new. First release was almost 13 years ago. awk, which I think is the closest comparison, on the other hand turns 50 in 2027… though new awk is only 40.

Thanks, I never used it and had forgotten about it until now.

From a quick glance, this is pacman with a yaml file instead of a shell script and PKGINFO (the latter was introduced for the same reason you’re doing it your way in the first place). The carcinization of package managers

I really like fish. It’s just so pragmatic, I don’t know how to describe it differently. No groundbreaking concepts (like nu or elvish), but the tools you need are right there and easily accessible with syntax that doesn’t make me scratch my head (bash).

NixOS as the first Linux distro is an interesting choice, definitely not bad, but probably not what most people would go for

Sorry if I sound dumb, but which kind of program would be the one to display the output of text based interfaces, also called terminal applications, if not a terminal?

Okay, that sucks. Yeah, I bought a refurbished business device

Then the “avoid at all costs” like Dell

Must have gotten lucky then. Bought a used Dell about one and a half years ago. Everything worked out of the box

I don’t think his statement is true though. If https://www.reddit.com/r/linux_gaming/comments/1ce7z19/gaming_on_linux_ep131_ntsync_vs_fsync_nobara_39/l1ho8od/ is not manipulated in any way, games with lots of these calls still get big improvements with ntsync over fsync (about 30% in this particular case, which is a massive boost). So while nobody can rule out that his statement may be true on average or in general, there are still cases where ntsync offers a tangible advantage – be it improved FPS or the fact that the game runs at all.

Edit: in the video that the thread is about, fsync didn’t beat ntsync in a single one (or I missed it when jumping through it). In the best one, they were exactly tied. Sure, the difference wasn’t really big, but again there are titles not working with fsync.

However, I want to stress that I’m not trying to talk about fsync. It’s a good solution that significantly improved performance. But ntsync is, from everything I’ve seen, almost always better; how much depends on the case, and it never seems to be worse.

Yes, sorry

Any linking against GPL software requires you to also release your source code under GPL. ALGPL allows you to link to it dynamically without relicensing, but as explained, there are platforms where dynamic linking isn’t an option, which means these libraries can’t be used if one doesn’t want to provide ALGPL licensed source code of their own product.