arxpoetica

Interesting to see how many things Gary got wrong.

Can you give an indication of what "next iteration" means in terms of timeline (even just ballpark)?

Svelte does not make any opinions about HTML attributes or tags, unlike JSX which contorts language standards such as `className` or disallowing style="..." without JS in CSS.

> The web matters

nuff said

Valid point I hadn't considered. Maybe the day isn't as soon as we think—perhaps both will exist...

...until we have speech muffler envelopes built into our devices.

There will come a day (with the advent of AI speech recognition) where keyboards will be obsolete.

That day is sooner than we think.

We may well look back on these lawsuits and laugh.

AI will likely steamroll current copyright considerations. If we live in a world where anything can be generated at whim, copyright considerations will seem less and less relevant or even possible.

Wishful thinking, but maybe we'll all turn away from obsession with ownership, and instead turn to feeding the poor, clothing the naked, visiting the sick and afflicted.

"The article was read, and lo, the examples clarified nothing! Names of protagonists were unknown, prophets recognized by only one. The main body of the text illuminated not the tense's usage. A synthetic, kitchen-sink example was sorely missed and yet never appeared."

tl;dr: noobs often like tailwind; veterans often dislike it. Both are right and both are wrong. Context is everything. Tailwind serves a function, but it will never fully replace native CSS APIs. "Can't we all just get along."

The default REM scaling is one of my main gripes about Tailwind.

Move to Utah.

Lots of software growth, but much of that is hardware related.

Many of these words ought to exist, ha. (As in, this is fun and clever.)