[WesolyKubeczek]

> 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

I remember this period differently. The frontend work was mostly, sometimes solely, all about turning whatever monstrous PSD came from the designer’s sick mind into HTML, and getting shafted if the result was not pixel-for-pixel identical. When project leads heard the word “semantic”, they had to reach for the dictionary. Upon hearing the word “accessibility”, they would set the dictionary on fire.

[wongarsu]

And knowing the differences between various browsers meant negotiating whether the layout being 3px off on Internet Explorer was acceptable, or whether we should ship different CSS files for different browsers to fix this discrepancy

[actionfromafar]

I think there might have been two overlapping periods, but it definitely started out as you said. What I wonder is, will AI increase frontend churn, or calm it down? (More churn would be, new frontends because of new frontend frameworks, AI accelerated, less churn would be, because AI is trained on what existed before)

I think I also reject the premise of the article, that frameworks caused frontends dev to de-skill. For sure, that happened to some extent. But it also caused a lot of frontend devs to be incredibly skilled in their chosen niche. (React for instance.)

[WesolyKubeczek]

> will AI increase frontend churn, or calm it down?

The former. It’s definitely the former, at least until subsidized tokens run out.

[altmanaltman]

nostalgia is one hell of a drug

[WesolyKubeczek]

Web has always fucking sucked, and it fucking sucks today. The only way to make the web technologies not suck is to use them to power a vacuum cleaner.

[danielbln]

Please no, I need my vacuum to work reliably in every room.