for others - https://godbolt.org/z/osaKrxsPx

thanks

yes, but in this particular case I wouldn’t want to second guess my decrement operation just happens to also be calling the white house or whatnot. Just make a method.

that’s why c++ gets bullied

a logical skeuomorphism, how eccentric

the internet won’t ask shit, specific websites will, which can and should be avoided

you can check if DNS over HTTPS is working here

https://1.1.1.1/help/

Because this whole discussion is fucking stupid. There was no good reason for a change.

similarly, I use master and stable, it helps that PRs default to master, making changes to stable more intentional.

I’m glad I’m not part of “we”

That’s weird, I watched Children of Men last night

well, NOW I have to click. 😤

yeah, at the very least a collective thing in a classroom

not much, how about you?

Lingmo balls

Then we have the “it works on my machine” issue. I’m vehemently against symlinks pointing out of the code repository because of that.

yeah, I think these are the main hurdles for me:

1. Untracked files are not copied

When you create a new worktree, it is created from whatever is comitted, so gitignored or uncomitted files are not copied.

So if you have .env files, you have to copy them over manually. And for dependencies, like for example node_modules, you would have to run npm install again in the new worktree.

Mainly .env files, as they are handcrafted. And:

2. Editor / IDE complexity.

A few projects I work on are multi-root (using VS Code terminology) and that’s already complex enough. Adding worktree directories means adding a level to that, which I’m not bought in. And I don’t want a separate workspace for each branch I work on, that just shifts the complexity from git to the IDE / editor.

dua-cli - file storage analyzer, ncdu alternative topgrade - one tool to upgrade all package managers

a miserable week with Yanet Garcia? Fine, I’ll take it

nonsense, it was at least 3 beavers