Hacker News Reader

I think it's due to they are doing a funny business to parse the progress, that's pretty much vibed and no one care. Like instead of using curl's progress, they re-invented a progress tracking with the tracing interface (--trace-ascii), byte by byte :(

https://github.com/anomalyco/opencode/issues/22998 https://github.com/anomalyco/opencode/issues/53702

View on HN

Okay nevermind this is pretty bad. Although humans do this too and I've also done this without realizing it, only noticed when I was trying to move a file bigger than few kilobytes.

I’m kind of surprised at the overlap in “has progress bar” and “is expected to take a few seconds max”.

I’ve never even debated it for files under hundreds of megs. It’ll show up soon, if I care I’ll do an ls in a loop to look at file sizes. Just log where the file is.

It's one of those paradoxes inherent to software development: even if a tool is designed to work with Big Data, developers are too impatient / feel too unproductive to actually work with Big Data during development, so they only bother testing their tool using small data for 99.9% of development. Problems the tool has under actual Big Data tend to only start being found as of v1.0-rc1.

it's also an inherit bash problem where what you write is what you get, there's no buffer to keep you from slowing something down to a crawl.

Reply on news.ycombinator.com