Uh, “no u”.
Putting the birthdate into linux is only helping Google, Apple and Microsoft.
…you can’t just say and claim that. At least give me some argument why would that be helping those companies.
Imo, the move would be if all linux distros were to let the date come and go and just geo block all requests from countries and zip codes that do this. Users breaking the law would not be the problem of the organization making the OS. If they’re not “offering” the OS in those zip codes, refuse all service, patches, updates, everything, they would not be legally responsible.
Daily usage? I have some audio issues. It “feels” like the whatever resets/reinitializes. Really quickly though, playback isn’t being interrupted. Sometimes it switches to a dead output channel though and I have to reset it to the actually connected output. Too lazy to diagnose it.
As a longer standing point of annoyance, I find it very difficult to quickly go UI -> package name -> bug tracker -> bug report. For understandable reasons devs don’t exactly advertise their bug trackers, they’re always a bit obfuscated and have some barriers.
Color management continues to not work correctly, although that may be due to some x11 wayland conflict. I have a dark color theme preference and certain applications that aren’t directly available as package, but e.g. via flatpack don’t integrate well. Gnome calendar is something I can name, without wanting to blame the devs of that piece of software in particular. They’re doing their best, it’s not a priority, maybe not even an issue on their preferred config.
I also have some freeze crashes, although that’s more recent, might be a harddrive/hardware issue that throws off something very low level. But the reboot is so quick I barely mind that.
But I couldn’t install a specific Python version? System python is 3.13 but I needed 3.10.
The others have covered virtual environments, which is what you need if you really want a 3.10 interpreter.
But… the thing I’m here to tell you is:
they recommend virtual box to not mess with your default installation of the program and the databases it uses.
for many projects this doesn’t actually matter. You can just ignore the warnings, use the most recent version and install whatever you need.
You’re already sandboxing this stuff in a virtual box, which you should be able to reset or bootstrap again when you need to. You’re not interfering with your actual systems’ python, you’re messing with your virtual box’s system python.
I find the whole venv stuff to be very annoying, I never need it, because I use libraries that don’t interfere with system operations and I don’t downgrade to interact with projects. And even if you’re not installing “correct” versions, most of the time newer versions fix bugs and expand functionality. It is extremely rare that functions get removed and it will actually break by you not using their exact version. Or like, version conflicts.
And besides, they would need some kind of CI / testing that would check for compatibility anyway.
tldr: ignore venvs, try it bare metal, see if something breaks. If not, there you go, if yes, you can still invest the time and effort of learning venvs.
Sounds good, good luck to the dev!
I mean, you have to modify it of course. You can’t literally blame cloudflare.
But you can modify everything so that it’s a funny joke that still looks like the cloudflare error that people know.
You know [Burger chain]? Self hosting is making your own burger. Kinda similar ingredients, kinda looking product overall, it’s still a burger.
But you’re in control.
Very good, we need more non github hosting sites.
Yes, but I complained on a very important project once…
We could have a neat little internet comment war about personal opinions on Qt…
But it’s the weekend and I’d rather not.
It says
On August 15th, 2025, Steam will officially stop supporting Linux distributions with a version of glibc older than 2.31.
How did this confusion happen?
I think saying it’s a [code hosting platform] instance is selling it a bit short.
They’re a registered club with official recognized “public benefit” status. They were specifically created to have a non commercial and community / society based choice for code hosting.
I don’t understand why the R4L are even trying to get it into THE kernel at this point. Especially after the open hostility, but also after basically offering to be “downstream” of whatever C people do.
The difference to forking and gradually transitioning things to Rust seem technically minimally negative and socially enormously positive to me.
And when and if people want to use the linux kernel with Rust, made by the R4L people, they would then be able to do that? Idk.
I have no stakes in either side, so I don’t really care.
To address this concern, CISA recommends that developers transition to memory-safe programming languages such as Rust, Java, C#, Go, Python, and Swift.
If only it were that easy to snap your fingers and magically transform your code base from C to Rust.
guy_butterfly_meme.jpg is this unbiased journalism?
Why the heck would 2 projects share the same library?
Coming from the olden days, with good package management, infrequent updates and the idea that you wanted to indeed save that x number of bytes on the disk and in memory, only installing one was the way to go.
Python also wasn’t exactly a high brow academic effort to brain storm the next big thing, it was built to be a simple tool and that included just fetching some library from your system was good enough. It only ended up being popular because it is very easy to get your feet wet and do something quick.
The difficulty with python tooling is that you have to learn which tools you can and should completely ignore.
Unless you are a 100x engineer managing 500 projects with conflicting versions, build systems, docker, websites, and AAAH…
Why is it like this?
Isolation for reliability, because it costs the businesses real $$$ when stuff goes down.
venvs exists to prevent the case that “project 1” and “project 2” use the same library “foobar”. Except, “project 1” is old, the maintainer is held up and can’t update as fast and “project 2” is a cutting edge start up that always uses the newest tech.
When python imports a library it would use “the libary” that is installed. If project 2 uses foobar version 15.9 which changed functionality, and project 1 uses foobar uses version 1.0, you get a bug, always, in either project 1 or project 2. Venvs solve this by providing project specific sets of libraries and interpreters.
In practice for many if not most users, this is meaningless, because if you’re making e.g. a plot with matplotlib, that won’t change. But people have “best practices” so they just do stuff even if they don’t need it.
It is a tradeoff between being fine with breakage and fixing it when it occurs and not being fine with breakage. The two approaches won’t mix.
very specific (often outdated) version of python,
They are giving you the version that they know worked. Often you can just remove the specific version pinning and it will work fine, because again, it doesn’t actually change that much. But still, the project that’s online was the working state.
Your joke, but as a short video by joel haver: https://www.youtube.com/watch?v=hnUpTyKSjag
(Thanks for actually engaging with the discussion).
Ok, sort of, maybe but this move is the move of big tech dominance. By caving to it, “linux” is positioning itself into a position of compliance with them, not opposition. What complying does is also removing the option to really oppose and evade big tech’s dominance.
We’re simply entering the era where installing an illegal operating system becomes a thing that is possible, because previously nobody cared to make an operating system illegal. And I would to have many distros to choose from that don’t comply with this, but I will pick the wacky silly outlier if I hate to. At least I like to think of myself as doing that.