Is that what I need to say to get enough black olives, they always add like 2 to each slice

It’s not their responsibility to make a proprietary shithole os easier to use

Even if you studied it, the answer boils down to "magic".

You take these magnets, and move them around these long snakes of metal (because electrons can move easily through metal) and that makes the electrons in the wires move.

Okay, why does moving around a magnet near metal make something inside it move?

Well there's something we call the "Lorentz force" which basically pushes a magnetic thing in a specific way if you move another magnetic thing around it

But why does that happen?

Magic

Yeah the thing is "living through" something doesn't really mean anything unless you were personally involved in it. Like I remember being in school on 9/11. I was a kid at the time, and everything I learned about it was from like CNN or similar. That doesn't make me an expert. There are definitely younger people who have studied history who will know more about it than me.

Thank you for the gaben 😔🙏

It will appear so to some people which will stir shit up, which is probably the point of this

It would be a monumental effort for smaller browsers to keep chromium extensions working, while the rest of the ecosystem moves to the new APIs. The only way that could work is if they all fork chromium and base their browsers on this new fork, and even then it's not guaranteed to develop a real ecosystem of plugins since chrome has more users than all of those other chromium browsers combined.

So yeah you have to use Firefox if you want to avoid that, at least for now.

Always merge when you're not sure. Rebasing rewrites your commit history, and merging with the squash flag discards history. In either case, you will not have a real log of what happened during development.

Why do you want that? Because it allows you to go back in time and search. For example, you could be looking for the exact commit that created a specific issue using git bisect. Rebasing all the commits in a feature branch makes it impossible to be sure they will even work, since they represent snapshots that never existed.

I'll never understand why people suggest you should default to rebasing. When prompted about why, it's usually some story about how it went wrong and it was just easier to do it the wrong way.

I'm not saying never squash or rebase. It depends on the situation but if you had to pick a default, it should be to simply merge.

I thought they were super convenient until I had to repair my phone and apple deleted my old sims because they thought there was a physical sim (there's wasn't). So I have to go to the agency for the sims I lost. One of them is in another country. So I won't be able to get that until I go there again.

Yes you will. It will just happen gradually over a couple years. No one is expecting this to happen overnight.

As someone who uses Django every day, I can tell you that the code is almost secondary to the amazing documentation. The documentation is such a core part of a framework that I don't see how it can be usable without really good and up to date documentation.

The fact that spring boot's documentation is so bad that it's impossible to even find a reference for a class you're using is, I'm sorry to say, garbage.

Isn't sync also free?