21–30 of 129 posts
Understatement of last year. It was a horrific standard and was a completely broken one security-wise from day 0. The folks who wrote it have never written an RFC or an internet standard before. Remember the VCs screaming about MCPs all day long last year? Well I don't see them doing that at all anymore, and called that 1 year ago. [0] [0] https://news.ycombinator.com/item?id=43486516
AI for coding itself is a fad
strongly agree! can't see any use of LLMs beyond tabcomplete and navigating an unknown codebase.
Also most people who I see succeed from the start are technical managers. That is people who can code, who are used to delegate (good at phrasing) and are more likely to accept something that works even though is not character by character what they expected.
I don't think MCP is a fad - I think it is the 2020s equivalent of: - Active X - asbestos - leaded gasoline and paint - radium medicines Well, with the exception of the first 3 actually being quite useful.
AI for coding itself is a fad
MCP is just a small, boring protocol that lets agents call tools in a standard way, nothing more. You can run a single MCP server next to your app, expose a few scripts or APIs, and you are done. There is no requirement for dozens of random servers or a giant plugin zoo. Most of the “overhead” and “security nightmare” worries assume the worst possible setup with zero curation and bad ops. That would be messy with any…
I found it a common misconception so I wrote about it here https://goto-code.com/dont-sleep-on-mcp/
This analysis dismisses MCP by focusing too narrowly on local file system interactions. The real value isn't just running scripts; it's interoperability. MCP allows any client (Claude, Cursor, IDEs) to dynamically discover and interact with any resource (Postgres, Slack) without custom glue code. Comparing it to local scripts is like calling USB a fad because parallel ports worked for printers. The power is standardi…
This analysis dismisses MCP by focusing too narrowly on local file system interactions. The real value isn't just running scripts; it's interoperability. MCP allows any client (Claude, Cursor, IDEs) to dynamically discover and interact with any resource (Postgres, Slack) without custom glue code. Comparing it to local scripts is like calling USB a fad because parallel ports worked for printers. The power is standardi…
Understatement of last year. It was a horrific standard and was a completely broken one security-wise from day 0. The folks who wrote it have never written an RFC or an internet standard before. Remember the VCs screaming about MCPs all day long last year? Well I don't see them doing that at all anymore, and called that 1 year ago. [0] [0] https://news.ycombinator.com/item?id=43486516
You say "have never written an RFC or an internet standard before" as if that's a disadvantage.