So the big important part of git is that it's a collection of commits. A branch is just a labeled commit and each commit is a list of what changed from the parent. Rebasing (the most confusing one for people) is when you fiddle with a commit from underneath yourself. Or in even more simple terms editing a parent commit. Rebasing is extremely powerful but most useful for when you notice a bug you wrote a couple commits ago. Fixing such issues via rebase (or !fixup commits you auto squash at the end) keeps your history clean. It's as though you never wrote the bug. The other thing you do a lot with rebasing is moving your branch up in the history cause somebody updated the remote.

I wouldn't be shocked if it was astro-terfing

Everyone from the lemmy.blahaj.zone instance that I've interacted with or seen have been trolls. Those guys are super weirdos idk what their deal is. It's baffling seeing what they claim to stand for

Wow, that looks like a nightmare

There are a couple projects with native block chain art but as you might expect it's low resolution pixel art due to the nature of block chain being prohibitively expensive to use as storage

Brave is forked from Chromium so hypothetically they could maintain V2 but they'd need their own store as they currently rely on Googles

He is not

Yep that's why I refuse to use standard libraries. It just makes my code too complicated...

Yup. The moron even admitted it too!

Wealth issue (not really shits cheap)

All cars are bad. The car you already own is less bad than a brand new car

Counterintuitive but more instructions are usually better. It enables you (but let's be honest the compiler) to be much more specific which usually have positive performance implications for minimal if any binary size. Take for example SIMD which is hyper specific math operations on large chunks of data. These instructions are extremely specific but when properly utilized have huge performance improvements.