News for hackers. Stuff that matters.
Re:Is AI causing a repeat of Front end's Lost Decade? by sdevonoes on Friday May 29, 2026 @08:14AM (#48322127)
Most of software engineering is accidental complexity. Sharding, buffering, caching, load balancing, contention, async, functions, classes, recursion…

Big corporations behind LLMs are taking it all.

Re:Is AI causing a repeat of Front end's Lost Decade? by dannyw on Friday May 29, 2026 @08:26AM (#48322214)
There's a huge difference between everything you mentioned, and dealing with 'browser quirks' like:

  <!DOCTYPE html>
  <!--[if IE 8]> <html lang="en" class="ie8 no-js"> <![endif]-->
  <!--[if IE 9]> <html lang="en" class="ie9 no-js"> <![endif]-->
  <!--[if !IE]><!-->
  <html lang="en" class="no-js">
  <!--<![endif]-->
The points the author made simply aren't good arguments. Yes, frontend development was harder during those days, but not harder in a good or rewarding way.
Re:Is AI causing a repeat of Front end's Lost Decade? by layer8 on Friday May 29, 2026 @08:32AM (#48322275)
That’s not what accidental complexity means. Accidental complexity comes from design errors that could have in hindsight been avoided, meaning that if those errors hadn’t been made (made by accident, literally), there wouldn’t be any accidental complexity. The items you list aren’t accidents that could be avoided, they are necessities in achieving relevant goals.
Re:Is AI causing a repeat of Front end's Lost Decade? by sevenzero on Friday May 29, 2026 @08:47AM (#48322411)
Sharding, buffering, caching, load balancing are mostly issues 99% of devs will never have to work on. It gets relevant on high load pages, but most stuff out there wont ever need it.