10 ms·

I agree with the article, and I love how the author is (mis-)using MCP. I just want to rephrase what the accident actually is. The accident isn't that somehow

by phh 1y ago

I agree with the article, and I love how the author is (mis-)using MCP. I just want to rephrase what the accident actually is. The accident isn't that somehow we got a protocol to do things we couldn't do before. As other comments point out MCP (the specificaiton), isn't anything new or interesting. No, the accident is that the AI Agent wave made interoperability hype, and vendor lock-in old-fashioned. I don't know how long it'll last, but I sure appreciate it.

iLoveOncall 1y ago
> I don't know how long it'll last I'm just baffled no software vendor has already come up with a subscription to access the API via MCP. I mean obviously paid API access is nothing new, but "paid MCP access for our entreprise users" is surely on the pipeline everywhere, after which the openness will die down.
- Bjartr 1y ago
  And I expect there'll eventually be a way for an AI to pay for an MCP use microtransaction style. Heck, if AIs are at some point given enough autonomy to simply be given a task and a budget, there'll be efforts to try to trick AIs into thinking paying is the best way to get their work done! Ads (and scams) for AIs to fall for!
  - iLoveOncall 1y ago
    > Heck, if AIs are at some point given enough autonomy to simply be given a task and a budget, there'll be efforts to try to trick AIs into thinking paying is the best way to get their work done! We're already there, just take a look at the people spending $500 a day on Claude Code.
- adamesque 1y ago
  I think for enterprise it’s going to become part of the subscription you’re already paying for, not a new line item. And then prices will simply rise. Optionality will kill adoption, and these things are absolutely things you HAVE to be able to play with to discover the value (because it’s a new and very weird kind of tool that doesn’t work like existing tools)
- pininja 1y ago
  Mapbox is just a small step away from that with their MCP server wrapping their pay-by-use API. I wouldn’t be surprised to see a subscription offering with usage limits if that somehow appealed to them. MapTiler already offers their service as a subscription so they’re even closer if they hosted a server like this on their own. https://github.com/mapbox/mcp-server https://github.com/mapbox/mcp-server
sshine 1y ago
Hype, certainly. But the way I see it, AI agents created incentives for interoperability. Who needs an API when everyone is job secure via being a slow desktop user? Well, your new personal assistant who charges by the Watt hour NEEDS it. Like when the CEO will personally drive to get pizzas for that hackathon because that’s practically free labor, so does everyone want everything connected. For those of us who rode the API wave before integrating became hand-wavey, it sure feels like the world caught up. I hope it will last, but I don’t know either.
- mh- 1y ago
  Unfortunately, I think we're equally likely to see shortsighted lock-in attempts like this [0] one from Slack. I tried to find a rebuttal to this article from Slack, but couldn't. I'm on a flight with slow wifi though. If someone from Slack wants to chime in that'd be swell, too. I've made the argument to CFOs multiple times over the years why we should continue to pay for Slack instead of just using Teams, but y'all are really making that harder and harder. [0]: https://www.reuters.com/business/salesforce-blocks-ai-rivals-using-slack-data-information-reports-2025-06-11/ https://www.reuters.com/business/salesforce-blocks-ai-rivals...
  - ebiester 1y ago
    It's going to take more people willing to move away from slack for those purposes. As it is, I'm going to propose that we move more key conversations outside of slack so that we can take advantage of feeding it into ai. It's a small jump from that to looking for alternatives.
    - sshine 1y ago
      The argument used to be “Let’s move FOSS conversation out of {Slack, Discord} because they prevent conversations from being globally searchable, and they force individuals into subscription to access history backlog.” Getting indexed by AI crawlers appears to be the new equivalent to getting indexed by search engines.
  - dgacmu 1y ago
bitwize 1y ago
Remember Web 2.0? Remember the semantic web? Remember folksonomies? Mash-ups? The end of information silos? The democratizing power of HTTP APIs?Anyone? Anyone?
- karaterobot 1y ago
  I don't understand your point. Some of those things were buzzwords, some were impossible dreams, some changed the way the web works completely. Are you just saying that the future is unknown?
  - klabb3 1y ago
    No. What they are saying is best said with a quote from Battlestar Galactica: > All of this has happened before, and all of this will happen again. ”It” here being the boom and inevitable bust of interop and open API access between products, vendors and so on. As a millenial, my flame of hope was lit during the API explosion of Web 2.0. If you’re older, your dreams were probably crushed already by something earlier. If you’re younger, and you’re genuinely excited about MCP for the potential explosion in interop, hit me up for a bulk discount on napkins.
    - bwfan123 1y ago
      And then, there are "architecture astronaut"s dreaming of an entire internet of MCP speaking devices - an "internet of agents" if you will. That is now requiring a separate DNS, SMTP, BGP etc. for that internet.
    - fragmede 1y ago
      I'm older and would like a discount please. The "this time it's different" energy is because assuming a human can interact with the system, and that vision models can drive a gui, who cares if there's an actual API, just have the AI interact with the system as if it was coming in as a human.
    - danielrico 1y ago
      I think battlestar Galactica must be quoting one of the Eddas. I've only read if it from Borges in Spanish, but Conner the same meaning: "Estas cosas han pasado. Estas cosas también pasarán."
adregan 1y ago
How ironic given the amount of APIs that were locking down access in response to AI training! Though the general API lockdown was started long before that, and like you, I’m skeptical that this new wave of open access will last if the promise doesn’t live up to the hype.
- TimTheTinker 1y ago
  MCP is supposed to grant "agency" (whatever that means), not merely expose curated data and functionality. In practice, the distinction is little more than the difference between different HTTP verbs, but I think there is a real difference in what people are intending to enable when creating an MCP server vs. standard APIs.
  - adregan 1y ago
    Might be another reflection of McLuhan‘s “the medium is the message” in that APIs are built with the intended interface in mind. To this point, GUIs; going forward, AI agents. While the intention rhymes, the meaning of these systems diverge.
- notatoad 1y ago
  i don't think it's ironic at all. the AI boom exposed the value of data. there's two inevitable consequences when the value of something goes up: the people who were previously giving it away for free start charging for it, and the people who weren't previously selling it at all start selling it. the APIs that used to be free and now aren't were just slightly ahead of the game, all these new MCP servers aren't going to be free either.
- miki123211 1y ago
  MCP seems to be about giving you access to your own data. Your Slack conversations, your Jira tickets, your calendar appointments. Those wouldn't go into AI training datasets anyway, locked down APIs or not. The APIs of old were about giving you programmatic access to publicly available information. Public tweets, public Reddit posts, that sort of thing. That's the kind of data AI companies want for training, and you aren't getting it through MCP.
mellosouls 1y ago
the AI Agent wave made interoperability hype, and vendor lock-in old-fashioned Perhaps but we see current hypes like Cursor only using MCP one way; you can feed into Cursor (eg. browser tools), but not out (eg. conversation history, context etc). I love Cursor but this "not giving back" mentality originally reflected in it's closed source forking of VS Code leaves an unpleasant taste in the mouth and I believe will ultimately see it lose developer credibility. Lock-in still seems to be locked in.
- talos_ 1y ago
  The VSCode extension Continue provides similar capabilities and gives you full access to your interaction traces (local database and JSON traces)
visarga 1y ago
The main benefit is not that it made interoperability fashionable, or that it make things easy to interconnect. It is the LLM itself, if it knows how to wield tools. It's like you build a backend and the front-end is not your job anymore, AI does it. In my experience Claude and Gemini can take over tool use and all we need to do is tell them the goal. This is huge, we always had to specify the steps to achieve anything on a computer before. Writing a fixed program to deal with dynamic process is hard, while a LLM can adapt on the fly.
- freeone3000 1y ago
  The issue holding us back was never that we had to write a frontend — it was the data locked behind proprietary databases and interfaces. Gated behind API keys and bot checks and captchas and scraper protection. And now we can have an MCP integrator for IFTTT and have back the web we were promised, at least for a while.
  - whitten 1y ago
    what is IFTTT ?
    - lazyasciiart 1y ago
      If this then that - a zapier type glue provider.
      - Mtinie 1y ago
        Minor chronological point but Zapier is an IFTTT-type glue provider. IFTTT was announced Dec. 14, 2010 and launched on Sept. 7. 2011. Zapier was first pitched Sept. 30, 2011 and their public beta launched May 2012.
        crucialfelix 1y ago
        And to answer the obvious next question: yes, there is an MCP for IFTTT https://mcp.pipedream.com/app/ifttt https://mcp.pipedream.com/app/ifttt
Animats 1y ago
> Want spell check? MCP server. > Want it to order coffee when you complete 10 tasks? MCP server. With a trip through an LLM for each trivial request? A paid trip? With high overhead and costs?
- notatoad 1y ago
  the whole point of the article is that it doesn't need to be an LLM, MCP is just a standard way to expose tools to things that use tools. LLMs can use tools, but so can humans.
  - therein 1y ago
    So the whole point of the article is that an API is an API and anything can call an API?
    - lazyasciiart 1y ago
      Maybe phrasing it this way will be the lightbulb moment for everyone who hasn’t got that yet.
    - tveita 1y ago
      There is a long tail of applications that are not currently scriptable or have a public API. The kind that every so often make you think "if only I could automate this instead of clicking through this exact same dialog 25 times" Before, "add a public API to this comic reader/music player/home accounting software/CD archive manager/etc." would be a niche feature to benefit 1% of users. Now more people will expect to hook up their AI assistant of choice, so the feature can be prioritized. The early MCP implementations will be for things that already have an API, which by itself is underwhelming. You would think Apple would have a leg up here with AppleScript already being a sanctioned way to add scriptable actions across the whole of macOS, but as far as I can tell they don't hook it up to Siri or Apple Intelligence in any way.
      - Animats 1y ago
conradev 1y ago
AI agents didn't only make adversarial interoperability hype, they've also made it inevitable! From here all the way until they're probing hardware to port Linux and write drivers.
exe34 1y ago
> made interoperability hype, and vendor lock-in old-fashioned I always imagined software could be written with a core that does the work and the UI would be interchangeable. I like that the current LLM hype is causing it to happen.
stavros 1y ago
I haven't seen an app that didn't have an API create one via MCP. The only MCP servers I've seen were for things that I could already access programmatically.
- bigiain 1y ago
  I am pondering if I should do this. If I have a app who's backend needs to connect to, say, a CRM platform - I wonder if instead of writing APIs to connect to Dynamics or Salesforce or Hubspot specifically, if there's benefit in abstracting a CRM interface with an MCP so that switching CRM providers later (or adding additional CRMs) becomes easier?
  - stavros 1y ago
    One of us doesn't understand MCP well enough, and it might very well be me, but how can MCP be used without an LLM? Most of the structure is in human language.
    - bigiain 1y ago
      I will also freely admit to not understanding MCP much, but using it without an LLM was (at least to my reading) pretty much the main thesis of the linked article. "Okay but. But. What if you just... removed the AI part? What if it's just "a standardized way to connect literally anything to different data sources and tools"?" (which had struck out text 'AI models' in between 'connect' and 'literally')
      - brabel 1y ago
        You’re right. It’s unclear, however, how your application will handle knowing when to call a tool/MCP. That’s the part where LLMs are so good at: understanding that to do a certain job, this or that tool would be useful, and then knowing how to provide the necessary parameters for the tool call (I say tool here because MCP is just a convenient way to pack a normal tool, in other words, it’s a plugin system for tools).
    - 1y ago
alexpotato 1y ago
Reminds me of the days of Winsock. For those that don't remember/don't know, everything network related in Windows used to use their own, proprietary setup. Then one day, a bunch of vendors got together and decided to have a shared standard to the benefit of basically everyone. https://en.wikipedia.org/wiki/Winsock https://en.wikipedia.org/wiki/Winsock
- ggambetta 1y ago
  Trumpet Winsock! Brings back memories :)
  - deleted 1y ago
    [deleted]
  - pyman 1y ago
    I think we're seeing a wave of hype marketing on YouTube, Twitter and LinkedIn, where people with big followings create posts or videos full with buzzwords (MCP, vibe coding, AI, models, agentic) with the sole purpose of promoting a product like Cursor, Claude Code or Gemini Code, or get people to use Anthropic's MCP instead of Google's A2A. It feels like 2 or 3 companies have paid people to flood the internet with content that looks educational but is really just a sales pitch riding the hype wave. Honestly, I just saw a project manager on LinkedIn telling his followers how MCP, LLMs and Claude Code changed his life. The comments were full of people asking how they can learn Claude Code, like it's the next Python. Feels less like genuine users and more like a coordinated push to build hype and sell subscriptions.
    - zarathustreal 1y ago
      They’re not being paid, at least not directly. They don’t need to be. “Educational” “content” is a play to increase the personal profile as a “thought leader.” This turns into invitations to conferences and ultimately funnels into sales of courses and other financial opportunities
      - 1y ago
qudat 1y ago
I joked with people in IRC that it took LLMs to bring answer engines into the terminal
zackify 1y ago
It is new and exciting if you just learned to vibe code, and you don’t even know what a rest api is
bjornsing 1y ago
Exactly. It’s a crack in the MBA’s anti-commoditization wall. Right now it’s like USB-C. If we’re lucky it will turn into TCP/IP and transform the whole economy.
tempodox 1y ago
The pressure to monetize after all those humungous investments into AI will surely move some things that have been stuck in their ways and stagnant. It looks like this time the IT industry itself will be among those that are being disrupted.
MomsAVoxell 1y ago
All vendor lock in is being transmuted to model access.
ljm 1y ago
I genuinely believe that low-code workflow orchestrators like Zapier or IFTTT will be the first major victims of agentic LLM workflows. Maybe not right now but already it’s easier to write a prompt describing a workflow than it is to join a bunch of actions and triggers on a graph. The whole hype around AI replacing entire job functions does not have as much traction as the concept of using agents to handle all of the administrative stuff that connects a workflow together. Any open source model that supports MCP can do it, so there’s no vendor lock in, no need to learn the setup for different workflow tools, and a lot of money saved on seats for expensive SaaS tools.

by phh 1y ago

iLoveOncall 1y ago

> I don't know how long it'll last I'm just baffled no software vendor has already come up with a subscription to access the API via MCP. I mean obviously paid API access is nothing new, but "paid MCP access for our entreprise users" is surely on the pipeline everywhere, after which the openness will die down.

Bjartr 1y ago
And I expect there'll eventually be a way for an AI to pay for an MCP use microtransaction style. Heck, if AIs are at some point given enough autonomy to simply be given a task and a budget, there'll be efforts to try to trick AIs into thinking paying is the best way to get their work done! Ads (and scams) for AIs to fall for!
- iLoveOncall 1y ago
  > Heck, if AIs are at some point given enough autonomy to simply be given a task and a budget, there'll be efforts to try to trick AIs into thinking paying is the best way to get their work done! We're already there, just take a look at the people spending $500 a day on Claude Code.
adamesque 1y ago
I think for enterprise it’s going to become part of the subscription you’re already paying for, not a new line item. And then prices will simply rise. Optionality will kill adoption, and these things are absolutely things you HAVE to be able to play with to discover the value (because it’s a new and very weird kind of tool that doesn’t work like existing tools)
pininja 1y ago
Mapbox is just a small step away from that with their MCP server wrapping their pay-by-use API. I wouldn’t be surprised to see a subscription offering with usage limits if that somehow appealed to them. MapTiler already offers their service as a subscription so they’re even closer if they hosted a server like this on their own. https://github.com/mapbox/mcp-server https://github.com/mapbox/mcp-server

sshine 1y ago

Hype, certainly. But the way I see it, AI agents created incentives for interoperability. Who needs an API when everyone is job secure via being a slow desktop user? Well, your new personal assistant who charges by the Watt hour NEEDS it. Like when the CEO will personally drive to get pizzas for that hackathon because that’s practically free labor, so does everyone want everything connected. For those of us who rode the API wave before integrating became hand-wavey, it sure feels like the world caught up. I hope it will last, but I don’t know either.

mh- 1y ago
Unfortunately, I think we're equally likely to see shortsighted lock-in attempts like this [0] one from Slack. I tried to find a rebuttal to this article from Slack, but couldn't. I'm on a flight with slow wifi though. If someone from Slack wants to chime in that'd be swell, too. I've made the argument to CFOs multiple times over the years why we should continue to pay for Slack instead of just using Teams, but y'all are really making that harder and harder. [0]: https://www.reuters.com/business/salesforce-blocks-ai-rivals-using-slack-data-information-reports-2025-06-11/ https://www.reuters.com/business/salesforce-blocks-ai-rivals...
- ebiester 1y ago
  It's going to take more people willing to move away from slack for those purposes. As it is, I'm going to propose that we move more key conversations outside of slack so that we can take advantage of feeding it into ai. It's a small jump from that to looking for alternatives.
  - sshine 1y ago
    The argument used to be “Let’s move FOSS conversation out of {Slack, Discord} because they prevent conversations from being globally searchable, and they force individuals into subscription to access history backlog.” Getting indexed by AI crawlers appears to be the new equivalent to getting indexed by search engines.
- dgacmu 1y ago

bitwize 1y ago

Remember Web 2.0? Remember the semantic web? Remember folksonomies? Mash-ups? The end of information silos? The democratizing power of HTTP APIs?Anyone? Anyone?

karaterobot 1y ago
I don't understand your point. Some of those things were buzzwords, some were impossible dreams, some changed the way the web works completely. Are you just saying that the future is unknown?
- klabb3 1y ago
  No. What they are saying is best said with a quote from Battlestar Galactica: > All of this has happened before, and all of this will happen again. ”It” here being the boom and inevitable bust of interop and open API access between products, vendors and so on. As a millenial, my flame of hope was lit during the API explosion of Web 2.0. If you’re older, your dreams were probably crushed already by something earlier. If you’re younger, and you’re genuinely excited about MCP for the potential explosion in interop, hit me up for a bulk discount on napkins.
  - bwfan123 1y ago
    And then, there are "architecture astronaut"s dreaming of an entire internet of MCP speaking devices - an "internet of agents" if you will. That is now requiring a separate DNS, SMTP, BGP etc. for that internet.
  - fragmede 1y ago
    I'm older and would like a discount please. The "this time it's different" energy is because assuming a human can interact with the system, and that vision models can drive a gui, who cares if there's an actual API, just have the AI interact with the system as if it was coming in as a human.
  - danielrico 1y ago
    I think battlestar Galactica must be quoting one of the Eddas. I've only read if it from Borges in Spanish, but Conner the same meaning: "Estas cosas han pasado. Estas cosas también pasarán."

adregan 1y ago

How ironic given the amount of APIs that were locking down access in response to AI training! Though the general API lockdown was started long before that, and like you, I’m skeptical that this new wave of open access will last if the promise doesn’t live up to the hype.

TimTheTinker 1y ago
MCP is supposed to grant "agency" (whatever that means), not merely expose curated data and functionality. In practice, the distinction is little more than the difference between different HTTP verbs, but I think there is a real difference in what people are intending to enable when creating an MCP server vs. standard APIs.
- adregan 1y ago
  Might be another reflection of McLuhan‘s “the medium is the message” in that APIs are built with the intended interface in mind. To this point, GUIs; going forward, AI agents. While the intention rhymes, the meaning of these systems diverge.
notatoad 1y ago
i don't think it's ironic at all. the AI boom exposed the value of data. there's two inevitable consequences when the value of something goes up: the people who were previously giving it away for free start charging for it, and the people who weren't previously selling it at all start selling it. the APIs that used to be free and now aren't were just slightly ahead of the game, all these new MCP servers aren't going to be free either.
miki123211 1y ago
MCP seems to be about giving you access to your own data. Your Slack conversations, your Jira tickets, your calendar appointments. Those wouldn't go into AI training datasets anyway, locked down APIs or not. The APIs of old were about giving you programmatic access to publicly available information. Public tweets, public Reddit posts, that sort of thing. That's the kind of data AI companies want for training, and you aren't getting it through MCP.

mellosouls 1y ago

the AI Agent wave made interoperability hype, and vendor lock-in old-fashioned Perhaps but we see current hypes like Cursor only using MCP one way; you can feed into Cursor (eg. browser tools), but not out (eg. conversation history, context etc). I love Cursor but this "not giving back" mentality originally reflected in it's closed source forking of VS Code leaves an unpleasant taste in the mouth and I believe will ultimately see it lose developer credibility. Lock-in still seems to be locked in.

talos_ 1y ago
The VSCode extension Continue provides similar capabilities and gives you full access to your interaction traces (local database and JSON traces)

visarga 1y ago

The main benefit is not that it made interoperability fashionable, or that it make things easy to interconnect. It is the LLM itself, if it knows how to wield tools. It's like you build a backend and the front-end is not your job anymore, AI does it. In my experience Claude and Gemini can take over tool use and all we need to do is tell them the goal. This is huge, we always had to specify the steps to achieve anything on a computer before. Writing a fixed program to deal with dynamic process is hard, while a LLM can adapt on the fly.

freeone3000 1y ago
The issue holding us back was never that we had to write a frontend — it was the data locked behind proprietary databases and interfaces. Gated behind API keys and bot checks and captchas and scraper protection. And now we can have an MCP integrator for IFTTT and have back the web we were promised, at least for a while.
- whitten 1y ago
  what is IFTTT ?
  - lazyasciiart 1y ago
    If this then that - a zapier type glue provider.
    - Mtinie 1y ago
      Minor chronological point but Zapier is an IFTTT-type glue provider. IFTTT was announced Dec. 14, 2010 and launched on Sept. 7. 2011. Zapier was first pitched Sept. 30, 2011 and their public beta launched May 2012.
      - crucialfelix 1y ago
        And to answer the obvious next question: yes, there is an MCP for IFTTT https://mcp.pipedream.com/app/ifttt https://mcp.pipedream.com/app/ifttt

Animats 1y ago

> Want spell check? MCP server. > Want it to order coffee when you complete 10 tasks? MCP server. With a trip through an LLM for each trivial request? A paid trip? With high overhead and costs?

notatoad 1y ago
the whole point of the article is that it doesn't need to be an LLM, MCP is just a standard way to expose tools to things that use tools. LLMs can use tools, but so can humans.
- therein 1y ago
  So the whole point of the article is that an API is an API and anything can call an API?
  - lazyasciiart 1y ago
    Maybe phrasing it this way will be the lightbulb moment for everyone who hasn’t got that yet.
  - tveita 1y ago
    There is a long tail of applications that are not currently scriptable or have a public API. The kind that every so often make you think "if only I could automate this instead of clicking through this exact same dialog 25 times" Before, "add a public API to this comic reader/music player/home accounting software/CD archive manager/etc." would be a niche feature to benefit 1% of users. Now more people will expect to hook up their AI assistant of choice, so the feature can be prioritized. The early MCP implementations will be for things that already have an API, which by itself is underwhelming. You would think Apple would have a leg up here with AppleScript already being a sanctioned way to add scriptable actions across the whole of macOS, but as far as I can tell they don't hook it up to Siri or Apple Intelligence in any way.
    - Animats 1y ago

conradev 1y ago

AI agents didn't only make adversarial interoperability hype, they've also made it inevitable! From here all the way until they're probing hardware to port Linux and write drivers.

exe34 1y ago

> made interoperability hype, and vendor lock-in old-fashioned I always imagined software could be written with a core that does the work and the UI would be interchangeable. I like that the current LLM hype is causing it to happen.

stavros 1y ago

I haven't seen an app that didn't have an API create one via MCP. The only MCP servers I've seen were for things that I could already access programmatically.

bigiain 1y ago
I am pondering if I should do this. If I have a app who's backend needs to connect to, say, a CRM platform - I wonder if instead of writing APIs to connect to Dynamics or Salesforce or Hubspot specifically, if there's benefit in abstracting a CRM interface with an MCP so that switching CRM providers later (or adding additional CRMs) becomes easier?
- stavros 1y ago
  One of us doesn't understand MCP well enough, and it might very well be me, but how can MCP be used without an LLM? Most of the structure is in human language.
  - bigiain 1y ago
    I will also freely admit to not understanding MCP much, but using it without an LLM was (at least to my reading) pretty much the main thesis of the linked article. "Okay but. But. What if you just... removed the AI part? What if it's just "a standardized way to connect literally anything to different data sources and tools"?" (which had struck out text 'AI models' in between 'connect' and 'literally')
    - brabel 1y ago
      You’re right. It’s unclear, however, how your application will handle knowing when to call a tool/MCP. That’s the part where LLMs are so good at: understanding that to do a certain job, this or that tool would be useful, and then knowing how to provide the necessary parameters for the tool call (I say tool here because MCP is just a convenient way to pack a normal tool, in other words, it’s a plugin system for tools).
  - 1y ago

alexpotato 1y ago

Reminds me of the days of Winsock. For those that don't remember/don't know, everything network related in Windows used to use their own, proprietary setup. Then one day, a bunch of vendors got together and decided to have a shared standard to the benefit of basically everyone. https://en.wikipedia.org/wiki/Winsock https://en.wikipedia.org/wiki/Winsock

ggambetta 1y ago
Trumpet Winsock! Brings back memories :)
- deleted 1y ago
  [deleted]
- pyman 1y ago
  I think we're seeing a wave of hype marketing on YouTube, Twitter and LinkedIn, where people with big followings create posts or videos full with buzzwords (MCP, vibe coding, AI, models, agentic) with the sole purpose of promoting a product like Cursor, Claude Code or Gemini Code, or get people to use Anthropic's MCP instead of Google's A2A. It feels like 2 or 3 companies have paid people to flood the internet with content that looks educational but is really just a sales pitch riding the hype wave. Honestly, I just saw a project manager on LinkedIn telling his followers how MCP, LLMs and Claude Code changed his life. The comments were full of people asking how they can learn Claude Code, like it's the next Python. Feels less like genuine users and more like a coordinated push to build hype and sell subscriptions.
  - zarathustreal 1y ago
    They’re not being paid, at least not directly. They don’t need to be. “Educational” “content” is a play to increase the personal profile as a “thought leader.” This turns into invitations to conferences and ultimately funnels into sales of courses and other financial opportunities
    - 1y ago

qudat 1y ago

I joked with people in IRC that it took LLMs to bring answer engines into the terminal

zackify 1y ago

It is new and exciting if you just learned to vibe code, and you don’t even know what a rest api is

bjornsing 1y ago

Exactly. It’s a crack in the MBA’s anti-commoditization wall. Right now it’s like USB-C. If we’re lucky it will turn into TCP/IP and transform the whole economy.

tempodox 1y ago

The pressure to monetize after all those humungous investments into AI will surely move some things that have been stuck in their ways and stagnant. It looks like this time the IT industry itself will be among those that are being disrupted.

MomsAVoxell 1y ago

All vendor lock in is being transmuted to model access.

ljm 1y ago

I genuinely believe that low-code workflow orchestrators like Zapier or IFTTT will be the first major victims of agentic LLM workflows. Maybe not right now but already it’s easier to write a prompt describing a workflow than it is to join a bunch of actions and triggers on a graph. The whole hype around AI replacing entire job functions does not have as much traction as the concept of using agents to handle all of the administrative stuff that connects a workflow together. Any open source model that supports MCP can do it, so there’s no vendor lock in, no need to learn the setup for different workflow tools, and a lot of money saved on seats for expensive SaaS tools.