Post #2170517

2026-05-04 10:47 UTC

And yes, it means governments should stop trying to develop code - a thing which they never ever done well. They should do what they actually know how to do - build public institutions, shared standards and requirements. They should invest in free education, knowledge sharing, and communication infrastructure.

Replies (2)

@michelin@hachyderm.io 2026-05-04 11:10

@bookwar the USA login.gov is actually very nice! But I don't know how much that is integration work vs developing key components In general I agree though, the recent EU forks seem completely unnecessary, and I say this as someone who agrees with the need for tech "sovereignty" (not sure I like the term)

Open ##2170518
@EdBruce@infosec.exchange 2026-05-04 19:50

@bookwar Nearly 5 decades ago pretty much 100% of the code I developed was for government work. My first job was a major upgrade of government developed system that had been running successuflly for over 2 decades. We were using a programming language developed by the government. This was on hardware built by private companies to government specs and requirements. Funny thing when Reagan came in and pushed COTS I regularly started seeing articles in RISKS about all the failures in the real world when military systems started using Windows and lots of non-government developed systems. Oh and that first system I worked on went back to work on a contract to maintain it. Was a nightmare of COTS hardware and software. The team I was on convinced them to swtich to C, I left and watched that ship sink from afar.

Open ##2170519