Top
Best
New

Posted by xyzal 7 hours ago

Is AI causing a repeat of Front end's Lost Decade?(mastrojs.github.io)
193 points | 188 commentspage 5
Npovview 6 hours ago|
if you value intelligence (and likely income from that intelligence) above all other human qualities, you're gonna have a bad time. -Ilya.
sublinear 6 hours ago||
> frontend used to be a highly specialized skill, requiring knowledge of semantic HTML, CSS, the differences of various browsers, accessibility, progressive enhancement, network performance, interface design and user testing – to just name a few.

It still is!

> To distinguish what they’re doing from what “frontend” has become, practitioners of this arcane art nowadays often refer to it as the “front of the frontend”.

I have never heard this term before, but I'm sure someone will point me to the bullshit influencer who came up with it?

Frontend frameworks are really just for web apps and most frontend devs are familiar with several. If they cannot also write a web page from scratch, they're not really a web dev. This is not up for debate. If you hire someone for the role, you need them to handle the work. AI is not going to help you here when it gets into the testing and bugfix phase.

standardUser 4 hours ago||
Honestly I think what is missing is not developers but designers. Or, I should say, designers hired to create competent designs that serve people well and not to instead manipulate users. If you want better front ends - get more and better designers! As for front-end code, I don't expect to ever write a line of that again in my life.
mock-possum 3 hours ago||
Opening with this claim of ‘Front end’s Lost Decade’ then not explaining what that is is infuriating to me, a front end developer - which decade was this supposed to be? How/Why was it ‘lost?’ How did I miss it?
Devasta 5 hours ago||
People don't use web tech because they care about quality, they target it very specifically because its one of the places where quality doesn't matter. If your native app crashes, your users will curse your name. Webpage or Electron slop freezes? They'll shrug and restart.

This idea that quality ever existed on the web is ahistorical at best.

iLoveOncall 6 hours ago||
> JavaScript frameworks have deskilled frontend development in the last decade. As someone who started with HTML/CSS and a bit of PHP, later did Ruby on Rails, and then was frontend team lead of a major Swiss newspaper (Next.js at the time), I’ve seen the transformation first-hand

I'm sorry but that simply does not make any sense. How is increasing the breadth of your skills leading to a deskilling?

gobdovan 6 hours ago||
Read in context. He's referring to the evolution of skill at group level, he even puts out the definition of deskilling and mentions 'skilled labor'. He then explains how frontend used to be a 'highly specialized skill', and how modern devs use Frameworks to consider browsers almost hidden compilation targets.
seszett 6 hours ago|||
The article explains at length what they mean by "deskilling" and it does not mean that individuals lose their skills.

The author having worked with various technologies over time is also not an example of "deskilling", it's a way of asserting that they have had time to observe the deskilling of the domain (since deskilling means a particular domain requires less specialised skills than it did before, not that the workers are losing skills) happen.

WesolyKubeczek 6 hours ago|||
The phenomenon of bootcamp graduates who knew React but did not know JavaScript.
cryo32 6 hours ago||
yes and now they get Claude to write React and don't know that or JavaScript.

When something goes wrong, no one understands anything.

efsher_azoy2 6 hours ago|||
I guess the author never tried to write big FE application in jQuery :D It definitely required some skill.
epolanski 6 hours ago|||
Just watch the terrible soup produced by MIT-bred Leetcode ninja "engineers" in money raining startups and FAANGs.

Low accessibility, terrible performance, lack of any fundamentals of html and css, abuse of those awful solutions like Tailwind or using 2016 technologies like React for rendering what should mostly be static websites + some web component, all plagued by memory leaks and very basic usability bugs.

lpcvoid 6 hours ago||
[dead]
js4ever 5 hours ago||
[flagged]
euejcidnf 5 hours ago||
[flagged]
volume_tech 5 hours ago|
[dead]