20 days after Claude's code leak: Did the accidental open-source actually change anything for developers?
Claude 程式碼洩露滿 20 天:這場意外的「開源」對本地開發者真的有幫助嗎?
It's been about three weeks since Claude's source code got leaked, and honestly? The hype might be bigger than the actual impact. Sure, we got a peek at Anthropic's internal tricks, saw how much of it is held together with duct tape and vibes, and watched a bunch of forks pop up. But here's the real question: did any of it actually matter? Most of those forks seem half-baked at best. The interesting stuff—like their parallel tool-calling and diffing techniques—doesn't seem to have made it into any of the existing popular frameworks yet. So did this leak actually move the needle for local development, or was it just a fun peek behind the curtain?
OpenAI is hosting a livestream event. Details about the specific announcements, product launches, or demonstrations will be revealed during the broadcast.
The last time OpenAI did an unannounced livestream, they dropped GPT-4 Turbo and changed pricing overnight
OpinionsRead
ChatGPT Images 2.0
OpenAI is launching ChatGPT Images 2.0 with major upgrades to image generation capabilities. Watch the livestream announcement at https://openai.com/live/
OpenAI is positioning this as a direct competitor to established image generation tools, suggesting they're confident enough to challenge the current market leaders
OpinionsRead
The "just wait 6 months" argument from 2025 survived exactly one iteration
Throughout 2025 the standard response to any complaint about an LLM was some version of "just wait 3-6 months, the next generation will handle this effortlessly." The argument was everywhere. Every limitation was temporary, every missing capability was a few iterations away, every autonomous agent demo was a preview of imminent reality.
It's April 2026 now and worth checking how that held up.
On r/ClaudeAI this week there's a long thread about Opus 4.7 where multiple users argue it's a regress
OpinionsRead
Mistral Medium 3.5 on AMD Strix Halo: Painfully Slow (Plan for Overnight Runs)
Someone actually tested Mistral Medium 3.5 on AMD's new Strix Halo chip, and the results are... not great. For a 48k-token prompt with 4k thinking tokens, it took about 2 hours just to get an answer about code architecture. Yeah, you read that right—two hours. The takeaway: if you want to run this locally on Strix Halo, queue it up before bed. The technical setup involved heavy optimization (Q5_K_XL quantization, GPU acceleration with -ngl 999, cache reuse), but even with all that tuning, it's still a crawl. Not exactly the "instant local AI" dream, but hey, at least it works.