4 ms·

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

by ojame 10mo ago

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 https://bun.com/docs/runtime/s3

mrcsharp 10mo ago
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.
- deleted 10mo ago
  [deleted]
- solumunus 10mo ago
  Being able to remove a layer of abstraction to get the thing done is usually good right?
- rs186 10mo ago
  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.
fishmicrowaver 10mo ago
An AI company scoops up frontend tech. Do you really think it was because of s3?
- gedy 10mo ago
  Bun is not really frontend tech
- rs186 10mo ago
  JavaScript ≠ frontend bun ≠ front end development tool hasn't been like that for many years