100% agree. It’s just not the same

I’ve said it once, I’ll say it again. Where tab groups?

You deserve all the upvotes

This was funny as shit. All the people that downvoted you can get fucked

Got angry when I saw the title and came here to start calling bullshit but I’m glad that it’s already been handled.

That would be a next level bamboozle but if it were true I’m wouldn’t even be mad.

If they came out and said this is what we did, I would donate to them just because of how gangster that move is

Bought this as a Christmas gift for someone, highly recommend. Everyone lost their shit. I think I saved Christmas with this shirt

Genuine question, where in Canada are you getting that price and is that including the Demand charge?

Cheap power in Canada is something I would genuinely be interested in

Where tab groups?

LOL. Admittedly only after I DuckDuckGo’d an explanation

Meme too sophisticated, it’s a 5 out of 7 at best.

How are you supposed to stream snipe if you don’t have twitch open?

After writing a massive list of assumptions and trying to explain it with some ridiculously complex reasoning, I realised the simplest reason is any calls to the backend need to be made again incase the data has changed. The response will have a cascading effect of calling functions and setting up event listeners or triggering events.

Obviously there are more reasons but this is the most obvious reason to do it.

Obligatory Corridor Video

Pirelli

Thank you for answering the question like a helpful person instead of just instantly posting “you’re wrong and you should use this instead”

It’s so frustrating when someone doesn’t understand that there are constraints that OP hasn’t included because it’s not relevant to the question.

It means both, twice a week and every two weeks. It’s confusing but what part of english isnt?

I wonder if it pairs well with some tendies

But if you didn’t have 200 configs files did you even build a project?

In theory yes. In reality it is highly unlikely to the point that you shouldn’t worry about it.

If someone happens to find an exploit that lets them execute code on the host machine or access to memory addresses that aren’t theirs. Then 100% they could infect everything.

Likelihood very low, would have to be the perfect storm of exploit plus permissions plus apples permissions to access stuff being broad enough that it can do what it wants.

If you are super paranoid, your Mac is taking snapshots of your disk in the background so you can always restore back every single time you do something questionable