classicposter

Yes, they probably don't know C ABI.

I recall an instance where he mocked the project as "Microslop" on his blog and then quietly edited the post later.

Sorry, this is wrong. Not relating Bun project.

https://web.archive.org/web/20260204011603/https://ziglang.o...

Microslop Windows provides a large ABI surface area for doing things in the kernel. However, not all ABIs are created equally. As Casey Muratori points out in his lecture, The Only Unbreakable Law, the organizational structure of software development teams has a direct impact on the structure of the software they produce.

I recall an instance where he mocked the project as "Microslop" on his blog and then quietly edited the post later. That aside, the earlier rewrite from TypeScript to Go involved efforts to minimize regressions as much as possible—such as announcements to users and the community, and a phased, one-on-one migration. This project, however, is a different story. It becomes from a buggy product to an entire slop product.

This slop rewrite introduced new vulnerabilities and regressions.

He must be suffering from AI psychosis.

https://github.com/oven-sh/bun/issues/30921

A CVE wasn’t announced for an HTTP Request Smuggling vulnerability

Even before the acquisition of Anthropic, there had never been a single vulnerability report.

https://github.com/oven-sh/bun/security

Do not use this in production.

Exactly.

https://github.com/yt-dlp/yt-dlp/issues/16766

No, Node.js is faster in real workload.

https://blog.platformatic.dev/bun-is-fast-until-latency-matt...

https://github.com/oven-sh/bun/security

Surprisingly, they appear to have not disclosed any vulnerabilities whatsoever. It's likely there have been numerous vulnerabilities in the past, but they are all being ignored.

https://x.com/DavidSherret/status/2031432509301428644

It's interesting that the developer who spearheaded the hype of Zig abandoned the engineering without addressing the segfault. They could have also taken the approach of gradually porting from Zig to Rust via FFI. Yes, this is a slop show by the AI lab.

Porting TypeScript to Go and coreutils to Rust is understandable given their legitimate background. However, this is just a slop. The original code and tests are of poor quality, so the only thing that can be fixed is segmentation faults...

A former engineer at Bun said that "there was too much vibe coding, but my opinion wasn't taken into consideration."

https://paperclover.net/q+a/2506010139

- too much ai chatter. so many examples of it failing to work. ill prove it by showing the most recent ai-generated pull request. yep, it’s failing. i will admit that my feedback on the above items were not very loud, but there has been no attempts to correct this vision.

https://x.com/bunjavascript/status/1966806250827714736

Haha, is it really okay not to retract that that the official account previously posted a caricature criticizing Rust?

https://github.com/oven-sh/bun/issues/30197

It seems there was an issue where the image API ignored the ICC Profile.(now fixed) Any developer with experience implementing image formats would almost certainly avoid this mistake. This is a problem that cannot be solved with vibe coding. In this situation, the user is merely a guinea pig for bug fixes.

Congratulations! I recall there used to be difficulties handling non-ASCII characters in the built-in terminal, but now I can use it without any problems regarding Japanese input. Providing a stable, real-time, stateful application like an editor is incredibly difficult.I appreciate the efforts of the team and contributors.

https://blog.platformatic.dev/bun-is-fast-until-latency-matt...

The latency seems to be very poor about complex applications like Next.js.