You should throw in CORBA from the 90s for completeness.
My view mostly it was a confluence of poor dev experience and over-engineering that killed them.
Some of those protocols were well designed. Some were secure, all were pretty awful to implement.
It’s worthwhile calling out REST as a long term success. Mainly because it was simple and flexible.
Whether MCP will have that staying power I dunno, personally I think it still has some flaws, and the implementation quality is all over the shop. Some of the things that make it easy (studio) also create its biggest flaws.
Move beyond benchmarks… proceed to list a bunch of benchmarks.
The problem for me is that it’s not worth running these myself, yeah I may pay attention to which model is better at tool calling. But what matters is how well it does at my use case.
I agree with you on the quality of the study. My point was that value shouldn’t be considered a given, we’re still figuring it out.
In my team I see examples like yours, but I also see engineers having to clean up slop when one of them got over their skis.
My _belief_ is that it’s a net positive, but we’re far from taking that as a hand wave fact. And it certainly ain’t the 5-10x people are shouting across the board.
As kids we used to have great fun knocking rocks together around sunset to get them to call back. Kinda like beetle bird calls.