zambachi

5 ms·

1.
by zambachi 1y ago
Yet what we’re seeing on the web with Typescript components turning to a pretty version of MFC minus the right/middle-click capability. The “single-page app” becoming a defacto standard mode of development. Looking at the Fluent design
2.
by zambachi 1y ago
From the spec: https://modelcontextprotocol.io/specification/2025-03-26/ser... “ For trust & safety and security, there SHOULD always be a human in the loop with the ability to deny tool invocations. Applicati
3.
by zambachi 1y ago
How does MCP not use existing standards when the reference transport is SSE on HTTP with a JSON RPC payload?
4.
by zambachi 1y ago
I disagree on the advantages of wisdom as these days I’m thinking the opposite: 1) Lack of wisdom leads to reinvention of the wheel. How many programming languages are there only now doing things the same way as 30 years ago? What is novel
5.
by zambachi 1y ago
JavaScript, HTML, and CSS have changed a lot since 2012. I think the problem is folks tend to think like engineers with all their widgets (e.g desktop development in the browser). Even Microsoft is going full TypeScript mode. Web developmen
6.
by zambachi 1y ago
How is the MCP API bad? It uses simple and widely available standards-based transports while still allowing custom transport implementations, along with a simple API that can be used easily without any libraries, in any programming language
7.
by zambachi 1y ago
I think people often think of their specific use-case and tend to forget the bigger picture. MCP does not force one transport or the other and that is great—use any transport you want as long as it uses JSON RPC as the payload. The two buil