Register and share your invite link to earn from video plays and referrals.

Search results for 248
248 community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including 248
the spike in july: new fuzzer overrides syscalls and diffs bun’s behavior against node on identical inputs. a /loop in claude code drives it and sends bugs to robobun to fix
i think _some_ visual indicator that it's stderr and not stdout is a good idea. it's always been weird to me that the terminal doesn't say you're looking at an error. but i've been kind of annoyed by the red styling in bun for awhile now
Show more
the red console.error ansi styling in bun - should we get rid of it?
hopefully the blog post was good enough to justify the wait we’re merging some more node.js compatibility improvements and then will release bun v1.4
rust rewrite blog post Monday Bun v1.4 hopefully Tuesday (video still editing)
0
48
1.2K
16
Forward to community
In the next version of Bun Web Streams get faster, use less memory, and pass 100% of relevant Web Platform Tests
Anthropic wants the public to see one thing: the careful lab, the safety lab, the grown-up in the room trying to keep frontier AI from running off a cliff. However, the pattern around Anthropic does not look like caution by itself. It looks like a company wrapping a business model in moral language, then using that language to justify opaque model behavior, anti-competitive access rules, regulatory pressure, and a future where builders, startups, researchers, and Opensource communities stay downstream of a few blessed frontier labs. Imagine a compiler that emits worse binaries when it thinks you are building a competing compiler. Imagine a microscope that blurs certain samples because the manufacturer dislikes the research direction. Imagine a debugger that lies only when your codebase resembles a future rival. Anthropic can learn from the internet, copyrighted books, code, public knowledge, user feedback if permitted, synthetic data, and its own models. But if a developer uses Claude to bootstrap a competitive open assistant, Anthropic calls foul. The company argues that safety controls may be lost and that competing models undermine the investment required to build frontier systems. The fight is whether intelligence becomes something people can own, inspect, modify, run locally, fine-tune, study, route, and improve, or whether it becomes a subscription permission layer run by companies that can refuse, degrade, surveil, retain, revoke, reroute, or lobby away your access. Anthropic's moat is being a permission regime. On daily basis, competitors and acquisition targets discover that access can disappear. The company asks governments to bless safety frameworks, deployment gates, incident reporting, evaluation regimes, and even future pauses that incumbents are best positioned to survive. If a coding or research model secretly changes the quality, direction, or reliability of an answer because it classified the user as doing disallowed frontier work, the tool is no longer merely "safe." It is untrustworthy. If Anthropic wants to be treated like a public-interest safety institution, it cannot behave like a hypersensitive platform monopolist whenever a customer gets too close to building alternatives. Yes, companies protect their IP. But Anthropic is not selling a normal SaaS widget. It is selling cognition as infrastructure. Once cognition becomes infrastructure, anti-competitive access control stops being a normal vendor dispute and becomes a social bottleneck. Anthropic repeatedly converts safety, security, and responsible deployment into mechanisms of control over who may build and what could be built. We cannot trust them.
Show more