oh you poor soul

do people not still do this ??

unless you are using ISO 8601 then i think u should...

-------- midnight toker ?

Ha, a Ha, ha A ah Ha Ha-ha! :)

where angry bird 1

I think it is relatively trustworthy, and I have used it to install Youtube to be patched with ReVanced. I would still be a little cautious downloading a apk from any website, but apkmirror might be the safest option due to it's popularity. but still use F-Droid or similar if you have the option.

**Land SHOULDN'T vote.

"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.

Why would you want that.

a kernel module should not be written in Go

op failed to realise that him smiling isnt the reason hes in special ed

excluding liking kids or animals. and relatives or nonconsenting people if relevant

An explanation of this problem can be found on the official W3C HTML validator wiki.

HTML parsers only allow this to stop pages breaking when developers make mistakes; see this Computerphile video. 'Able to be parsed correctly' is not the soul criterion for it a syntax being preferred, otherwise we would all leave our <p> elements unclosed.

Yes, it is not "incorrect" to write <br/>, but it is widely considered bad practice. For one, it makes it inconsistent with XML. Linters will often even "correct" this for you.

I personally find the official style (<br>) to be more readable, but this is a matter of personal opinion. Oh, and I used to have the same stance as you, but I also used to think that Python's whitespace-based syntax was superior...

At the end of the day, regardless of anyone's opinion, we should come to SOME consensus...and considering that W3C already endorses <br>, we should use this style.

found the react dev

its okay. you can come out ;)

Yes.

but op is verified

more likely something about "the jews"

I blame little Bobby Tables.