Why MCP’s Disregard for 40 Years of RPC Best Practices Will Burn Enterprises
(julsimon.medium.com)
from vermaterc@lemmy.ml to programming@programming.dev on 10 Aug 10:38
https://lemmy.ml/post/34445467
from vermaterc@lemmy.ml to programming@programming.dev on 10 Aug 10:38
https://lemmy.ml/post/34445467
#programming
threaded - newest
This is what happens when we remove the science from CS and start vibing.
I don’t think it has anything to do with vibe coding, the problem with MCP is just it needed to be done fast (because otherwise another protocol would appear and get all the hype) and needed to be very easy to use for hobbyists (again: to get hype, Enterprise software is boring)
Yeah the principal engineer at my company is just smashing his keyboard every day to implement MCP services and shit and in the meantime is fucking up our repo and I’m trying to clean up the mess but all upper management cares about is “when AI?”
He’s not vibe coding it, but as with all the MCP specs, it’s ignoring many things about type safety and the like pointed out in this article
What you’re describing is definitely the AI vibe: full speed at the cost of quality, logic, and all else.
To (quite badly) paraphrase Woody Allen:
“The quality of this code is so bad.”
“Well, at least there’s a lot of it.”
What’s the original quote?
www.youtube.com/watch?v=lDxE4r5ixD0
Sounds like JavaScript
I’m just here for the Seventh Seal picture. Y’all can ignore me.
Why did we need another competing web API standard?