4 ms·

I really wish we'd learn from Web 2.0. All the mistakes of "hey everything has an API now" that we learned from we're back to repeating. I feel like that meme

I really wish we'd learn from Web 2.0. All the mistakes of "hey everything has an API now" that we learned from we're back to repeating. I feel like that meme from Watchmen with the blue guy sitting on Mars.

deleted 1y ago
[deleted]
anildash 1y ago
Definitely having that feeling a lot these days watching the cycles repeat. I am tired of earth. These people. Their APIs.
olalonde 1y ago
What mistakes are we repeating?
- thuanao 1y ago
  Not understanding that businesses don't want open data or open protocols. Internet businesses want to monopolize information and charge rent for it. Capitalists don't want to commodify software, as that means lower profits and competition. They want to monopolize it. That's the whole game, except for companies selling physical goods over the Internet.
  - olalonde 1y ago
    So, is the idea that MCP might benefit from more built-in support for things like paid APIs to incentivize businesses?
    - thuanao 1y ago
      I think so. Though the premise of MCP betrays that AI isn't human-level intelligent. If it was there would be no need for a standard interface. It would be able to read API docs, navigate UIs to generate the proper keys, enter in billing info, and use all of that to make API requests by trial and error. That's what humans do.
      - 8note 1y ago
        i dont want to have to find it all those docs though. its much faster if i hand it a packet
  - riwsky 1y ago
    software capitalists don’t want to commodify software. But their complements do: I could totally see Apple pushing for something like this to make the iPhone more valuable and integrated.
- CSMastermind 1y ago
  Assuming people adopt MCP then: - JSON over the wire instead of binary - Schema optional with the spec only defining the envelope - Lack of inheritent support for code generation - Poor support for flow-control or multiplexing - Deadlines/timeouts, compression, per-call metadata, bi-di streaming, TLS, load-balancing hints: none of it standardized - No inbuilt payment mechanism

deleted 1y ago

[deleted]

anildash 1y ago

Definitely having that feeling a lot these days watching the cycles repeat. I am tired of earth. These people. Their APIs.

olalonde 1y ago

What mistakes are we repeating?

thuanao 1y ago
Not understanding that businesses don't want open data or open protocols. Internet businesses want to monopolize information and charge rent for it. Capitalists don't want to commodify software, as that means lower profits and competition. They want to monopolize it. That's the whole game, except for companies selling physical goods over the Internet.
- olalonde 1y ago
  So, is the idea that MCP might benefit from more built-in support for things like paid APIs to incentivize businesses?
  - thuanao 1y ago
    I think so. Though the premise of MCP betrays that AI isn't human-level intelligent. If it was there would be no need for a standard interface. It would be able to read API docs, navigate UIs to generate the proper keys, enter in billing info, and use all of that to make API requests by trial and error. That's what humans do.
    - 8note 1y ago
      i dont want to have to find it all those docs though. its much faster if i hand it a packet
- riwsky 1y ago
  software capitalists don’t want to commodify software. But their complements do: I could totally see Apple pushing for something like this to make the iPhone more valuable and integrated.
CSMastermind 1y ago
Assuming people adopt MCP then: - JSON over the wire instead of binary - Schema optional with the spec only defining the envelope - Lack of inheritent support for code generation - Poor support for flow-control or multiplexing - Deadlines/timeouts, compression, per-call metadata, bi-di streaming, TLS, load-balancing hints: none of it standardized - No inbuilt payment mechanism