Jesus Michał "Le Sigh" 🏔 (he)

A #cat (owned by 3 cats), a nonconformist. #Gentoo developer, est. 2010. Taking care of #Python, #LLVM, #Xfce. #FreeSoftware enthusiast. #CarFree → #rail around #Poznań and western #Poland. #MADAO. #AntiCapitalism. #ActuallyAutistic + #diabetes. Random rants, silly humor. Playing with tongue, and enjoying double entendres.

Follows require approval because apparently AI-bros think not refusing a follow is consent.

Note: if you can read Polish, I recommend following my Polish profile instead (link in table). It includes unique content that doesn't work in English, and I boost all English content there anyway.

#TootFinder

Public Key

npub1r9jmk6t0ape7t9ddfv5nrrsh87pluzxtepzjqu93sctkkurun0wqft4ppx

NIP-05 Address

mgorny@social-treehouse-systems.mostr.pub

Profile Code

nprofile1qqspjedmd9h7sul9jkk5k2f33ctnlql7pr9us3fqwzccv9mtwp7fhhqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds9cyzza

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1r9jmk6t0ape7t9ddfv5nrrsh87pluzxtepzjqu93sctkkurun0wqft4ppx

Show more details

Last Notes

2026-04-25 12:15:33 UTC

The bright #LLM future, next part.
git.gentoo.org is now effectively dead, being DDoS-ed by almost a million different IPs every day. Most of them are just performing a single request at a totally random URL. How are people supposed to deal with that? How can we distinguish a legitimate user who hit some URL from a scraper that distributes its operations over thousands of IP addresses?
If you use LLM crap, you're part of the problem. You support these bastards. You should be ashamed of yourself.
#Gentoo #NoAI #NoLLM #AI

2026-04-11 14:03:54 UTC

Completed:
✅ Ultimate Doom
✅ Doom II
✅ Heretic + Shadow of the Serpent Riders
✅ Hexen
I suppose I should mix in some #Doom expansion next, before going for Hexen's Deathkings of the Dark Citadel.

2026-03-21 14:38:37 UTC

- reply

@nprofile…6z3g, well, I suppose i'm missing some context here, but it really sounds like you are defending people who aren't just "forced" to implement something, but who are doing that wilfully while having openly expressed opinions largely in agreement with these laws.
In other words, it sounds like another case of "Don't be angry at nazis, they're people too. Just kiss their feet and hope they don't decide that you don't deserve to live the next week. Unless they already believe that, and are just waiting for a good excuse to have you executed."

2026-03-21 07:38:12 UTC

Age verification in #Gentoo: if you're using Gentoo, you must be old enough. Problem solved.
#shitposting

2026-03-04 12:56:53 UTC

- reply

@nprofile…6z3g, not to mention it doesn't pass its own test suite.

2025-10-08 08:13:24 UTC

Sequoia PGP exemplifies everything that's wrong about #RustLang (don't mean this against Sequoia). It features a bunch of different CLIs, which is a reasonable design.
If Sequoia were written in C, these CLIs would probably be using some shared library. If Sequoia were written in Python, they would probably use a shared Python package. However, it's written in Rust, so every CLI is a huge binary with its own copy of subset of shared Sequoia code, built separately:
-rwxr-xr-x 1 root root 12M 10-08 06:36 /usr/bin/gpg-sq
-rwxr-xr-x 1 root root 4,7M 10-08 06:36 /usr/bin/gpgv-sq
-rwxr-xr-x 1 root root 21M 10-08 08:38 /usr/bin/sq
-rwxr-xr-x 1 root root 6,9M 10-08 08:38 /usr/bin/sqop
-rwxr-xr-x 1 root root 3,1M 10-08 08:32 /usr/bin/sqv

2025-10-01 04:02:37 UTC

When I bought a #Pixel phone, I've spent three times as much as I usually spend. I figured out it's justified, since I'm finally going to have a phone with good software support (#GrapheneOS).
Over the last 6 months, #Google:
1. locked down the device tree,
2. increased embargo to security updates to 3 months,
3. broke battery charge limiter.
Won't recommend this to anyone.
#Android

2025-08-26 05:17:35 UTC

At the vege-table.
#DadJokes

2025-08-25 10:13:16 UTC

Just a random reminder that you can't call someone a lunatic, unless their madness is influenced by the moon.

2025-08-24 03:14:44 UTC

You know what's the difference between a human programmer and an "#AI coding assistant"?
Sure, human programmers make mistakes. And rookies often make "worse" mistakes than an #LLM can come up with. However, the difference is that humans can actually learn. Teaching them comes with a payoff; not always and not necessarily for your project, but there's a good chance that they'll become better programmers and contribute back to the community.
Sure, human programmers sometimes plagiarize. And of course they need to look at some code while they learn. However, they actually can think on their own and come up with something original. And they can learn that plagiarism is wrong.
And most importantly, usually they don't lie if they don't have to, and there are limits to their smugness. You can build a healthy community with them.
You can't build a community with unethical bullshit-spitting machines.
#programming #FreeSoftware #OpenSource

2025-08-23 10:26:37 UTC

Well, I am complaining about #AI slop introducing some random bugs in a minor userspace project, and in the meantime I learn that #Linux #kernel LTS developers are using AI to backport patches, and creating new vulnerabilities in the process.
Note: the whole thread is quite toxic, so I'd take it with a grain of salt, but still looks like the situation is quite serious.
"You too can crash today's 6.12.43 LTS kernel thanks to a stable maintainer's AI slop."
And apparently this isn't the first time either:
"When AI decided to select a random CPU mitigation patch for backport last month that turned a mitigation into a no-op, nothing was done, it sat unfixed with a report for a month (instead of just immediately reverting it), and they rejected a CVE request for it."
https://xcancel.com/spendergrsec/status/1958264076162998771
#security #LLM #NVIDIA #Gentoo

2025-08-22 18:16:38 UTC

Unpopular opinion (yes, I know y'all going to ban me now): #Microsoft #Teams is not the worst videoconferencing tool I've used at dayjob.
#Slack: tested screen sharing before the job interview using the browser. During the interview it turned out that the test mode is different than the actual "huddle", and had to install the app real quick.
#Google Meet: "Meet doesn't work on your browser". Tells me to install one of the support browsers, e.g. #Firefox. Except that I'm using Firefox. 🤦
#Zoom: "install our app".
Teams: miraculously just worked.

2025-08-19 08:52:05 UTC

I've seen a poster with examples of sign language on a bus stop in Piła. That's a fine idea.

2025-08-18 19:23:36 UTC

If a track contains only music and "oioioioioi"s, is that a vocal track or an instrumental track?

2025-08-18 05:25:29 UTC

The best way to think of "stakeholders" is to imagine people holding wooden stakes.

2025-08-14 20:04:24 UTC

New on #Quansight PBC blog: Python Wheels: from Tags to Variants
https://labs.quansight.org/blog/python-wheels-from-tags-to-variants
"""
Many #Python distributions are uniform across different Python versions and platforms. For these distributions, it is sufficient to publish a single wheel that can be installed everywhere. However, some packages are more complex than that; they include compiled Python extensions or binaries. In order to robustly deploy these software on different platforms, you need to publish multiple binary packages, and the installers need to select the one that fits the platform used best.
For a long time, Python wheels made do with a relatively simple mechanism to describe the needed variance: Platform compatibility tags. These tags identified different Python implementations and versions, operating systems, and CPU architectures. Over time, they were extended to facilitate new use cases. To list a couple: PEP 513 added manylinux tags to standardize the core library dependencies on GNU/Linux systems, and PEP 656 added musllinux tags to facilitate Linux systems with musl libc.
However, not all new use cases can be handled effectively within the framework of tags. To list a few:
• The advent of GPU-backed computing made distinguishing different acceleration frameworks such as NVIDIA CUDA or AMD ROCm important.
• As the compatibility with older CPUs became less desirable, many distributions have set baselines for their binary packages to x86-64-v2 microarchitecture level, and Python packages need to be able to express the same requirement.
• Numerical libraries support different BLAS/LAPACK, MPI, OpenMP providers, and wish to enable the users to choose the build matching their desired provider.
While tags could technically be bent to facilitate all these use cases, they would grow quite baroque, and, critically, every change to tags needs to be implemented in all installers and package-related tooling separately, making the adoption difficult.
Facing these limitations, software vendors have employed different solutions to work around the lack of an appropriate mechanism. Eventually, the #WheelNext initiative took up the challenge to design a more robust solution.
"""
#packaging

2025-08-14 05:24:56 UTC

Kanban? Sure I can ban!
#WordPlay

2025-08-11 04:43:19 UTC

I feel like people have forgotten what "analog" means. They're living in an analog — digital dichotomy, where everything that's electrical is "digital", and everything else is "analog", entirely ignoring the whole lot of analog electronic devices, or rather dumping them all in the category of "digital".
Perhaps we're lacking a good term for all the non-electrical devices.
#English

2025-08-11 03:22:33 UTC

Using the sexagesimal numeral system for measuring time was a stroke of genius.
Think about it. It exists for a few thousand years already, and people back then already predicted the existence of metric system and my person, and set the time measure so that I could easily compute that I'll walk 1 km in 10 minutes.
#shitposting

2025-08-09 05:51:48 UTC

Dear scammer,
If you want to scam me, you could at least bother setting the correct MIME type for your email, so I would actually see something else than a bunch of inline HTML with lots of CSS.
#scam #spam #email

2025-08-08 14:25:37 UTC

#Google Docs: "These actions are unavailable using the Edit menus, but you can still use: Ctrl+C for copy, Ctrl+X for cut, Ctrl+V for paste."
Yeah, sure, but I clicked "paste without formatting".
(Yeah, figured out it's Ctrl+Shift+V" but still Google sucks.)

2025-08-07 13:57:30 UTC

You can't say "participants" without "pants".

2025-08-07 07:29:47 UTC

Claiming that LLMs bring us closer to AGI is like claiming that bullshitting brings one closer to wisdom.
Sure, you need "some" knowledge on different topics to bullshit successfully. Still, what's the point if all that knowledge is buried under an avalanche of lies? You probably can't distinguish what you knew from what you made up anymore.
#AI #LLM

2025-08-03 03:45:08 UTC

Thinking about it, Enlightenment (the desktop environment) used to be pretty baroque.

2025-07-30 14:33:09 UTC

When I get a #spam where someone is offering to be my "deigner", and I'm like… why would I hire someone to deign?

2025-07-29 15:07:51 UTC

Substack? Why would I want a substack if I can't keep up with the items from my main stack!

2025-07-28 19:50:46 UTC

Some things are groß, but some are just gross.
#WordPlay

2025-07-26 13:30:55 UTC

New on blog: "EPYTEST_PLUGINS and other goodies now in #Gentoo"
"""
If you are following the gentoo-dev mailing list, you may have noticed that there’s been a fair number of patches sent for the #Python eclasses recently. Most of them have been centered on #pytest support. Long story short, I’ve came up with what I believed to be a reasonably good design, and decided it’s time to stop manually repeating all the good practices in every ebuild separately.
In this post, I am going to shortly summarize all the recently added options. As always, they are all also documented in the Gentoo Python Guide.
"""
https://blogs.gentoo.org/mgorny/2025/07/26/epytest_plugins-and-other-goodies-now-in-gentoo/

2025-07-23 13:14:27 UTC

Okay, time to continue bashing. Perhaps this one project is just that bad, but Conan sounds like a complete antithesis of what a package manager is all about.
Well, this package insists to build its dependencies via Conan. Except it insists on really old versions that don't work with my glibc. So I need to start swapping dependencies.
Except it turns out Conan doesn't care much about resolving dependencies. So I actually need to start adjust versions of the dependencies of packages that it wants to build. And then it starts rebuilding other stuff and again everything fails because of incompatible versions.
And when I finally manage to find a working set, the actual project fails over protobuf version. After a long WTF-ing, I finally realize that it's complaining, because it somehow managed to mix the version of protobuf built by Conan and the external protobuf installed by Conda.
So yeah, great job. A package manager that doesn't really resolve dependencies but instead forces a dependency hell on you, and on top of that ends up mixing system packages with its own packages.

2025-07-21 04:39:24 UTC

Fun fact: in #Polish, all cardinal directions have the same names as times of day. East is "wschód" which means "rise" (as in sunrise, "wschód słońca"), west is "zachód" — "set" (as in sunset, "zachód słońca"). North is "północ", lit. "midnight", and south is "południe", lit. "midday".
Apparently, the #English etymology is not so clear. "West" and "east" seem to unrecognizably stem from the words for evening and dawn. "South" seem to be related to "sun", whereas "north" to "to the left of the rising sun".
https://en.m.wikipedia.org/wiki/Cardinal_direction

2025-07-17 03:40:30 UTC

I've just noticed that the town of Powodowo is doubly "OwO".

2025-07-13 17:45:26 UTC

Given that #Gentoo #Bugzilla mail is down for three days now, if anybody needed to search for bugs changed since Friday:
https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&o1=greaterthan&order=changeddate&v1=2025-07-11

2025-07-02 04:47:30 UTC

A progress walks into a bar…
#DaddyJoke

2025-06-23 18:49:38 UTC

The time has come for me to propose that #Gentoo leaves #GitHub.
#Microsoft has been purveying #enshittification of this platform for years now. Pushing #Copilot everywhere was the last straw.
https://public-inbox.gentoo.org/gentoo-project/1c0b6be5cb24d51deecaed2ccf99593d0fac185e.camel@gentoo.org/T/#t
#AI #LLM

2025-06-21 05:47:56 UTC

My personal recommendation would be to stay away from the "#Python Code Quality Authority". The projects have been pretty much taken over by a toxic and mean-spirited person. #Ruff is a good replacement, with very friendly upstream.
https://github.com/PyCQA/pycodestyle/issues/1183#issuecomment-1664412107
https://github.com/PyCQA/pyflakes/pull/802#issuecomment-1943806162
#PyCQA

2025-06-09 16:14:20 UTC

"Private property. No mowing grass !!"
https://cache.treehouse.systems/media_attachments/files/114/654/281/737/794/731/original/6ec91872e240adc2.jpg

2025-06-07 08:38:34 UTC

Time for the periodic check of my ~/.cache directory:
ccache: 4G
uv: 2.2G
pre-commit: 2.1G
rattler: 1.7G
mozilla: 1.1G
thumbnails: 1G
evolution: 550M
fotema: 511M
pip: 404M
Not assuming infinite space in home directory is overrated.
#Gentoo #Python

2025-06-02 03:54:15 UTC

Just one more build system, bro! Surely you won't regret adding one more build system!
Of course they're trying to shove #Bazel in.
https://github.com/libarchive/libarchive/issues/2581

2025-05-27 07:14:31 UTC

English-speaking people are weird. They eat dates, like there was something nourishing about the calendar.

2025-05-26 09:19:07 UTC

Isn't it telling that you commit changes to a VCS or SQL queries just like you can commit a crime, commit adultery or arsen? And these are just a few suggestions from a search engine autocompletion.

2025-05-25 16:41:12 UTC

His Ek-cellency demands belly rubs.
#cat #CatsOfMastodon
https://cache.treehouse.systems/media_attachments/files/114/569/418/468/778/661/original/caff9cbcee0e52fa.jpeg

2025-05-19 04:46:58 UTC

- reply

@nprofile…kcjh, but what if I deliberately mean it as the second letter? xP

2025-05-17 17:54:14 UTC

I've released gpyutils 0.14.0 today. The new version replaces the ugly PYTHON_COMPAT processing and mangling algorithm from 2013 with a new one. It was necessary, since the old version messed up the suffixes in "python3_{13,14}t" (it got confused by the "t").
In the new version, I've made a few different assumptions. Notably, nested braces are no longer supported (like "python3_{{10..13},13t}" — it's literally used by one package), and groups are more proactively replaced with ranges (eg. changing "python3_{11,12}" to "python3_{11..13}" instead of "python3_{11,12,13}").
https://pypi.org/project/gpyutils/0.14.0/
https://github.com/projg2/gpyutils/compare/v0.13.2..v0.14.0

2025-05-13 04:42:01 UTC

- reply

@nprofile…7093, the train has been manufactured in 2013, so I'm guessing the manufacturer installed it. Apparently it's been serviced in 2019 and they didn't update it then — but it's pretty likely that whoever installed it doesn't work there anymore, and nobody cares about these, as long as they work. Then they'll probably be replaced by whatever they're putting in them nowadays.

2025-05-13 04:13:08 UTC

Excuse me, my train seems to be having a kernel panic. No DRM for you today.
It's a Newag Impuls, ED78-002, Western Pomerania.
#Linux #train
https://cache.treehouse.systems/media_attachments/files/114/498/551/756/400/762/original/3e153668ce5d4188.jpg

2025-05-11 08:01:04 UTC

Gębczyce #granite mine.
#hiking
https://cache.treehouse.systems/media_attachments/files/114/488/142/839/679/532/original/1908d6d88994a9d1.jpg

2025-05-10 10:54:25 UTC

Past: "Michał, fix my laptop, it's not working right."
Today: "Michał, wipe that laptop clean, it's old and not working right, so I have to trash it."
(Do I have to add that mine is older?)
PS. Of course it will run Linux when I find a minute.
#ecology

2025-05-08 15:33:16 UTC

Given brutal opposition from other #Gentoo developers, I have withdrawn the patches to distutils-r1 that implemented experimental support for deduplicating installed files from #Python packages using symlinks. Per their argumentation, users who wish to save tons of space should just use a CoW-capable filesystem, and use a tool like duperemove.
The code will remain in #gpep517 for people who want to play with it, but it's only been tested to limited extent (i.e. within the bumps I've been doing the few last days), and without the eclass support I won't be able to pursue larger scale testing.

2025-05-07 05:31:45 UTC

Nowadays it may seem that computers (or computer software, to be more precise) are easier to use than years ago. I disagree.
In my opinion, it's much harder to just *use* anything today. That is, to make it perform the exact task we need from it, without interrupting us in our work and without doing anything undesirable. Today, programs tend to use us (and not in Soviet Russia but in Capitalist West). And instead of doing what we needed to do, we end up doing what software vendors expect us to do.
#enshittification #AntiCapitalism

2025-05-04 04:03:40 UTC

Wake up at 4 AM. Hear suspicious, silent beeping.
Did someone left the fridge door open? Nah, that kind of beeping would be louder.
Try checking the time on the phone. Try again. Discover that stupid Android froze in the middle of the night. So it's the charger whining!
Start nervously looking for the sports band on the table. Oh, it's 20 minutes to wake-up time.
Android got rebooted, whining didn't stop. Oh, I've left the laptop power supply plugged in!

2025-04-26 11:06:38 UTC

Fun fact: with #Python tarfile, the stream mode (`w|xz`) is faster than the regular mode (`w:xz`) for writing archives, but much slower (`r|xz` vs. `r:xz`) for reading them. For the latter, there's a rather simple pull request for a year now.
https://github.com/python/cpython/issues/132994
https://github.com/python/cpython/issues/121109

2025-04-24 13:20:21 UTC

I accidentally wrote "ewbuild", and it was so true.
#Gentoo

2025-04-18 06:16:23 UTC

"Fork you."
#FreeSoftware

2025-04-14 05:09:24 UTC

Internet is going great. Thanks to bot protection, you can't use #RSS / Atom feeds from #GNOME GitLab or #kernel cgit anymore. Which of course makes zero sense, because feeds are intended for machine consumption by design.
Honestly, #LLM #TechBros are the worst scum.
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/1962
https://bugzilla.kernel.org/show_bug.cgi?id=220009

2025-04-13 03:12:47 UTC

#EuroLLVM is a good opportunity to talk of the #LLVM community. No, not at the conference.
Because if you ever were wondering what LLVM project's attitude towards its volunteer contributors is, just look at the ticket prices. I mean, which volunteer would spend $750 on a conference ticket?!
But yeah, we know our place. It's to spend weekends fixing what corporate contributors broke through the week, then beg them to actually review our fixes before they break more. And in the meantime, our gracious lords will debate how to mess up our future even more.
https://llvm.swoogo.com/2025eurollvm
#OpenSource

2025-04-06 09:20:18 UTC

Slightly less technical today.
Many people don't appreciate the difference between #FreeSoftware and freeware (as in non-paid software). It's like assuming that a free world is the same as a world without prisons — except that the latter doesn't necessarily imply the former.
Most importantly, most of us aren't actually opposed to paying for software. Sure, we do often want our software to be freely available to everyone who needs them — and we do want software developers to be able to live a honest life without having to keep trying to find new ways of getting money from users to survive. But that's not the point of Free Software.
The most important thing about Free Software is the safety. The safety that if I choose to use this particular program today, then I will probably be able to keep using it a month from now, a year from now, perhaps even ten years from now. And there's a fairly good chance that I'll be able to save my work, and move it to another program. And if the program stops being developed by its original creators, then a community will form to take care of it.
There won't be a company asking me to switch to an absurdly expensive subscription in half a year, because they underestimated cloud costs. All my work won't suddenly be erased, because an algorithm flagged my account as suspicious. No company will tell me that my version is no longer supported, and I need to upgrade now — except that upgrade does a lot of unnecessary changes that I don't like, and on top of that messes up all my files. And when the company goes bankrupt, I won't lose everything, or end up with a program that eventually becomes broken — and all you can do is hammer around it, hoping you'll make it work a while longer.
I'm not claiming that Free Software is perfect, and the community is free from assholes with megacorporation-sized egos. But these essential freedoms are what makes programs sustainable. Even if you aren't a programmer and can't fix something yourself, you can pay somebody to do that — and I definitely prefer paying a honest man, to paying racket money to a corporation.

2025-03-30 14:08:35 UTC

I'd like to use the opportunity to reiterate my point about abolishing #DST, in a slightly different form.
Ask yourselves a bunch of questions:
1. How many devices automatically adjust to DST today, using a date-based algorithm?
2. How many of them get automatic timezone data (or software) updates? Or at least get updated periodically? And how many are going to require an intervention to get the algorithm updated?
3. How many of them actually permit algorithm updates? How many of them get software updates? And how many use software that was long abandoned, and perhaps the sources were lost in the mists of time? In other words, how many "can't do", and we're stuck with doing manual adjustments every half a year to keep the local time correct?
4. How many of these synchronize their UTC time, therefore overwriting our local adjustments? How many of them will permit disabling this synchronization, and how many will require us to physically block it instead? And how many will end up quickly collecting clock drift once the synchronization is off?
5. In the end, how many critical devices we're going to miss entirely, just because they "always worked" and nobody remembers about them anymore?
Sometimes I feel like people are thinking of abolishing DST as if they were living a hundred years ago. Unfortunately, today we're deeply computerized, and such a change requires a lot of preparation work, and readiness to intervene when things fall apart. What it doesn't require is a bunch of noisy politicians, waking up a month before each DST switch to philosophize on their couches. And in the end, such a reform will definitely mean trashing some otherwise good hardware that doesn't get updates anymore.

2025-03-20 17:08:45 UTC

Calling using #LineageOS be like:
1. You take the phone. Unlock it. Start Fossify dialer (because AOSP dialer is too broken to be used). The phone reboots.
2. You wait till it asks for PIN. You type the PIN in.
3. You wait till it starts. Then you turn the screen off, since you need to wait for SIM card to reboot too.
4. You take the phone. It turns out it turned itself off.
5. You start it again. Wait for PIN input. Input PIN.
6. You wait for it to boot. Turn the screen off.
7. You take the phone again. Turns out SIM card didn't reboot yet.
8. You wait some more. Finally, you can call!

2025-03-16 08:56:44 UTC

> InfiniBand
Looks inside.
> not infinite bandwidth

2025-03-07 05:00:11 UTC

- reply

@nprofile…fa4k, and I thought I'm having a poor reception and the image is not loading.

2025-03-02 12:08:06 UTC

Fun fact: in English, datum/data comes from a Latin word meaning "that is given". In #Polish, its equivalent "dana" / "dane" literally means "given".

2025-02-25 20:15:37 UTC

Beware, I'm going to say something wildly inappropriate.
I have some albums in 192 kHz / 24-bit FLAC, and some albums in 44.1 kHz / 16-bit FLAC — and I don't hear any difference. I mean, I don't have the same album in two variants to compare; but in general I can't tell if I'm listening to the lower or higher quality stuff. Horrible, isn't it?
And before you ask: yes, I have a hardware that can handle it. Well, except that my speakers are generally considered not-very-good-quality People's Republic of Poland stuff, but well, obviously I won't be replacing good speakers when they sound fine (yeah, I know I'm totally clueless, never heard really good speakers in my life, et cetera).
Well, but at least I definitely hear a difference between FLACs and whatever shit Spotify streams. Just saying.
#audiophile

2025-02-19 19:32:32 UTC

The best way to imagine how #RustLang maintenance looks like is to look at role descriptions of #Gentoo Rust team members: https://wiki.gentoo.org/wiki/Project:Rust

2025-02-19 11:07:12 UTC

As you're probably aware, the #English adjective "free" applied to software can be a bit ambiguous. It could either mean software respecting your freedoms ("#FreeSoftware"), or one that is available free of charge ("#freeware"). (Don't get me started on the assholes advertising demo or trial versions as "free software".) So, to disambiguate we sometimes use the term "libre", possibly as #FLOSS (free/libre open-source software).
Fortunately, we don't have this problem in #Polish. The "free of charge" meaning is translated into "darmowe" or "bezpłatne", while the other meaning goes as "wolne".
Well, except that "wolne" can also mean "slow". Which is fine, because I'm so tired of how fast things are moving. Let's make more "slow software".

2025-02-11 18:53:26 UTC

Today I'm posting on the company blog:
"""
In 2017, #PEP517 changed the #Python #packaging landscape forever. Prior to it, the setuptools build system held a de facto monopoly. If you were to publish a Python package on PyPI, you either used setuptools, extended it or had to create something reasonably compatible with it. And given how many different options setuptools provided, and how various users used different combinations of these options, you were likely to spend a lot of effort implementing what you believed to be necessary, and still learn that someone's workflow does not work.
PEP 517 enabled a ‘black box’ approach to building Python packages. A package needed only to name the backend it wished to use, and the backend implemented a few predefined functions to run the build process and create a source or binary distribution. This interface is well-defined and relatively simple. There are only two mandatory functions, and currently up to five optional — compared to 28 commands in setuptools (each with its own list of options).
Unsurprisingly, many new build systems were created. Some of them focused on pure Python packages, others on integration with other build systems such as CMake, Meson or Cargo. It is clear that you can now choose between many new build systems. But how popular are they today? In this post, I would like to explore that.
"""
https://labs.quansight.org/blog/pep-517-build-system-popularity

2025-02-08 19:43:32 UTC

Are you tired of OOM-killer being useless? Some random #C++ or #RustLang compilers are eating up all your RAMs, system is swapped to death, your whole X11 freezes and the best OOM killer can do is kill some tiny useless processes that don't make a difference? You keep bashing SysRq+f until it kills your whole desktop — and with some luck that actually kills the compiler.
So here's a little trick:
echo 1000 > /proc/self/oom_score_adj
…on the shell that you'll use to run the build. This is inherited by the spawned compiler processes, and adjusts their OOM score so that OOM killer will actually target them first.
#Gentoo #Linux

2024-09-28 15:46:49 UTC

New on blog: "The perils of transition to 64-bit #time_t"
"""
In the "Overview of cross-architecture portability problems", I have dedicated a section to the problems resulting from use of #32-bit `time_t` type. This design decision, still affecting Gentoo systems using glibc, means that 32-bit applications will suddenly start failing in horrible ways in 2038: they will be getting `-1` error instead of the current time, they won't be able to `stat()` files. In one word: complete mayhem will emerge.
There is a general agreement that the way forward is to change `time_t` to a 64-bit type. Musl has already switched to that, glibc supports it as an option. A number of other distributions such as Debian have taken the leap and switched. Unfortunately, source-based distributions such as #Gentoo don't have it that easy. So we are still debating the issue and experimenting, trying to figure out a maximally safe upgrade path for our users.
Unfortunately, that's nowhere near trivial. Above all, we are talking about a breaking ABI change. It's all-or-nothing. If a library uses `time_t` in its API, everything linking to it needs to use the same type width. In this post, I'd like to explore the issue in detail — why is it so bad, and what we can do to make it safer.
"""
https://blogs.gentoo.org/mgorny/2024/09/28/the-perils-of-transition-to-64-bit-time_t/

2024-03-29 07:53:24 UTC

A #Wikipedia editor has arbitrarily decided to remove #JPEGXL from the "Comparison of browser engines" table as "irrelevant", based on the #Google decision not to support it. That's a nice example of lack of objectivity, and letting the reality be defined by Google monopoly — and not even #GAFAM, because Apple supports the format.
https://en.wikipedia.org/wiki/Talk:Comparison_of_browser_engines#Support_for_Irrelevant_standards

2024-03-27 15:37:48 UTC

Err, why does #Mozilla #Firefox (a "private browser") for #Android require #Google Services Framework? And why does it include Google trackers?
https://reports.exodus-privacy.eu.org/en/reports/org.mozilla.firefox/latest/

2024-03-12 15:51:50 UTC

I suppose it's a public channel, so I can share this:
<fsf> Current voting results for "Accept Gentoo Linux as an associated project": Yes: 8, No: 0, Abstain: 0, Missing: 0 ()
That's from yesterday's #SPI, Inc. meeting. Still a few steps before it actually happens.
#Gentoo