- cross-posted to:
- programming@programming.dev
You must log in or register to comment.
This article is about AI stuff and I wonder if it’s written by AI too, because this is bullshit.
Their solution, External Data Representation (XDR), wasn’t over-engineering. It was essential for systems where data corruption could result in system failure. The Interface Definition Language (IDL) with compiler-generated stubs caught type mismatches at build time, not runtime.
MCP discards this lesson, opting for schemaless JSON with optional, non-enforced hints. Type validation happens at runtime, if at all.
Tons of web based APIs use JSON and still have strict compile time checking. The problem isn’t JSON.
I didn’t read the article yet, but maybe they’re not saying that JSON is schemaless, but that this is a usage of JSON with no schema. If that’s the case, the fact that it’s JSON doesn’t matter, but it being schemaless means there’s no defined contract, or that it’s very loose.
But also this article could be shit, idk yet
I may have misinterpreted tbh, it felt like they were saying JSON prevented it from having schemas but that may not have been the case.
