2 ms·
There's actually two facts you have to consider side by side 1. Front-end dev changes often 2. Websites have become worse at being websites Like AMP, single-
by zwaps 8y ago
There's actually two facts you have to consider side by side
1. Front-end dev changes often
2. Websites have become worse at being websites
Like AMP, single-page apps being mostly broken if not viewed in a pristine no-addon Chrome, loading megabytes of scripts to display a bit of text, overlays blocking the screen, sluggish scrolling, broken dynamic loading, misused and misunderstood statistical testing suites, fragile "graceful" third party content everywhere, less accessability, pop-ups, now scripted, again! ... the list goes on and on.
Being good at displaying text is now a killer feature of only few elite websites... Imagine that.
I believe front-end devs are much less sophisticated programmers than the frameworks they use. Those frameworks are usually years of work from big corps geared at a specific use-case. Back in the day, before so many new technologies, people were hesitant to write websites with tools they would not be able to write themselves.
Today, I do not think more than a fraction of front-end devs actually understand what all these new technologies are doing under the hood, nor could write them themselves.
And if you are already playing with Legos, it of course leads to putting in too much stuff without sense and too much stuff where it doesn't belong.
Finally, I think everyone (subconciously?) realized that the web has become bad. But if the only option you see is a new framework, then people chase after new tech instead of writing better websites with simple technologies.