781–790 of 822 posts
Github is failing to load the 800 comments, naturally. I'll bet they're fun.
Too bad modern computers are not capable of processing 800 paragraphs of text. That’s several hundred kilobytes! Maybe the technology will advance thanks to AI…
* someone else's
Earlier quoted context omitted.
> AI was given the answer, it just repeated it back in a slightly different format. Ridiculous.
How so? The code was already coded, the tests were already coded, the architecture was already in place. Even the help in needed to map some stuff to the new language was already coded. What did AI actually do here?
This will go down in history as the biggest mistake of software engineering of all time. Bun is the runtime of Claude Code, which is the core product of a trillion dollar company, which now sits on a vibe-coded app, where not a single person in the world has a proper mental model of.
If this goes wrong even in the slightest , the ridicule about a drug dealer getting high on their own supply will be neverending and grim.
not enough people are emotionally prepared for if it’s not going wrong even in the slightest
This is more like an ignorant business man's view on technology and engineering. It is not about failing or winning in the bussiness sense but this business man point of view is just despicable from the point of view of an engineer who is trained to do a "good job".
Earlier quoted context omitted.
First, why are you calling it "add-on". Second, it's done via the same C ABI.
Node's been calling native code distributed in a npm package "add-ons" for a decade and a half. Fair call on the same C abi. Adapting to node 26.1.0's new FFI is happening in https://github.com/anomalyco/opentui/pull/104 . There's also some new FFI adapters opentui is adding there, and they're adding a worker. So there is some adaption. That was sort of the interesting useful actual look I thought might be informativ…
Earlier quoted context omitted.
It really is incredible how frequently these occur in everyday codebases of sufficient size.
We actually have a constant in our codebase to mark such bugs. You found one? Put it inside an: if (PREFER_EXISTING_BUGS_TO_NEW_ONES) { theOldBehavior(); } else { theNewBehavior(); } Then, if we ever go to do a v2 of the thing, we can review these existing "load bearing bugs" and see if they make sense to change.
Earlier quoted context omitted.
In what way? Foresight about what? It was an experiment before, regardless of people's reaction at the time doesn't make it less of an experiment back then. I feel like I'm misunderstanding this entire conversation right now.
Why are you defending them so much, lol. It's no longer an underdog open source project fighting for survival, it's a freaking Anthropic subsidiary that has been bought for hundreds of millions of dollars.
Earlier quoted context omitted.
There's a reasonable request to run the same analysis for the Zig version of the code as a comparison. In lieu of that, it seems the Swivel devs ran an analysis on Tigerbeetle, one of the other major Zig projects, and found only 7 medium/low priority issues: https://xcancel.com/SwivalAgent/status/2054063291266113994
To clarify, those are things an LLM considers to be issues, and LLMs can make mistakes. Some of those are clear false positives, others I need to revisit tomorrow to say one way or another.
As an educational thread, see this one from a week ago where Jarred again deflects from a merge decision and legions of foot soldiers attack anyone who predicted the impending merge: https://news.ycombinator.com/item?id=48073680 Didn't age well, did it?
As an educational thread, see this one from a week ago where Jarred again deflects from a merge decision and legions of foot soldiers attack anyone who predicted the impending merge: https://news.ycombinator.com/item?id=48073680 Didn't age well, did it?
It'll never cease to amaze me how many bootlickers are out of there that don't really care which boot to lick.