Because we’re more akin to LLMs than we might be comfortable to admit. Or at least parts of us, subsystems of our psyches… Brains are belief engines more than they are objective parsers of reality.

Wow fuckin’ wooosh with you and that one hey? Only a very weak beta would feel even remotely attacked by that movie. Good luck Chuck!

Yes, that is another benefit, once you start getting muscle memory with the library. You start to parcel things by context a bit more. It’s upped my habit of discrete commit-by-hunks, which also serves as a nice self-review of the work.

👏 Super duper this is the way. No notes!

https://gitmoji.dev/

Quasi parallel reply to your other post, this would kind of echo the want for a capital letter at the start of the commit message. Icon indicates overall topic nature of commits.

Lets say I am adding a database migration and my commit is the migration file and the schema. My commit message might be:

     🗃️ Add notes to Users table

So anyone looking at the eventual pr will see the icon and know that this bunch of work will affect db without all that tedious “reading the code” part of the review, or for team members who didn’t participate in reviews.

I was initially hesitant to adopt it but I have very reasonable, younger team mates for whom emojis are part of the standard vocabulary. I gradually came to appreciate and value the ability to convey more context in my commits this way. I’m still guilty of the occasionally overusing:

   ♻️ Fix the thing

type messages when I’m lazy; doesn’t fix that bad habit, but I’m generally much happier reading mine or someone else’s PR commit summary with this extra bit of context added.

Could have been worse. I mean, like, imagine of you were using like CVS and you put a watch on the root! Haha and then like every trivial commit in the repo caused everyone to in the entire org to get an email and it crashed the email servers.

Like who’d even DO that?! Though, I bet if you met that guy he’d be ok. Like not a jerk, and pretty sorry for all those emails. A cool guy.

You nailed it with the critique of commit messages. We use gitmoji to convey at-a-glance topic for commits and otherwise adhere to Tim Pope’s school of getting to the point

100% they do. Rebase is an everyday thing, merge is for PRs (for me anyway). Or merges are for regular branches if you roll that way. The only wrong answer is the one that causes you to lose commits and have to use reflog, cos…well, then you done messed up now son… (but even then hope lives on!)

Here’s an example

Say I work on authentication under feature/auth Monday and get some done. Tuesday an urgent feature request for some logging work comes in and I complete it on feature/logging and merge clean to main. To make sure all my code from Monday will work, I will then switch to feature/auth and then git pull --rebase origin main. Now my auth commits start after the merge commit from the logging pr.

Merge keeps the original timeline. Your commits go in along with anything else that happened relative to the branch you based your work off (probably main). This generates a merge commit.

Rebase will replay all the commits that happened while you were doing your work before your commits happen, and then put yours at the HEAD, so that they are the most recent commits. You have to mitigate any conflicts that impact the same files as these commits are replayed, if any conflicts arise. These are resolved the same way any merge conflict is. There is no frivolous merge commit in this scenario.

TlDR; End result, everything that happened to the branch minus your work, happens. Then your stuff happens after. Much tidy and clean.

Fuck a merge commit! Rebase ervray day bay bayyy.

Somehow I doubt a lot of these opinions are steeped in the experience of building an HTML layout using tables, transparent gifs and inline width attributes. Shit was wild before CSS.

I’m feeling this. My day today was roont by plasma 6. I still can’t unlock any LUKS usb drives with dolphin.

Hmmm…

Looks like:

• AMD Ryzen 7 3800X
• on an Asus ROG STRIX B550-I
• 32GB DDR4 @ 2666
• 3070 RTX

Honestly, it’s possible that I just don’t notice low framerate as I’m a product of the Atari/NES gen of console gamers; my standards may be co-opted. I’m just reporting that my experience has been positive. Fair to say though that Wayland is still hit and miss, and still is. I general avoid it and stick to x while using steam, and tinker around with it when X’s idiosyncracies bother me enough. Nvidia in general just hasn’t picked my berries like it seems to have for others. Certainly not enough to ever make me retreat to a windows install 😁

Really? I’m having a very dissimilar experience, and am also on Manjaro. Drivers were a peach to install and I get at least as good as performance on windows…to the extent that the dual boot has (over the years) become just a single boot. I’m even running a valve index on it - Alyx runs smooth. Built in 2019.

TBH I’m surprised at a lot of these threads about Nvidia as it’s just been a few times that the drivers didn’t work out on an update and I had a black screen. But I’ve had almost as many breaking issues from non Nvidia related stuff in its lifetime.

Now with pumpkin spice melange!

Get a free Juice of Sapho with every purchase. (May stain lips)

Works great. Very occasionally I get an error (black screen) requiring me to disconnect and reconnect the display port adapter but I get the same occasional nonsense with my regular monitor too so 🤷.

Usually that happens after new Nvidia drivers too so…

Love me some Kate.

That’s relatable pain. So far I’ve had a stable 5ish years, and only had 2 issues, one being my own tomfoolery with some KDE config, the other being Nvidia, and I don’t gotta tell you kids about Nvidia and Linux, regardless of distro…

ETA: endeavour looks really slick too, thx for broadening my world. Probably need to justify a wipe of a laptop to try that out.

Lol at all the hostile responses not getting that this is a meme. Freaking whoosh.