Makes sense. It’s like having your personal undergrad hobby coder. It may get something right here and there but for professional coding it’s still worse than the gold standard (googling Stackoverflow).

Onfuscators probably use it though, so no spec ever will be able to get rid of this crap.

BASIC. At least VB.

It’s Proton VPN. Lack of IPv6 support is a downer but I wouldn’t call them shit.

Edit: maybe elaborate why you deem IPv6 so crucial? As I said: everything works just fine without.

What the fuck are you talking about? My ISP supports IPv6 just fine, but following my VPN’s advice I disable it (on certain devices at least) for privacy concerns. And it makes exactly zero difference in functionality.

Auto-“correct”. Thanks, fixed.

Why should we care? So address space may run out eventually - that’s our ISPs’ problem.

Other than that I actually don’t like every device to have a globally unique address - makes tracking even easier than fingerprinting.

That’s also why my VPN provider recommends to disable IPv6 since they don’t support it.

More like:

Computer scientist: We have made a text generator

Everyone: tExT iS iNtElLiGeNcE

Best to join a C++ community on some social media then. They’ll tell you immediately why “C with classes” isn’t C++.

OK, that’s excessively “convenient” for booleans. But I don’t get the passionate YAML hate, seems like a simple enough language for config. Didn’t have the pleasure (“pleasure”?) to work with it though, so what’s why else is it shitty?

I suppressed most of my former js knowledge but I guess it’s a string now.

Basically lower and upper end of sizes, yes. Team sizes too.

Worked with both, both worked fine.

Yes.

Right button right before a three week vacation.

That joke is possibly older than SQL injection.

Maybe she just wasn’t impressed by your noob skills and is having doubts herself?

What do you mean? Like not pushing at all until you’re making the MR? Because if the branch has ever been pushed before and you rebase, you’re gonna need to force push the branch to update it.

Not everyone works in large orgs that require pull requests. We have a dev branch multiple devs push to and just branch off for test phase. So I commit locally (also interactive rebasing when fixing stuff from earlier). When I’m ready to push, I fetch, rebase and push. I never force push here.

I was replying to the other comment, not yours.

I know. Answered anyway because I thought of the same thing as you.

Though there’s not really a way of using rebasing without force pushing unless it’s a no-op.

I like to rebase after fetching and before pushing. IMO that’s the most sensible way to use it even in teams that generally prefer merge. It’s also not obvious to beginners since pull is defaulted to fetch+merge.

Of course it has its uses. I didn’t mention them because the guy just learned about rebase - it’s unlikely to be applied flawlessly from the start.