pull down to refresh

100 sats \ 1 reply \ @k00b 12 Aug \ parent \ on: Why MCP’s Disregard for 40 Years of RPC Best Practices Will Burn Enterprises AI
We don’t disagree about better specs being better or MCP having flaws (I haven’t looked very closely but it’s safe to assume it has many). Protocol economies just seem to have a mind of their own and produce spaghetti specs more often than not, so I see wanting a different spec (after one is widely adopted) like wanting an exception.
I don't read this as a complaint, but as great advice for whatever comes next.
That’s a fair reading. Complaint was a poor word choice. The author seemed frustrated was what I meant.
write
preview
100 sats \ 0 replies \ @optimism 12 Aug
I don't think you said complaint - I was just trying to put it in perspective, so it's my poor choice of words haha.
In the end, I've been on protocol design teams, lead them, and in an unfortunate situation been the whole team by myself. But I haven't jumped in to help. So ultimately the blame is on me, and every other experienced protocol designer that didn't help with me.
reply