|
|
|
|
|
by sapeien
3421 days ago
|
|
The current front-end web stack today is not the answer, I think that is not so controversial except to the most die-hard fanboys. Most of the contents in this handbook are going to be worthless in a year. Most front-end work is repetitive, with some minor variations. Rather than a framework, I think that perhaps an expert system for making web apps that is basically an interface for metaprogramming, would be a vast improvement over the current tech. |
|
Internet/web: no
Web browsers: no
DNS: no
HTTP: no
Web Hosting: no
UI Design: no
HTML: no
CSS: no
SEO: no
JavaScript: no
DOM, BOM, JQuery: no
Web Fonts: no
Accessibility: no
... and so on. But maybe you meant just Javascript libraries, which seem to make up just a small part of the content, but ok... Let's use "Module/Package Loading Tools" as a sample, because this thing is really to big to go through everything:
Browserify: Started in 2012. So... nope
Rollup: Started in 2015. No (but close!)
SystemJS: 2013. Nope, sorry
Webpack: 2013. Nope
And let's arbitrarily add the behemoth:
React: 2013. Nope
It appears there was an awful lot of new frameworks in 2013 and that let to the impression of framework churn. To perpetuate that narrative four years later seems to be more groupthink than reality.