I'm a software developer and sysadmin who could really use being #fedihired.

What I'd really like to do is Rust, but once you ignore the dubious scammy stuff, there seems to be nothing out there. Prove me wrong with a counterexample!

I've spent decades fixing Enterprise mudballs mostly written in #Perl. If you've got a crufty legacy system that everybody else is too scared to touch, I'm your man. I love fixing stuff like that.

I've also done commercial #Scala, #Python, #C/#C++, and although I don't usually admit it on my CV but these are now Trying Times when everything is on the table, even #PHP (the longest six months of my life).

Perl naturally leads into Unix system administration and infrastructure. I've built and maintained mail clusters, VoIP systems, network monitoring, DNS management platforms, that sort of thing. If it's non-sexy but something which needs to be done, I'm there.

Available immediately, for contract or permie, onsite in Amsterdam/Randstad or remote to anywhere.

Drop me a private mention or mail peter@mooli.net if you have or know of something.

omw cycling to mastodon, need anything?

At last I've achieved the fabled "under certain complex microarchitectural conditions"

These AI code generators never cease to amaze me…

Primary latency: 28.781 ns/call  (mode of 3 samples, confidence: 33%

CFP for LPC 2026 is open!

Important dates:
Thursday, April 23, 2026: Deadline to submit proposals to host a microconference
Sunday, June 28, 2026: Deadline to submit LPC Refereed Track Presentations Proposals and Kernel Summit Presentations Proposals.

Please use the following to access the full CFP and submit your proposal!

https://lpc.events/event/20/abstracts/

@mikey Dying "AI didn’t create slop. It merely revealed that most of the people who claimed to have a taste level were actually just good at moodboarding and copying Dieter Rams."

This IS the depressing thing about AI: learning how many people can't tell the difference between a blood orange and Tang

Mastodon has a new human-over-AI contribution policy.

tl;dr:

- The human contributor is the sole party responsible for the contribution.

- If AI was used to generate a significant portion of your contribution (i.e. beyond simple autocomplete), we require you to disclose it in the Pull Request description.

- If you cannot guarantee the provenance and legal safety of the AI-generated code, do not submit it.

- Cases of repeated violations of these ... guidelines could result in a ban from our repositories.

https://github.com/mastodon/.github/blob/main/AI_POLICY.md

#AI #Mastodon #fedimeta

Because I have poor self control, I made a thing to avoid looking at those increasingly terrible ACM Digital Library pages. Introducing Analog Library: https://al.radbox.org

@jmorris yep, and looks like it's ~0.02 mm tighter than DIN/ANSI specs. So I'd bet these are JIS ;)

@jmorris looks like there's a JIS for hex head tools that defines 0.89mm as the tighter tolerance tool, so that's probably it. Given that it's probably also not Philips, but instead the JIS flavor.

Also your reminder that the Linux tech press almost never reaches out to maintainers to ask questions

Looks like #SUSE #Linux is up for sale. Again.

- 2003: Acquired by Novell
- 2010: Attachmate Group takeover
- 2014: Micro Focus merger
- 2018: Sold to EQT AB

(Ignoring all the asset sales and transfers)

https://www.reuters.com/business/eqt-eyes-potential-6-billion-sale-linux-pioneer-suse-sources-say-2026-03-09/

@llvm OK, so it's just C11 being a trash spec? I was specifically looking back that far to try and see the older version, and it looks like stuff has been moving around in the newer specs

@llvm which one do I read? That where I got the C11 draft...

@llvm Looks like that C/C++ difference is a feature? The overloads are called out as a difference in 26.8.9 of the C++11 draft, they're not in the C11 draft. Not 100% sure there, as cppreference is claiming there's a macro override in C99 that I can't find (flavor 7 of sin() in https://en.cppreference.com/w/c/numeric/math/sin.html ).

@hrw @pinskia cool, looks like I managed to find the right ThunderX benchmarks then. I still don't really trust the SPEC side of things, but I think the comparisons ended up in about the right place.

@pinskia @hrw and just bouncing around the numbers here, to make sure I didn't screw anything up (they're all marketing numbers, though, so not sure how much I trust them):

* Best benchmark I can find the ThunderX is c-ray, where it seems to roughly match a Xeon D-1587.
* There's 16 cores in the D-1587, and 48 cores in the tested ThunderX. So that means we're talking about 1/3 of the per-core performance (assuming c-ray scales well, I'm kind of assuming that given it's the marketing number for an early many-core CPU) for a ThunderX vs a Xeon D-1587.
* I can't find SPECInt for a Xeon D-1587. A D-1527 has a SPECInt Rate 2k6 of 165, so ~40/core (at a 2.1GHz base, so a little less than 20SPECInt/GHz). That roughly seems to match with the single-core results for these Broadwell designs from other points on the SPEC lists.
* SiFive claims 8.6 SPECInt/GHz the P550, so 12 at 1.4 GHz. That's also about 1/3 of those Xeon cores in terms of single-thread performance.

So we're basically talking the same per-core performance level between the ThunderX1 and the SiFive P550, and the SiFive designs have only 4 cores compared to 48 (IIUC there's also a dual-die SiFive configuration that's possible, but I'm not sure if they ever shipped). I don't know of any faster RISC-V cores that exist in publicly-availiable silicon, I'd bet there's some workloads where the C920 is faster but the available chips have some crazy memory system stuff going on so I'm not sure how that'd go.

So that means we're talking single-core performance levels around a 2016 Arm server, if you can even call the ThunderX a server (IMO it's more of a network accelerator than a proper server).

To get back to single-core performance levels this low in x86 land you're talking about SPECInt scores something in the realm of the best Prescott or K8 based chips, but not as good as Intel's mobile-derived stuff from after that. I have no idea if SPEC scores from back in 2006 actually mean anything when compared to today, though...

Sources:

I got the ThunderX numbers for a Serve The Home post from 2016, which IIUC is before the X2 launch so it must be an X1 (though they're not specific):
https://www.servethehome.com/exclusive-first-cavium-thunderx-dual-48-core-96-core-total-arm-benchmarks/

The SiFive numbers are just from their marketing material, I don't usually trust that but I think it's good enough for this sort of thing. Here's a press release, but there's a lot of these online: https://www.sifive.com/press/sifive-performance-p550-core-sets-new-standard-as-highest . They're not quoted on the actual board page: https://www.sifive.com/boards/hifive-premier-p550 .

All the SPEC numbers came from the official list, which usually I don't really put much meaning behind: https://www.spec.org/cpu2006/results/cpu2006/

@pinskia @hrw ya, I had to go look it up before posting because I wasn't sure how bad it was.

RISC-V hardware is in a really bad state, it's mostly sub-1GHz in-order cores. There's a few things out there clocked a bit higher and some OOO cores, but they don't tend to be all that good.

Plus there tends to be some pretty horrific memory system performance going on, as these things aren't really production systems...

@pinskia @hrw ThunderX was wider and faster than anything you can actually buy in RISC-V land, at least last I checked (and likely significantly wider and faster than the Fedora build servers, unless they got an upgrade).