5 ms·

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

by sapeien 10y 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.

threepipeproblm 10y ago
This comment makes so much more sense than their "Myth of the Full Stack Developer"
bigmanwalter 10y ago
I've been getting into web2py recently. It's a backend framework for python that autogenerates crud forms for you. It'll autogenerate an entire admin backend just from your table definitions in the ORM. I use Pjax to make page loads a bit quicker. Don't miss my front-end SPA framework whatsoever. Especially since my sites are SEO ready out of the box.
shaki-dora 10y ago
Let's see, going by the index, which technologies are younger than a year (the logic being "would your statement have made sense a year ago" because I obviously can't prove if a technology will still be relevant a year from now): 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.
- sapeien 10y ago
  jQuery has had the reputation of being very antiquated for a while. The problem that it set out to solve no longer exists. The same will be true of what you mentioned above. Now there are tools that solve problems that arise from other tools, it is getting very meta. An ecosystem like this cannot last indefinitely.
- ravenstine 10y ago
  What people are feeling as "framework churn" is probably more like framework uncertainty.
- milesrout 10y ago
  Those 2013 frameworks didn't get to the level of completion necessary to become popular until 2015, really.

by sapeien 10y ago

threepipeproblm 10y ago

This comment makes so much more sense than their "Myth of the Full Stack Developer"

bigmanwalter 10y ago

I've been getting into web2py recently. It's a backend framework for python that autogenerates crud forms for you. It'll autogenerate an entire admin backend just from your table definitions in the ORM. I use Pjax to make page loads a bit quicker. Don't miss my front-end SPA framework whatsoever. Especially since my sites are SEO ready out of the box.

shaki-dora 10y ago

Let's see, going by the index, which technologies are younger than a year (the logic being "would your statement have made sense a year ago" because I obviously can't prove if a technology will still be relevant a year from now): 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.

sapeien 10y ago
jQuery has had the reputation of being very antiquated for a while. The problem that it set out to solve no longer exists. The same will be true of what you mentioned above. Now there are tools that solve problems that arise from other tools, it is getting very meta. An ecosystem like this cannot last indefinitely.
ravenstine 10y ago
What people are feeling as "framework churn" is probably more like framework uncertainty.
milesrout 10y ago
Those 2013 frameworks didn't get to the level of completion necessary to become popular until 2015, really.