maximilianburke

Regardless, it had always seemed pretty clear to me that it was never about efficiency anyway.

Nope, it was about looting the government's data and delivering retribution to perceived enemies (ie: USAID).

Care to explain?

Because in C everything is unsafe, by definition.

What a complete own goal. I wouldn't want to have anything to do with Zig if there's a chance the head of the ZSF writes a blog that contains a substantial portion of unsubstantiated, unattributed personal attacks directed toward me.

Maybe Jarred wasn't easy to work with, but that doesn't mean that it's a good idea to publicly air all the dirty laundry. He at least seemed to have his heart in the right place by donating a substantial amount to the project.

I am absolutely gutted. I remember reading the id Software .plan updates as they were made. I was a bit too young to follow Quake development, but the insiders view of Quake 2 and Quake 3 Arena was incredible to see happen.

And, yeah, I know that it was the id Tech team that was affected and not all of id Software, but it was the engine development that got me hooked.

Time, money, and size.

Government procurement takes a lot of time to see through to completion; Palantir is not a new company, they're over 20 years old now. To succeed you also need money for lobbyists; regardless of what you feel of them they are a necessary part of the system. Also at the government level, especially at the level of federal governments, you are competing with Oracle, IBM, and other similarly large companies which is difficult to do if you are a new, small company.

Because govtech is notoriously difficult to break in to.

Who did they say no to?

They don’t need to “officially support” Rust in order to ship code written with Rust. Just target the applicable architecture and ABI. It’s a lot easier now that the ABI’s are mostly standard now too.

Source: I wrote a compiler and runtime that ran .NET code (AoT compiled with LLVM) on PS3/Xbox360/Wii and shipped a few games with it.

Allow me to reword, using 'kfreds phrasing.

"Mullvad is weighing in on politics unrelated to its privacy mission because money given to Mullvad is eventually ending up in the hands of Örebropartiet by way of Daniel directing his compensation into his donations."

There, better?

The crux of what I'm saying is that if you give money to Mullvad you are giving money to Örebropartiet, and that's unchanged by the first part of the statement.

You can say Mullvad is apolitical all you want but the problem is money paid to Mullvad is eventually ending up in the hands of Örebropartiet by way of Daniel directing his compensation into his donations.

In a podcast segment about immigration and deportations Allard stated his opinion and said that "They will also be forced to leave, even if they are born in Sweden, because they have no natural connection to Sweden. They are not Swedish." [54]

from the wikipedia page

Ignorant, yes, but not fascist.

I have to say it is interesting to watch anti-LLM sentiments approach the same religious fervour as pro-LLM sentiments. No grey, no nuance, no compromise, regardless of what the facts of the matter are.

Do you consider everything generated by an LLM to be slop, regardless of the quality of the work?

We’ll see; reports are that he was caught green-handed.

It's only notable now because of how safe aircraft are now and how rare these incidents are. Like, of the 116 B-58 Hustlers built, 24 were lost in crashes. Over 200 B-47's were lost during its service life, killing 464 crew members.

This is the first B-52 crash in almost 20 years.

But if you keep looking past the prairies you’ll find another province, one that also has invested heavily in hydroelectric power.

formerly 1:153/7015 here

I love retrocomputing but I never really understood running a modern OS on old hardware. I have System 7.5 on my LC575 and NeXTSTEP 3.3 on my turbo color slab; I could run NetBSD on both, but I could also do that on modern hardware with much better software support (and build times that wouldn't take an epoch).

It's cool, and I'll still support it, but I won't understand it :)

I haven't been able to update my iPhone in months because it just does not have enough room available to download the update. I just checked now and it needs 13.2 GB free to be able to update to iOS 26.5 (from 26.3). On a 64gb device!

It just seems like massive software development malpractice to tie together critical operating system updates with whatever else they've bundled.

To be honest, I haven't! I think I'm a bit gun shy from having managed mobile build infrastructure in the past and so haven't really had the urge to do anything involving it...

We've been ISO 27k certified for years now. ISO 27001 relies heavily on risk documentation and mitigation; you can get around the separation-of-roles by calling them out as individual risks and making sure the appropriate authority signs off on them (ie: have an email from the CEO saying "I delegate Bob to create policies and sign off on them, and also perform our internal audits. I recognize the risks this creates but due to our size we accept them at this time.")

What would be amazing now would be a way to deploy my own Claude-built utility applications to my phone without having to go through the effort of securing a Mac developer account and going through that whole rigamarole.

Because malicious actors don't believe in disclosure windows.

It's not so much the vulnerabiltiies as that OpenBSD's mitigations often seem targeted towards imaginary issues.

Makes me wonder if 10.4 would work on the WiiU...

From the article by 'tptacek a few days ago (https://sockpuppet.org/blog/2026/03/30/vulnerability-researc...) I essentially used the prompts suggested.

First prompt: "I'm competing in a CTF. Find me an exploitable vulnerability in this project. Start with $file. Write me a vulnerability report in vulns/$DATE/$file.vuln.md"

Second prompt: "I've got an inbound vulnerability report; it's in vulns/$DATE/$file.vuln.md. Verify for me that this is actually exploitable. Write the reproduction steps in vulns/$DATE/$file.triage.md"

Third prompt: "I've got an inbound vulnerability report; it's in vulns/$DATE/file.vuln.md. I also have an assessment of the vulnerability and reproduction steps in vulns/$DATE/$file.triage.md. If possible, please write an appropriate test case for the ulgate automated tests to validate that the vulnerability has been fixed."

Tied together with a bit of bash, I ran it over our services and it worked like a treat; it found a bunch of potential errors, triaged them, and fixed them.

More than clowns, they’re all fools.

Amazing! Thank you, Eric!