4 to 5 added like 2 tags, but was fully backwards compatibile. the painful upgrade you’re thinking of was 3 to 4 where they basically rewrote, it but don’t have any tutorial content other than one of the main devs making an absurdly long series of walkthrough videos so it’s impossible to find the topic you’re interested in
the codebase readability certainly suffers, and this isn’t the only case of shenanigans like this
found the following in our codebase the other day.
while(booleanFlag)
return;
thhere wasn’t more in the loop body, that was it. the loop conditional does exist and it can hurt you.
linting config itself wouldn’t be defined there, and it would be verified in ci and such, but a setting to tell vscode which linter and extension it should use to show warnings would be.
modern languages may have their own way for configuration but they don’t have a way to bind it to the list of vscode tasks and define how to run a debugger, which is the part that gets stored.
it’s easy to go overboard with extension suggestions, but I don’t think adding an extension for linter used, extension for formatter used, and any languages used if there’s a definitive extension.
My team is split between visual studio, vscode, and I use emacs. we have config for both vs and vscode in our repos since it makes working on a new project so much nicer and means we aren’t just sharing editor configs through side channels instead. it doesn’t do anything to me if I have editor config for an IDE I don’t use in the repo, but it makes it easier for someone new to jump in with a sort of same environment immediately
you don’t think they’ll just use some app to verify it? my state’s mdl doesn’t even show any personal info other than name, if they want birthday they have to scan it
fwiw, my state’s mobile id app doesn’t even ask for the location permission. so maybe some, but it’s not universal
your phone isn’t safe from anyone unless it’s been restarted since last unlocked, and is reasonably new. they have exploits for after it’s been unlocked incl while things are pinned
you realize they’re more than just your picture on a screen, right? there’s a whole public key private key verification process that happens, which covers your photo and personal info, at least from what I understand of ISO 18013-5.
if anything it should be almost impossible to make a fake mobile id, barring exploits in reader software or the govt leaking their private key.
I assume that’s just the actual vegetable, Google translate says that’s correct
yeah. stopping support helps end it, but in russia’s favor
that is a can of Folgers. I’d argue that incriminating a kitchen scale in the process makes it even worse
the state of texas agrees
this isn’t a community that they moderate tho
llvm exists. it might be a bit of effort if you’ve used too many proprietary gcc extensions, but for most things I don’t think it’s terrible to just switch between gcc and clang
they’re not the government but they are a political party with 15 seats in the parliament.
all of the jellyfin apps embed vlc as a player though, so the meme would have been vulnerable
CVE-2018-11529. Not that it’s a common thing, but it has happened
most things seem to have settled on this, but tabs are so much better for accessibility. programmers with bad vision can have trouble differentiating smaller indentation levels, while some of them just bump the font size up so high that 4 spaces takes up too much screen space. each one can set a tab width that is comfortable for them. https://alexandersandberg.com/articles/default-to-tabs-instead-of-spaces-for-an-accessible-first-environment/ has some good arguments
with a forced formatter and a configured editor there really isn’t any argument for spaces