ESBMC: https://esbmc.github.io/

A good plan... if you can afford to maintain your fork forever.

Google and MS could do it

I think that the issue is not the XSLT implementation (that could be contained), but its deep intégration in the XML stack which is part of web pages processing. Think about XML "processing instructions".

No. Keep using XSLT server side.

In an XML document a "processing instruction" can trigger the XSLT processor to transform the document in another format.

So an XML document would be parsed and processed by the XML engine, trigger XSLT processor, which would then trigger again the XML processor again and the HTML processor.

So XSLT processing for XML/XHTML is deeply embedded. Dropping it removes a lot of corner cases that AI is good at exploiting.

Cool project. Empty repo? https://github.com/justjake/fujimod Not much interested in the code, more in the development process (prompts, skills).

That other thread is interesting as it raises issues about how the organization is managed money-wise: https://news.ycombinator.com/item?id=50082093

Link!

Schedule the morning coffee in HomeAssistant?

Taking stimulants before your body has had a chance to spin up natural production is counter-productive.

If the washing machine is on the network, its manufacturer is already aware about its age.

Its manufacturer's competitor isn't, though, and they're probably really interested in that marketing info.