Llvmpipe is enabled in mesa at compilation time and actually modifies the swrast_*.so the last time I checked. Not runtime configurable. Also, I know at one point it had issues running on 32 bit machines. Not sure if that’s still the case.

Just add a new user

To be fair, C predates dependency hell. It was either there or it wasn’t. C++ has less of an excuse, but it was just object oriented concepts taped to C so it’s no surprise it was also missing dependency management.

Now with cmake, gnu-make, meson, gradel, and the world of metabuild systems that wrap those, nothing will change. It it does, it might as well kick start world war 3.

https://github.com/MultiMC/Launcher/issues/4102

I agree limiting application scope is useful for multiple reasons, however Jellyfin started as a fork of Emby which already had music support. I have yet to find a standalone application that has enough features to sway me from just utilizing the existing media server functionality.

Finamp’s current alpha was a huge surprise to me. I stopped looking at development for a few months and in that time they completely reworked it

Nope, but it has become a backronym https://wikipedia.org/wiki/Object_storage#Origins

Ah, so the kernel actually uses mailing lists. You need to use the get maintainers Perl script to get the people you need to send the email TO and then send it to them with the dri-devel list CC’d.

That wouldn’t be accepted as is, but those sound like tunables. They could be exposed as kernel parameters. May be worth submitting the patch as an RFC just to call attention to it.

What modifications were required? The good part of a rolling release is that upstreaming things means you only have to deal with manual fixes for like 2 or 3 updates.

They’d update it, but they are afraid it would no longer work as well

You would first need to define malicious code within the context of that repo. To some people, telemetry is malicious.

I made it through college without using windows on any of my personal machines, but I did need to access a library or computer lab to take 1 test that needed a specialized web browser for some reason. Other than that, I was actually pleasantly surprised by how easy it was to slip by with a good PDF viewer, libreoffice, and Inkscape.

My degree was in computer engineering, most groups I worked in outside of the engineering department just preferred collaboration through office online or google docs.

Ah, my last phone that no longer receives any updates. Pixel 2XL. Just keeping it around because parting with electronics is difficult.

Arch on every box in the house, including the primary router. Mixed Intel and AMD. Openwrt on every AP (unfortunately Mellanox and MediaTek firmware blobs for the radios). GrapheneOS on my daily and LineageOS on my legacy phone.

Aside from occasional games, I don’t install anything I don’t have the source to. My phone is the only exception, for apps required to interface with the rest of the world.

Yo, they added full page copies now? Gotta give it a spin again

Something like this can kind of be achieved programmatically by unraveling bash completion arguments and loosely parsing terminal help strings.

They aren’t all formatted uniformly though, so you’ll need to come up with a filtering mechanism to prevent returning garbage. You’ll also always be a little out of date…

Bash, just because everything else already uses it. That and bashisms have infected nearly all of my scripts as I clumsily bump into the limitations of POSIX string manipulation.

I have found some very fun things with sed branching patterns as a result of these limitations though…

https://www.gnu.org/software/sed/manual/html_node/Branching-and-flow-control.html

Well, assuming you meant type specifier, at least not before C99. After that it is required. C23 explicitly states that a type specifier is required for all declarations.

If you actually meant type qualifier, then no. That was never required.