I think you might have skipped over the 10,000+ years of strict feudalism, a shrouded theocracy pushing their century-spanning agendas, aristocracy through landed gentry, and a drug-addled transportation cartel, all overseen by a massive, monopolistic megacorporation that controls all trade, economic affairs, and commerce throughout the universe. And everyone's a drug addict if they can afford it.
But sure, at least they didn't have AI! lol!
In other words, Warhammer 40K but without any aliens to trigger a massive xenophobic response that removed all warlike guardrails.
Not known for deep understanding of high technology? The Catholic Church was behind the scientific discovery of The Big Bang through the Catholic priest (and astrophysicist) Lamaître. Mendel, the father of modern genetics, was an Augustinian friar. Steno, a Catholic bishop, formulated the foundational principles of stratigraphy, establishing geology as a formal science. Secchi, a Jesuit priest, was a pioneer in spectroscopy and the first to establish that the Sun is a star, creating the first stellar classification system.
Visually impaired people use smartphones too. If the app isn't supporting the accessibility features of the platform, it should still be held liable under the ADA.
(Unfortunately it won't as was found when Southwest Airlines was sued over this. Congress hasn't updated the ADA to include web sites since the ADA precedes the web and so it wasn't enumerated explicitly. Also unfortunately, the GOP who have never been huge fans of the ADA have blocked any attempts at patching that hole.)
But check out the settings on your iPhone/iPad or Android device. Whole sections dedicated to accessibility, especially for the visually impaired.
If the Executive Branch doesn't care about the Constitution and inconvenient laws when directing the law enforcement agencies under its control, Congress doesn't hold the executive to account by either withholding funds or threatening impeachment, and the SCOTUS majority doesn't try to rein in these acts while seeming to lack the ability to enforce its own decisions, the words printed on the Constitution are just useless ink.
Elections have consequences, and we're all paying them. Some paying a lot more than others.
I'd rather go to Svelte for lower bundle size than Preact, better performance than Preact, and clearer code with fewer lines written than Preact.
Sure, I'd lose access to the React ecosystem, but I'd also gain access to the vast ecosystem of vanilla JS libraries without having to write/use a wrapper, so that's a wash. (bind:this is awesome!)
The "reconcile" (my God do geeks love making what they do sound fancier than it is) does not match the HTML5 parser "reconciliation" spec. The DOM element API "emissions" match the order triggered by the markup parsers. Y'all are tiresome sometimes.
Do you have to close all of your tags? Yes. Is the markup based on HTML with XML rules like closing tags? Yes. Do you even have to close the tags of your custom components? Yes. When generating your createElement sequence from JSX, does it create or close tags in a different order/hierarchy than what you specified in the JSX? No. Does it emit markup or element creation calls that match the parsing behavior of HTML5? No.
Walks like an XHTML duck. Talks like an XHTML duck. It's an XHTML duck despite the JS interop and the lack of DTD preamble.
Learn JavaScript first, then React. Far too many devs know the React APIs without any context. If you know JS/TS, any framework is learnable. If you don't, your React code will never improve past mediocre and bloated.
Strong foundational knowledge in HTML and CSS helps as well. Still amazes me how many folks put onclick handlers on div tags and freak out when margins collapse.
The fact that you have to go to often heroic measures to keep your bundle size under 500KB even for simple apps doesn't make it irrelevant or useless. It is indeed bloated: on the development boilerplate side, the bundling/deployment side, and the browser runtime experience.
With an experienced and top-notch developer, anything is possible in any language or framework. For the other 95% of devs out there—especially on a team where the lead doesn't keep a strong grip on the reins—React turns to mud awfully fast. But it's mud with an extensive ecosystem and tons of inertia helping it succeed.
Smaller, cleaner, and faster code while still focusing on dynamic interfaces? Svelte or SolidJS
Focus on server-side HTML rendering with little to no browser dynamism? PHP (It really is quite nice now.)
Focus on server-side HTML rendering with some browser dynamism? HTMX + server framework (PHP, Django, Go templates, etc.)
Getting a job as quickly and easily as possible, especially at larger companies? React or Angular (You're a cog in the machine, but cogs often get better paychecks to deal with multi-megabyte code blobs.)
Can't decide between code elegance/performance and finding a job, so you're willing to compromise a little on both? Vue
I like Svelte too, but take another look at Angular. Your memories of Angular 9 don't match up anymore. It's A LOT more streamlined now with so much less boilerplate than before. And signals.
That said, transitioning to some backend or infrastructure focus never hurt anyone. It's good to see problems from different perspectives and roles. No one ever got fired for knowing too much SQL.
I'm still laughing about the fact that JSX renders to XHTML, not the HTML5 that browsers actually use. 99% of the time they're the same and parsing occurs as expected. That last 1%, things get weird quick.
No accounting for taste, I suppose. For me, class components were absolutely horrid and hooks simply made it less horrid by comparison. I guess anything can seem amazing after you've been stuck in knee-deep mud.
Studies have shown that number of lines of code is directly proportional to the number of bugs produced in that code, regardless of language or framework. Would it stand to reason then that a framework (yes, I said it) like React with its boilerplate is suboptimal, even with the new compiler?
As an old school web dev, to this day I cannot understand how multi-megabyte JavaScript code blobs (after gzipping!) became "normal" and acceptable.
Ha! plpgsql's seemingly sole purpose is to inject imperative code into a set-based environment. Probably does it more smoothly than most pl languages, but that's at the cost of imperative clarity.
But you're right. Postgres does allow for-loops like this. (They're also slower than the equivalent set-oriented approach.)
I love LATERALs, but this still fits within set theory and a bulk application rather than an iterative for-loop. It may even be implemented as a for-loop within the engine, but SQL being declarative abstracts that away from the query interface.
It's sets all the way down. A set of f(x) is still a set.
But sure, at least they didn't have AI! lol!
In other words, Warhammer 40K but without any aliens to trigger a massive xenophobic response that removed all warlike guardrails.