careful there cowboy, we are in the golden age of ai, regulation is still catching up.
You don't want to sell guns to people without some sort of background check. The amount of exploits found in the last few months have been pretty scary already.
This is just one more layer of caution, because it reveals how little we know how these llms work. They know how to make them, but they seem to be unable to properly restrain them.
Yes, I think that too. Besides sports, most young people studying today are aiming for jobs that are mainly indoors. It's not a requirement, of course, but because a lot of modern careers consist of working in offices or other enclosed environments.
No movement, No sun, Stale Air (Unless you have good ventilation). Pretty harmful if we think about it.
The best Chinese RAM on the market is 50% larger and requires more power and thus emits more heat, as it is a 16nm feature size. If they can get to competitive sizes, then of course data centers will purchase it.
I see comments like this and they seem so pointless.
The port was done in a week. Do you think the development is finished?
Obviously there are some unsafe blocks that will remain forever unsafe. But other will eventually be removed.
> Delegate, do not pair-program. Cat Wu (Claude Code team): “The model performs best if you treat it like an engineer you’re delegating to, not a pair programmer you’re guiding line by line.” Write a crisp brief upfront, then let it run.
This is also how you get a slop codebase that you won’t easily understand.
It becomes a labyrinth that only the Agent knows.
It’s not a catastrophe when your making prototypes or projects like you see on X.
But if you are expanding your codebase or trying to build something more professional and maintainable. I find it important to explicitly spec things bit by bit so I can understand and some what keep my writing style in this codebase.
But this is only productive when you have a fast model otherwise it kills your chain of thought while you wait for the output.
If the model is slow, delegation is probably the only way.
I trust them because of their reputation.
I have been a bun user before v1.0.0 and I experienced some shortcomings, bugs, memory leaks and things of that nature. But all of them were eventually patched, and it has become my go to runtime for at least 2 years now.
I trust their judgement to do the right thing.
I don’t understand the overreaction since this is a parallel development.
If it turns out to be better than make it default. Bugs get fixed it’s not like their zig version didn’t have issues before.
Anthropic has a serious savior complex (when it is actually about total control) and believe that you should not run your own models locally and they do not care about you and I.
This Bun Zig to Rust rewrite is great content for them and for their IPO prospectus, but it isn't performative in the sense that it is fake. (It is real with terrible code.)
What this really means is that it gives the green light to managers and everyone else to use Claude to do massive rewrites; even when it produces hundreds of thousands of lines of slop.
Unless comprehension debt is what you want.
You do not have the same amount of token-spend as the Bun team does.
> I trust their judgement to do the right thing.
They will do the "right thing" for their investors (and soon Wall Street).
I have had experiences where customers use AI to communicate and express their issues. Sometimes they produce walls of text like the website exemplifies, but overall it's a better alternative to not be able to explain the issue because you don't know the specific terminology and you are just a layman trying to do things.
Show some love for the layman, we are all laymen in areas we don't know about.
reply