AI companies are reinventing REST with MCP while abandoning XSLT, which is seen as a more efficient and RESTful approach for LLMs.

I still can't wrap my head around AI companies trying to reinvent REST with MCP at the same time they kill off XSLT A single server shipping XSLT provides proper RESTful content for LLMsLLMs with schemas and self a documenting APIs. The same endpoint tells browsers where to find templates to render a webpage out of iit 🔗 https://tonysull.co/death-of-xslt

I still can't wrap my head around AI companies trying to reinvent REST with MCP at the same time they kill off XSLT A single server shipping XSLT provides proper RESTful content for LLMs with schemas and self a documenting APIs. The same endpoint tells browsers where to find templates to render a webpage out of it 🔗 https://tonysull.co/death-of-xslt-mw23h36a

I still can't wrap my head around AI companies trying to reinvent REST with MCP at the same time they kill off XSLT A single server shipping XSLT provides proper RESTful content for LLMs with schemas and self a documenting APIs. The same endpoint tells browsers where to find templates to render a webpage out of it Instead we're left having to create yet another bespoke API implementation for every service and fight to keep them all up to date and tested 🔗 https://tonysull.co/death-of-xslt