501–510 of 646 posts
Earlier quoted context omitted.
You might not like it but you actually live in a world with other people and building technology often affects their lives and they have opinions on it. For AI a lot of that impact has been negative.
I don't have the emotional energy to care, actually. This is actually fascinating. How does my opinion matter? Should I join all the socials (this is my only form of social media) and stand on my soapbox and shout into the void? Do I need to express I care so others know I care and have picked a side and have opionions on evrything? I do not care. My opinion does not matter. I can scream into all the voids. I can vir…
“Learned helplessness” himself graced us with his presence.
Earlier quoted context omitted.
I'm not sure what "exhibiting the behavior you are criticizing" would even mean here. BUT. "Ignore anything but actual problems" is a terrible stance to take generally for software and dependency selection. Incidents are fairly sparse, process is much easier to observe. So if you can find connections between process and incident possibility, that's a very reasonable heuristic. And it's easy to find examples of overag…
You are putting words in my mouth, I never said anything about such a stance. The vast majority of new software is written using AI. The problem is not that it is written by AI, but rather than some people treat it like a black box. It is entirely possible to use AI to write code and verify that it is correct. Even Linus Torvalds is allowing AI generated code into the Linux kernel as long as it's managed properly.
Not even 10 percent is. Good lord. Go outside and touch grass.
Earlier quoted context omitted.
It's not really political. Or let me rephrase possibly yt-dl is being political. VUT the concept of 'not adopting a core dependency until it has been widely used in production for 6 months - a year.', is not a political on general. A full rewrite of 1 million loc is essentially a new runtime that has the same ABI as the previous and for many downstream consumers it's not something they are comfortable taking a produc…
I think your stance is more reasonable than the one in the article, TBH. If yt-dlp said something like "We're going to wait 6 months on the Rust rewrite", that would be reasonable. But instead it says something more like we think that Bun is vibe-coded, so we don't want to use it any more. That seems less reasonable.
That’s as reasonable as it gets. Yt-dlp isn’t a beta testing grounds for hyperscalers.
Why are some people so pressed about this decision? From my point of view, if you're truly a vibe code enthusiast wouldn't you be able to just vibe code your own better yt-dlp (or fork the existing one and do whatever you need to do with it)?
It appears they mixed JS building into their python project, aiming to support multiple package managers which are executed from their python script.
This explains the otherwise non-sensical explanation about bun That's not how JS packaging normally works. I would set up a separate folder for the JS project, and use one package manager to build the project, like anyone else does.
Publish the package to npm, or bundle the tarball with your python program.
I guess the permission model of the JS runtime could be another topic, but at least they would have their build fixed without worrying about Node dependency resolution and package managers in their Python code.
Can anyone explain why bun was used to begin with?
Obviously the JS build should happen outside of Python and use one package manager instead of attempting to support them all.
Earlier quoted context omitted.
Notably, they aren't (yet) dropping support for older, pre-rewrite versions of Bun. They also could be leaving the door open to support Bun in the future, if the rewrite proves successful. I think waiting and seeing is the right, conservative move.
If that was how it was phrased I think there would have been less push back, but that's not at all how it's been communicated. There is no assumption to rereview at a later date at all given the focus on the AI usage etc. If they said we will rereview in 1-6 months or whatever the whole discussion would be mute.
Bun shat on community and yet-dlp owed them free testing? No, sir.
Earlier quoted context omitted.
On the whole, I think vibe coded test suites can be pretty good. But it really depends on how you prompt. I often get the AI to brainstorm needed tests into a text file while it works. Then later I get another agent to write tests based on the list. It does a reasonable job. Its also pretty good at writing regression tests when it fixes a bug. Where LLMs struggle - or at least where claude struggles - is fixing the a…
I find that adversarial multi agent setups eventually fall down because one side or the other always manages to convince the other side to give up given enough time. I’ve tried all sorts of things to keep Claude from cheating, but the only one that works is to restrict access to the tests files, which obviously isn’t a real solution. We recently had an “AI week” at work and I spent $1000 in tokens trying out differen…
Earlier quoted context omitted.
The whole point of having canary builds is that they're unstable. That's why they're called canary. Rockets failing in test flights isn't a bad thing.
> Rockets failing in test flights isn't a bad thing. I hate to be pedantic but for a whole host of environmental reasons, they are suboptimal, and it still incinerates money to lose a rocket during a flight test.
In case you aren't aware, the whole codebase of Bun did not explode into debris just because it hit a bug. They can just fix the bug and recompile.
Earlier quoted context omitted.
Care to share a link? There are 0 posts on Bun blog, or the GitHub page README announcing/explaining the rational for the rewrite, or project direction
https://news.ycombinator.com/item?id=48073680 There's been lots of talk about it here and on his twitter and such.