Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
classicposter
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
classicposter
27d ago
https://bsky.app/profile/jacob.gold/post/3msvjwys7lc2t Hey, did the memory leak really solve with slop rewrite?
2.
▲
by
classicposter
28d ago
https://x.com/yagiznizipli/status/2082905235459117202 They were pleased to be faster than Go in the "Hello World" benchmark, but unfortunately, they lag behind Node.js and Deno in complex real-world work
3.
▲
by
classicposter
2mo ago
Yes, they probably don't know C ABI.
4.
▲
by
classicposter
2mo ago
> 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/202602040116
5.
▲
by
classicposter
2mo ago
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
6.
▲
by
classicposter
2mo ago
This slop rewrite introduced new vulnerabilities and regressions.
7.
▲
by
classicposter
4mo ago
He must be suffering from AI psychosis.
8.
▲
by
classicposter
4mo ago
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
9.
▲
by
classicposter
4mo ago
Exactly. https://github.com/yt-dlp/yt-dlp/issues/16766
10.
▲
by
classicposter
4mo ago
No, Node.js is faster in real workload. https://blog.platformatic.dev/bun-is-fast-until-latency-matt...
11.
▲
by
classicposter
4mo ago
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
12.
▲
by
classicposter
4mo ago
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 s
13.
▲
by
classicposter
4mo ago
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...
14.
▲
by
classicposter
5mo ago
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
15.
▲
by
classicposter
5mo ago
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?
16.
▲
by
classicposter
5mo ago
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
17.
▲
by
classicposter
5mo ago
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
18.
▲
by
classicposter
6mo ago
https://blog.platformatic.dev/bun-is-fast-until-latency-matt... The latency seems to be very poor about complex applications like Next.js.