or voting third party in a backwards outdated voting system like that of the US

understanding how a cpu works and how to write efficient programs is the easy part.

understanding why windows does [anything] is the hard part.

same logic as “if u hate america then leave”.

some people want to do their part to make the site (or country) better. they cant do that by giving up and going back to reddit. lemmy is great…but it could be better.

is op stupid ?

they likely aren’t good regex’s ;P … anything with more than, say, 6 operators is probably missing an edge case or will be outdated in a year (and then it’s impossible to determine its original intention)

ugh literally 1984

i think they mean that pronounciation matters for determing validity, not for the actual record or distinguishing between names

so John\r Doe ? depending on the software, when it gets printed, the carriage return will move the cursor to the start of the line without moving a line down, becoming \x20Doe.

no one is “good” with regex.

im sure the devs tasked at fixing that bug loved u ;-)

wait till u hear what the templeos people have to say about openbsd

cry about it

*indirectly named after an animal…

only the funniest internet meme this year

thats Smithers from The Simpsons

will you serve free as in free beer ?

people = a group

persons = a group of individuals

same with drainage holes on boats

you mispelt ‘pro’ as ‘con’ for some reason

“readability” is subjective. much like how there is no objective definition of “clean code”. i am not arguing that either option is more generally “readable”, i am insisting that people use a common standard regardless of your opinion on it. a bad convention is better than no convention. i dont personally like a lot of syntax conventions in languages, whether that be non-4-space indenting, curly braces on a new line, or early-declared variables. but i follow these conventions for the sake of consistency within a codebase or language, simplicity on linter/formatter choice, and not muddling up the diffs for every file.

if you want to use <br/> in a personal codebase, no-one is stopping you. i personally used to override every formatter to use 2-space indenting for example. but know that there is an official best practice, which you are not following. if you work in a shared codebase then PLEASE just follow whatever convention they have decided on, for the sake of everyone’s sanity.