You can relax. If you install an Ubuntu based OS (v24.04 LTS for long term support) like Lubuntu or even Linux Mint you’ll have a pretty stable system with great hardware support and lots of online help.

And as long as you don’t mess with any files outside of your home directory and keep a regular backup of your system you’ll be just fine.

Also, there’s a lesson to be learned in our mistakes. In the future, keep a copy of files you want to delete but are not sure what they are for, before you actually delete them.

ISO 8601

Especially if the topic is sex, as OP claims. Like WTF.

Mine will probably be Bottles.

The team behind that application did a fantastic job. Wine was due for something much more user friendly like this. And integration with Proton, allowing 3D acceleration is the cherry on top.

When using KDE, press meta-T to activate the equivalent of Windows Power Toys’ Fancy Zones.

You can then set tiling zones and when you drag a window, hold shift at the same time to lock it in one of the zones.

I was going to say the same. This was my introduction to MST3K as well.

The movie’s theme song, the actors, the plot and the cast’s comments were the cherry on top.

IDEs have come a long way. But I’ve done qt development using Jetbrains Clion IDE and QTCreator. I don’t remember it being that difficult. Then again, I started programming using Turbo Pascal and Turbo C. So …

I dunno. Having worked with Java and c#, web dev, c++, I found working with QT in C++ to be so much easier.

Ditto.

I agree.

Unfortunately, from experience, nobody seems to have time for that. They just learn git pull, push, add, commit and merge and that’s about it.

Sometimes they’ll use checkout and end up in detached head and have a panic attack. That’s when I come in. lol

Who cares when it could run Doom in full screen?

Yeah that’s what I did as a workaround. Reset (soft) to the first parent commit and do a single commit with all the changes.

What I do locally on my branch is my own business.

Honestly, when doing a merge/pull request into the parent branch, that’s when you squash. You don’t need the entire history of a development branch in main.

Yeah I saw someone else’s answer and I totally learned something new today.

Holy shit! I never took the time to read about it rerere. But it all makes sense now.

However, it’s still a lot of extra steps for what could otherwise be really simple with a regular merge.

Is there really a big advantage in using rebase vs merge other than trying to keep a single line of progress in the history? It’s it really worth all the hassle? Especially if you’re using a squash merge in a pull request…

Wasn’t that always the case? I mean compared to my IBM PC clone, mine did way more and cost way less. And it was upgradeable. And mine could play games.

All it can take is one commit in the parent branch. If your branch has many commits because you’re a commit freak then your fucked.

Absolutely

I consider myself above average in terms of Git know how. But I’ve come across situations using rebase where you’re stuck resolving the same conflicts over several commits.

I still don’t understand that part quite well.

This doesn’t happen when you do a normal merge though. Making it easier to manage

You need to merge more often.

Rebase. That’s where the real trauma is.