I'm still laughing on how the error handling for tools is done, it's just a boolean field IsError.

https://modelcontextprotocol.io/specification/2025-06-18/ser...

There is a difference between protocol error and tool usage error, makes sense you want the model to see the tool usage error, so they can correct.

I'm guessing it has a the same shape as a normal message + IsError so on the handling side you don't really have to do anything special to handle it, just proceed as normal and send the results to the LLM so it can correct if needed.

Because they don't have exclusive control, unlike social media where you can't take your data and move it to another provider, you can just take your repo to whichever provider or self-hosted GitOps option you want.

Not only can you take it with you, every developer already has a local copy of the entire repository.

The real value IMHO of github is the issue tracker and the visual diff/display of PR changes.

Then you have to replace those professionals with even more specialized and expensive professionals in order be able to deploy anything.

Because they are used to the even insaner markup of smaller retailers that would ask 10USD for an IC that cost 5 cents at bulk

Probably architecture changes (x86 has a lot of historic baggage that difficults newer designs) and also more specialized hardware in the CPU, probably this might also be one of the reasons Apple went this way with the M Silicon

Does it really matter? i've run Minecraft servers with Coretto 21 on Arm and had no issues at all even with the weird setup

Ive honestly never heard of coretto but it seems to be basically openjdk 21 under the hood so I don't see why that'd be a problem.

Could pumped-storage batteries help in that case?

People using consumer generative AIs are already using it for free, or very cheaply. It may be hard for falling costs to drive more demand.

Relevant: https://xkcd.com/927/