• 0 Posts
  • 111 Comments
Joined 2 years ago
cake
Cake day: July 14th, 2023

help-circle



  • It’s the problem, but also the strength. That fragmentation allows room to experiment.

    It also puts pressure on the underlying protocols/specs to be air-tight. If you have just one implementation to support, you can do whatever. If you have to support 15, all with different goals and constraints, you gotta be pretty damn careful.

    So in the end, we get foundational systems that are able to evolve over time instead of needing a breaking-change, ground-up rewrite every 2 years.


  • This is basically what the Luddites were fighting against:

    A world where labor has no opportunity to develop skills or use them, no authority over the machinery which dictates the nature of what is made and how, chasing fewer and fewer jobs for less and less pay.

    Their solution was to take sledgehammers to the factories. The owners, of course, hired thugs to shoot them. And the politicians ruled that the machines were sort of the property of the crown, and therefore destruction of these machines should be punishable by public execution.

    Funny enough, data centers today are considered strategic assets under the protection of DHS. Which is a fancy way of saying: still owned by the crown, still gonna shoot you if you try to negotiate via sledgehammer.






  • I’d settle for just requiring interoperability. Seems like a reasonable requirement for a government to demand the ability to change vendors.

    We have that requirement when it comes to munitions. You’re not allowed to sell the military a gun for which you are the only ammo manufacturer.

    A side effect would probably be that more commercial software would be interoperable as a result, just because it’s easier for the vendors to maintain a single product rather than wildly different variants.