101–110 of 127 posts
What makes Bun Bun is all the things that got removed from this project. Node is already powerful enough and well maintained. Why would anyone use this?
This got me thinking, What if you feed Bun's code into AI, and instead of Rewriting it in Rust, tell it to follow TigerStyle as much as possible?
> Allocate all memory at startup. Don't allocate after initialization.
It's not compatible with bun. It's not compatible with most programs.
Earlier quoted context omitted.
A new project based primarily on existing code is still a fork. Also Ship of Theseus.
Wasn't the point of the Ship of Theseus precisely that establishing wether something is or isn't something else is at least complicated? Using it right after saying "X is still Y" kind of seems to make the opposite point.
Similarly, a "fork" as we understand it in the context of software is this thing that, even though it's a modified copy, retains its extrinsic identity: "This software X was worked on in Y context, and is now being worked on in Z+ contexts". Same software, even if it gets a name change.
Earlier quoted context omitted.
Valkey made me forget redis existed in about a day. If I say redis now I actually mean valkey.
Why is valkey better?
Earlier quoted context omitted.
Because there will be a reason why the code was changed that introduced the bug. If you fix the bug you might inadvertently break a different piece of functionality. A git commit gives you the reason for the change and the context of what other files were changed at the same time. I’ve found that invaluable.
Guess I must be doing something wrong to never have encountered this issue in my 5 years.
Earlier quoted context omitted.
Guess I must be doing something wrong to never have encountered this issue in my 5 years.
I'm tempted to suggest you have encountered the issue but your team mates are shielding you from the consequences (with or without their knowledge).
Earlier quoted context omitted.
That actually is helpful, but it would require a git history that actually makes sense. I rarely encounter well thought out git histories. For me its often just dev ramblings or 10 word commit messages
If I can choose "badly maintained history" and "no history" I'll choose the former every time. That's even less of a problem when Claude can do a first pass for you.