ppnd

=_=

[ppnd @MRGA2k]

这个是真喜欢

[Ryan Stephen @Ryan__Stephen]

playing with realtime diffusion ui

[ppnd @MRGA2k]

@AnthropicAI @realDonaldTrump Is this true?

[ppnd @MRGA2k]

@ClaudeDevs @claudeai welcome back to GPT5.5!

[ppnd @MRGA2k]

@__oQuery 昨天同时跑了几个dynamic workflow，稳定好久的号就被封了。

[ppnd @MRGA2k]

outlook邮箱垃圾邮件算法有病啊，太害人了。

[ppnd @MRGA2k]

此去经年，应是良辰好景虚设。便纵有千种风情，更与何人说？

[ppnd @MRGA2k]

@akazwz_ 责任问题

[ppnd @MRGA2k]

@OpenAI You should have GPT rewrite uv in Zig.

[ppnd @MRGA2k]

@ThePrimeagen Bun: excuse me 🤫

[ppnd @MRGA2k]

@jarredsumner Why not use Claude to rewrite JavaScriptCore in Rust too?

[Elon Musk @elonmusk]

@karankendre Anthropic will not be destroyed. Their AI+harness goes far beyond coding and Opus 4.7 is still better than Composer 2.5, albeit a lot more expensive.

Cursor is however an important piece of the puzzle to make Grok much better.

[ppnd @MRGA2k]

@stefanzweig @marchliu 比不过emacs，emacs有��仰、哲学加成的同时还有最大的自由度

[ppnd @MRGA2k]

@dreamsofcode_io Openclaw be like: “Look at me!”

[Loris Cro ⚡ @croloris]

@ru_tamamo @seg4lt Quite a few people in the Zig community are actually glad Bun is gone. Bun has been a bad example of how to use Zig effectively since the beginning.

If I had a magic button to magically speed up the process that led Bun to go to Rust, I would have pressed it a long time ago.

[ppnd @MRGA2k]

@jarredsumner @secemp9 Bun already had over 3,000 bug issues while it was still using the Zig version. This already shows that Bun has problems with its test coverage.

[Mitchell Hashimoto @mitchellh]

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all.

There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message.

A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this.

On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting!

There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting.

I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first.

I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

[ppnd @MRGA2k]

@victor_cw @tokerumaisurii https://t.co/Pg56VuX8Qe

[ppnd @MRGA2k]

@akazwz_ jarred开始疯狂vibe coding。3000多bug看看rust实力

[ppnd @MRGA2k]

@luoyonghao 龙哥

[ppnd @MRGA2k]

@YoavCodes Bun should learn from Zig and spend more time thinking through better design decisions, rather than having Claude rewrite parts of the project in another language and treating the programming language itself as the solution to engineering and maintenance problems.