JavaScript: The Good Parts by Douglas Crockford is a comically short book. React: The Good Parts would be shorter still.
219 karma · joined May 9, 2013
https://www.blipjoy.com https://github.com/parasyte
JavaScript: The Good Parts by Douglas Crockford is a comically short book. React: The Good Parts would be shorter still.
And if you needed to manipulate strings to generate HTML, you'd be doing so with some kind of template mechanism, like string concatenation or substring substitutions. John Resig, author of jQuery, wrote Secrets of the JavaScript Ninja in 2008 [1], offering a small templating engine that does exactly that. The first commit in the Underscore library credits this book for their `template` method [2].
I think your chronology is skewed or confused. "SPAs" have been brewing in some form since the mid-2000's, when people stopped writing plain old HTML and CSS. Everything was jQuery UI widgets and AJAX, Prototype and Underscore templates. HTML died a very long time ago.
[1]: https://blog.codinghorror.com/secrets-of-the-javascript-ninj...
[2]: https://github.com/jashkenas/underscore/commit/02ede85b539a8...
Keep in mind, these are not products in the endless feature treadmill promoted by scrum.
- A mod manager for Vintage Story in Swift.
- A GameShark Pro adapter using an ESP32 that hosts a web app for dumping N64 ROMs and searching for cheat codes.
I have been out of the tech startup labor market for many years. But when I was doing hiring in a startup around 2017, we had to put specific, conscious effort into accepting inexperienced candidates. The default mode for hiring is finding like-minded individuals whose experience overlaps with the existing team.
Using AI as a scapegoat for hiring freezes or layoffs is just more FUD. Like all propaganda campaigns, the purpose of fatigue is to induce an amnesia effect.
They did. Now it's all JSX or htmx or some other favored template or DSL monstrosity. Most people do not write HTML or CSS, and haven't in decades. You're spot on.
This says nothing about quality, however. Quality of HTML/CSS is purely subjective. A website's presentation layer cannot meet any technical standard metric for quality in engineering or manufacturing such as durability, reliability, efficiency, or safety.
We can stop any time, now. Money was already a satisfactory root cause.
As a counterexample, tobacco taxation is less effective for reducing smoking than alternative policies [1]. So, yes, we can hope that higher taxes help people make better choices. Or we can implement better policies that are known to be more effective.
[1]: https://web.archive.org/web/20250323131704/https://tobacco.u...
Having identified the true root of the problem, I would recommend directing resources towards dismantling advertising. Focusing on anything else is wasted effort.
[1]: https://ourworldindata.org/technology-long-run
[2]: https://waitbutwhy.com/2015/01/artificial-intelligence-revol...
I don't care.
I hear these complaints multiple times per day. Not just "nearly daily". The backlash has long since drowned out the original source. The ad nauseam anguish has been steadily increasing for months.
I almost prefer to listen to asshole CEOs at this point. At least they have more to say than just repeating these same points.
Being dismissive of AI panic is healthy. What you're engaging in is not.
I was going to say the same of you.
Touché.
FWIW, I don't consider surgeons to be extortionists. That's an absurdity that you are using as illustrative of why I'm wrong to call software developers extortionists when they charge for a privilege that should be a right. There are two issues with the comparison: 1) I did not call software engineers extortionists (but sure, I can see how you drew that conclusion), and 2) people absolutely should have a right to life-saving surgery and should not be denied on the basis of payment.
There is a huge preexisting problem: health care is not a human right [1]. There are other issues with health care that isn't just money. Many life-saving transplant patents are stuck in a wait list, for instance, and many die waiting. I do what I can. I'm a registered organ donor and try not to destroy my liver. I just haven't died yet, and I still need it. But this line of reasoning is off in the weeds, and I won't pursue it further.
Perhaps what it comes down to is that you have a pro-capitalist outlook, and I have They Live sunglasses.
A lean website can work just fine on complete trash connections like GPRS or Comcast without incremental loading. Web developers are not incentivized to make lean websites.
SPAs add unnecessary complexity -> increasing page weight -> making finer grained incremental loading more important -> requiring even more code. It's a self-induced problem.
As a corollary, McMaster Carr is often used as an example of a website that didn't fall into the SPA trap, and customers greatly benefit from that [1]. The front page weighs about 14 MB with all of the images, but the loading experience is great even with network throttling simulating a poor connection. There is a good reason the site has this reputation.
Overengineering is the true root of all evil. Web developers cannot learn that fast enough.