Yeah, I've seen things spelled this way before in barbershop arrangements. Usually because it's less accidentals. I think it makes sense from a "what notes should I play" perspective, but seeing these chords spelled in a weird way gives you insight into how some composers actually think, and all that REALLY matters is what the music sounds like.
HTML isn't a "tree of elements" though; it's about content token sequences described by regular languages where the symbols can also represent nested markup. The regular content model stuff is what drives SGML/HTML tag omission/inference and is a major feature of markup languages as a text format compared to primitive co-inductive expression syntax a la s-expr and co.
"Please write the first couple sections for an article based exclusively on the content below. Be direct and concise, but dive into details. Use a personal tone with “you” language. Write in the style of blogger Brian Dean. Use short paragraphs for easy readability. Change the wording so we don’t plagiarize the source material. Make the headlines somewhat catchy and intriguing while still concisely communicating what each section is about.
- AI, also known as artificial intelligence, is overhyped
- AI will never be able to replicate what a human can do
- AI will never replace humans
- AI is a trend that will die out
- AI is not really artificial intelligence, just a trick"
How many times do you think somebody’s penis has to be attacked by insects before preventing that becomes the main “figure of merit” for evaluating sleeping positions? I think it is not very far from 1 time.
The article does in fact give an explanation for each item. (Perhaps you may not think it's eli5. I found them mostly fairly explanatory[1], but... maybe they're more eli20? And maybe fairly short and terse?)
[1] Except double-entry bookkeeping, which didn't explain anything. And the AD-AS model, which probably is not possible to explain in a concise way or an eli5 way. And...
I made a paint app with jQuery, and thought it would be a good idea to refactor to React so I could run it on a Next js server and add some multi user support, with later plans of refactoring that to a React native app.
Completely painted into a corner, I gave up after about six hours of trying to get my event listeners to work with React.
It's a shame, because there's so much server side stuff I could be doing right out of the box with Next, but now I basically need to choose a completely different architecture from the one I want because I thought it would be easier to use jQuery.
In all fairness, direct DOM manipulation works a lot better than React for the original app, but now I have to keep DOM state in sync with my server, which is a whole other challenge that React solves quite nicely.
