Live data from Hacker News

Bun.Image

bun.com

11–16 of 16 posts

Re: Bun.Image

#11

Earlier quoted context omitted.

The other big problem with LLM documentation is that it tends to drift from the code, because agents forget to update it. Then later agents sometimes reference the documentation, sometimes reference the code, and get confused. For agent written code I now default to no documentation and explanatory function signatures, it works better for me at least.

Humans also tend to forget to update documentation and the same confusion happens. I don't think it's really a new problem.

I agree, I think for agents though, documentation does more harm than good. When I'm writing code with an agent I tell it to skip documentation entirely (reading or writing it) and it leads to more accurate outcomes.

When agents write most of our code, I question if we will still even need documentation.

Re: Bun.Image

#13

This looks like one of the better pieces of LLM-output documentation I've seen. It's bad technical writing, but better than most of what I've seen come out of an LLM. --------------- Pre-empting the "how can you tell", here's some of the tells. > The API is shaped after Sharp: Constantly using "shaped" and "shape" is becoming an LLM-ism, much more common than in human writing. > The constructor accepts a path, bytes,…

The other big problem with LLM documentation is that it tends to drift from the code, because agents forget to update it. Then later agents sometimes reference the documentation, sometimes reference the code, and get confused. For agent written code I now default to no documentation and explanatory function signatures, it works better for me at least.

I just have a rule in AGENTS.md that any additions, removals or modifications to the public facing APIs should update the corresponding API documentation, works fine for me (assuming both sit in the single workspace).

Re: Bun.Image

#14
post #6

I really like this. Having image manipulation as a core standard library feature rather than an optional package makes complete sense to me for a web development platform in 2026. It's not like image manipulation is a poorly understood problem or a fast-moving field.

> It's not like image manipulation is a poorly understood problem

You would think, but the initial implementation of this stripped ICC profiles (https://github.com/oven-sh/bun/issues/30197), and while that was fixed in time for the release, it still currently doesn't understand EXIF rotation metadata (https://github.com/oven-sh/bun/issues/30235) or high-bit-depth images (https://github.com/oven-sh/bun/issues/30462)

Re: Bun.Image

#15

Earlier quoted context omitted.

Humans also tend to forget to update documentation and the same confusion happens. I don't think it's really a new problem.

I agree, I think for agents though, documentation does more harm than good. When I'm writing code with an agent I tell it to skip documentation entirely (reading or writing it) and it leads to more accurate outcomes. When agents write most of our code, I question if we will still even need documentation.

I think that's a fair take. I think we definitely still need specs that describe the desired behavior as an artifact. But documentation describing the implementation definitely feels less important.

Re: Bun.Image

#16
post #14
post #6

I really like this. Having image manipulation as a core standard library feature rather than an optional package makes complete sense to me for a web development platform in 2026. It's not like image manipulation is a poorly understood problem or a fast-moving field.

> It's not like image manipulation is a poorly understood problem You would think, but the initial implementation of this stripped ICC profiles ( https://github.com/oven-sh/bun/issues/30197 ), and while that was fixed in time for the release, it still currently doesn't understand EXIF rotation metadata ( https://github.com/oven-sh/bun/issues/30235 ) or high-bit-depth images ( https://github.com/oven-sh/bun/issues/304…

Sure, but there's a finite list of things like that. I'll be surprised if there's anything notable outstanding like that within a month or two.
Post reply on HN