Comment by usef-
1 day ago
I suspect this thread won't go anywhere.
Something that's experimental can receive further changes and then no longer be considered experimental.
1 day ago
I suspect this thread won't go anywhere.
Something that's experimental can receive further changes and then no longer be considered experimental.
There could be some genuine discussion if you stop bending over backwards justifying YOLO prompting with strained logic.
Feel free to point out where my logic is wrong. It sounds like you think they've made a stable release already? None of the new code is sent to users yet. It's a direct translation without relying on major AI decisions. I'm happy to call them cowboys if they make a release with lousy testing.
> Feel free to point out where my logic is wrong.
I already have, as have others, but
> It sounds like you think they've made a stable release already?
What's the point if you keep refusing to acknowledge the issue and tossing out theories about how I and others might be wrong, just to see what sticks?
> None of the new code is sent to users yet.
So? The decision to adopt was already made and the code was merged without planning, without considering downstream impacts, and without proper inspection. People who won't read their own code before merging won't read it after. But many of you don't even see this as an issue. So again, what's the point in trying to point all of this out?
Also you yourself said the experiment is over. You can't have it both ways.
> It's a direct translation without relying on major AI decisions.
Because the genie said so? That sounds lacking in scientific rigor, but
> I'm happy to call them cowboys if they make a release with lousy testing.
Oh right, that the test passes is proof that the new code is debuggable, maintainable, architecturally sound, semantically equivalent to the old code, and non-disruptive for downstream users. Apparently testing has leapt centuries ahead in the past two weeks or so.
1 reply →