82
Why MCP’s Disregard for 40 Years of RPC Best Practices Will Burn Enterprises (julsimon.medium.com)
submitted 1 year ago by to c/programming@programming.dev
9 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [S] 15 points 1 year ago* (5 children)

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)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 10 points 1 year ago* (2 children)

    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."

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago (1 child)

    What’s the original quote?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 8 points 1 year ago

    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

  • permalink
  • fedilink
  • source
  • parent