Comment by solenoid0937
2 days ago
It's just more reactionary "AI bad." The tech world is rapidly splitting into people that "get" AI and people that bizarrely still resist it because they are stuck with a 2024 understanding of what AI can do (and never bothered to update their priors in earnest.)
Anyone who isn’t supporting using runtime rewritten by an LLM is obviously “doesn’t get it” and a luddite.
But in this case, the yt-dlp maintainers didn't actually evaluate the rewrite yet, they just declared they wouldn't support it, sight unseen.
Not really an argument on its merits.
OSS is not a testing ground for rewrites made by hyperscalers. Bun is free to fork yt-dlp and prove it is stable enough.
Why is it their job to evaluate a 1m+ line code rewrite?
That’s the fun part no one has evaluated the rewrite yet! Not even the bun team!
Claude says it’s all good though so what could go wrong
[flagged]
What about people who view AI as a useful tool, and use it daily while still recognizing it’s limitations?
I’m no AI hater, but there’s a limit to how much trust I give it and the Bun rewrite is well beyond that limit.
It's a bit of a contradiction. We understand that AI can be used usefully, and to great effect. But if someone else uses it, it's a potential liability.
I think the issue is, we understand our own usage of it, and respect the boundaries of what's possible and what needs to be done to use these tools properly.
But we don't know how the other guy is using it.
We don't know if they're being responsible, and using it in a safe manner.
If they are: great. But if they aren't, we're opening ourselves up to all kinds of security shenanigans.
It's one of those things where we're only going to be okay with it, if we're the ones using it. But that also means other people will be suspect of our code.
It's really a no win scenario, except for inside each of own little bubbles.
AI or not, I trust a development team with a rigorous code review process, and I distrust a team that merges one-shot seven-figure PRs.
Bun has very loudly defected from the former category to the latter.
In this case though we do know how it was used? We’re talking about a specific case here.
It was used to write 1 million lines of code in a week.
Yes it was translating an existing codebase, but still there’s no way that is a safe transition.
Would you ship that at your job? I definitely would not
1 reply →