kamen @ kamen @lemmy.world

Posts

5

Comments

639

Joined

2 yr. ago

Evolution do be weird sometimes.

It would if everybody votes with their wallet.

Something you're paying for should be completely ad free, period.

That's why you don't buy in a rush but rather track the price of something you're interested in buying over a couple of months.

Imagine playing a shooter over a network using this protocol.

By this logic one might say that DD/MM/YYYY works for alphabetical chronological sort if you don't go between months...

DD/MM for readability, YYYY/MM/DD for alphabetical sorting that's also chronological.

That's fair, but then why did he want to acquire it so bad?

It's as if this guy is trying to see how many times he can shoot himself in the foot and walk away.

The sad thing is that this happens because someone forces them to comply and not out of principle.

Yeah, but there's still the tendency to simplify things (e.g. "color" vs "colour") and the ever shortening of phrases as if it's difficult to say the whole thing ("macaroni and cheese").

Can I counteract that with "then maybe you should release finished products at the initial public release date"?

In order of appearance: wildcard, simplified, traditional.

Fair point. But that pollution still ends up in the atmosphere, just less concentrated above the cities.

Unless we're talking solar, wind or something else clean and renewable, EVs don't eliminate emissions, they just move them somewhere else.

My take is use a GUI for anything read-only/nondestructive (i.e. anything that won't modify your local or remote state). It's nice for example to compare the state of two branches.

For anything that does changes make sure you know what's happening under the hood, otherwise you might shoot yourself in the foot. It's convenient for example to do a commit and push in one go, but then you lose the ability to edit any changes (you're forced to either do another commit, or change your local commit and force push).

In VSCode you can go to the Output pane and switch to Git - there you'll see everything that gets done through Git's CLI for whatever you do through the GUI (although it can be a bit noisy); same goes other GUI utils.

One key thing that can help you wrap your head around rebasing is that branches get switched while you're doing it; so, say you're on branch feature and do git rebase master, for any merge conflict, whatever's marked "current" will be on master and what's "incoming" is from feature.

There's also git rerere that should in theory remember a resolution you do between two branches and reuse it every time after the first; I've rarely used it in practice; it would happen for long lived branches that don't get merged.

"The planet is fine! The people are fucked." - Carlin

Maybe they got something that you missed. I often miss details like that.

Probably around the pandemic when people became extra wary about hygiene - at least that's my observation. I've also noticed that people listen to voice messages like this - if you're in a loud environment and don't have headphones, it kind of makes sense. It still looks stupid, and for normal phone calls it is stupid, since both the earpiece and the microphone are optimised for having the phone on your ear.