As much as this hurts, yeet;
as an alias throw;
is hilarious
As much as this hurts, yeet;
as an alias throw;
is hilarious
The technology behind the registry is fine (which is what I think @VinesNFluff meant)
But it’s execution in Windows was ass
In theory, a configuration manager with DB-like abilities (to maintain relationships, schematic integrity, and to abstract the file storage details), isn’t a bad idea
But the registry as it is today is pure pain
Sanity checks
Always, always check if your assumptions are true
I’ve been running Linux for 4 years, but this still hurts to read
I mean, you just need to look at the conflicting files, fix up the code, then stage those changes and pop a new commit
There’s no “special” merge conflict resolution commit “type”
As for fixing the code itself, I usually look at what changed between both versions, and then re-author the code such that both changes make “sense”
I’ve had no issues with @pawb.social and Voyager
Shell scripts don’t count
That’s not a programming language, that’s hieroglyphs
If you do that, you lose formatting and comments every time you load the source from disk