duped

Unless you use musl-gcc which is a proper GCC frontend with musl libc sysroot. The compiler is indeed (too) tightly coupled to its sysroot but linux is not special here. If anything interacts with the CRT it needs to know which CRT to use.

I'm not arguing that there aren't problems here, just that I think people have different expectations that are a little extreme. The libc implementation is a core part of the operating system, if you want to target that OS you should target that libc. Some distros (alpine) prefer musl libc, most prefer glibc. And distros really are different operating systems.

Why? If you compile your program against an older glibc it will run on newer glibc. glibc is the loader.

That's what I'm saying though, glibc-linked binaries are forwards (but not backwards) compatible.

The interpreter/loader is glibc and a key part of bootstrapping an executable built against glibc is loading libc itself before continuing on to load the program. Versioning is a problem when distributing binaries linked against a newer glibc to distros that ship an older one. The C compiler doesn't really care as much.

> all shared libraries depend on the specific glibc version to load them

Not really, though. glibc uses symbol versions that are forward but not backward compatible. If you got an error that said "this program was built for a newer version of <distro>" would you say the same thing?

Note this is the same (if not worse) on MacOS, and on windows you used to distribute the CRT with your application just to deal with the same problem.

I'm curious what the limiting factor is for "years not months" when building these fabs. DRAM is a commodity, there are only threeish major manufacturers, all have huge amounts of capital, multiple nations bend over backwards for new semiconductor production projects, and there seems to be unlimited money going into purchasing these things.

Even when it comes to manufacturing the tooling/testing infrastructure, it's just a question of money aiui.

Data centers directly led to my rates increasing over the last ~6 months where several came online locally without supply increasing. Natural gas prices also impacted it, but the data center buildout over the last year has not helped.

That article is two years out of date, and looking at nationwide electricity usage doesn't account for the local impacts of these data centers.

(* nb4 "it's summer": talking about price per kWhr)

The Chinese and Russians didn't double my electricity rates this year.

How much more value did those commits create than in 2025?

But that discards my point, which is that you should probably have been prevented from pushing all those to github unless you were paying them for it, but you weren't because the executives running github can't admit that AI is bad for their platform.

Microsoft executives have an incentive to pretend that AI is great and scaling it has no problems

Rust binaries are not static by default, they _statically link other crates_ by default. Subtle but important distinction.

The police cruiser's primary role is deterrence not investigation or data collection. A better comparison would be stasi informants.

This isn't an IDE, words do mean things

I mean I get that novice programmers might get tripped up on floating point representation but if you don't know "f32 can't represent 0.1 exactly" then you shouldn't yet be worried about the nuance of relaxing IEEE 754 compliance for the purposes of performance.

> C/C++ compilers give you a way out of this with the -fast-math

People should really use the individual optimization flags they want (no signed zeros, no trapping math, associative math, reciprocal math) and not -ffast-math because the other optimizations it enables leads to surprising code (for example, isinf and isnan may become noops, which will break production code).

Basically never use an optimization flag that changes the semantics of your code without understanding exactly what that means. I have had to fix this in a number of codebases because someone thought that flag was as innocuous as -O3.

And if you have to enable flush to zero/denormals are zero it should be explicit in your code and scoped.

The text of the bill is here: https://ilga.gov/Legislation/BillStatus/FullText?GAID=18&Doc.... There's about 3.5 pages of text defining this.

The relevant text doesn't call it an "algorithmic feed" for what it's worth. They define an "addictive" feed and it's essentially any kind of personalized recommendation.

> "Addictive feed" means a website, online service, online application, or mobile application, or a portion thereof, in which multiple pieces of media generated or shared by users of a website, online service, online application, or mobile application, either concurrently or sequentially, are recommended, selected, or prioritized for display to a user based, in whole or in part, on information associated with the user or the user's device, unless any of the following conditions are met.

The medical field is filled with charlatans and quacks. Elizabeth Holmes went to jail because she defrauded the wrong people.

What bothers me about the D'Addario thing is that it never crossed the mind of that employee or the company what they're doing was wrong.

Their customers are musicians. They want to hear what the strings sound like in a demo. What they did was not just dishonest, it's contrary to literally everything their customers do.

Whoever did it has no sense and shouldn't be working in that business. Full stop.

I say this as a D'Addario customer of 20+ years that will never buy their strings again.

The one thing that falls over is that the webhooks are actually self modifying code since you have an 'on commit' webhook that bootstraps the actions logic from the workflow.yaml file(s) (which are not really config files, they have logic that needs to be evaluated).

I don't disagree that it's obvious they've got problems but I'm just saying it's obvious to me the part that falls over (the scheduling of jobs) and why that would impact self hosted runners, which do no scheduling but depend on it to function.

As for 'just a message queue with some database updates and sharding that's easy to reason about'... Here's a job scheduling problem as an example: imagine you schedule a job, and there's no runner available. How do you disambiguate between no runners available because you've reached capacity, runners not being available because they're on a real network with faulty connections, and runners not being available because of a faulty rollout of internal updates?

A simple message queue for job scheduling is fine if you own everything and can deal with the operational overhead of identifying those cases by hand, but Github can't do that.

I'm not sure that it's that mind boggling. The entire complexity and value of GHA is not in the runners but the scheduler that the GH frontend hooks into and runners subscribe to jobs from. It's the most likely thing to fall over. '

If the scheduling was self hosted it would be inexcusable but you can always just connect whatever you want to webhooks.

The point I'm making is they're not entitled to scale a business if they can't scale responsibly

But they couldn't possibly do it at that the scale they're operating at. They couldn't hire enough people in the countries they operate, or know the language, or trust that who they do hire aren't corrupt or working against their interest. And they can't manually approve every ad, or make sure targeting isn't illegal or otherwise harmful.

---

This is sarcasm, by the way. Most decent people make sure what they're about to do won't harm other people and if would cause harm they wouldn't do it. But social media companies and ad networks aren't run by decent people. They're run by people who believe their business is entitled to infinite scale regardless of how many people are harmed along the way.

Just because it's by design doesn't mean it's good

Or their app was configured to let other LE agencies access it without their knowledge in violation of state law (1). Only linked one case but afaik it happened in a number of CA cities.

(1) https://www.malwarebytes.com/blog/privacy/2026/02/flock-came...

> The result is that software that can be personalized doesn’t need a plugin system or a config file.

Yes, please make me rebuild my software to change an API endpoint or port number. It's a wonderful use of time and electricity to build and spin up agents to fix the inevitable problems with building software. Instead of changing a string in configuration file.

(/s if not obvious).

Configuration and plugin systems exist for a good reason: software should be reconfigurable and modular without requiring the wholesale replacement of the original. Even if the code is open source, there are good reasons to move logic and data out of tree and into config or plugins.

No, I'm thinking of improperly stored gasoline evaporating and combusting.

Poorly stored gasoline can spontaneously combust, though. So more like a firebomb.

You don't find it useful that use after free, double free, uninitialized memory, and many kinds of race conditions are just impossible in code that compiles?

What exactly is the low level subset you feel like you can't use?

People find it immensely useful in practice, though.

I think the word "taxonomy" is a really good way to look at music theory. Really, the study is about giving names and notation to things in music so we can write and talk about it at all.

There's an interesting idea though that there could be a deeper why specific sounds and their combinations are the things we create names for, but that's an intersection of cognition/physics/culture that goes beyond elementary music theory.