This matches some previous comments around LLMs driving adoption of programming languages or frameworks. If you ask Claude to write a web app, why not have it use your own framework, that it was trained on, by default?

Users are far more likely to ask it about shadcn, or material, than about node/deno/bun. So, what is this about?

Currently Claude etc. can interact with services (including AWS) via MCPs.

What the user you're replying to is saying the Bun acquisition looks silly as a dev tool for Node. However if you look at their binding work for services like s3[0], the LLM will be able to interact directly with cloud services directly (lower latency, tighter integration, simplified deployment).

0: https://bun.com/docs/runtime/s3

That doesn't make sense either. Agents already have access to MCPs and Tools. Your example is solved by having an S3 wrapper as a set of tools.

I bet you didn't click that link. A wrapper and an API that is built-in to the runtime and optimized for those use cases are different things.

Being able to remove a layer of abstraction to get the thing done is usually good right?

An AI company scoops up frontend tech. Do you really think it was because of s3?

JavaScript ≠ frontend

bun ≠ front end development tool

hasn't been like that for many years

Bun is not really frontend tech