Thank you! I feel like I’m taking crazy pills! Didn’t we have an entire multi-year SSR craze like 9 years ago and came to the same conclusion? But it’s React now so somehow it’s different?
-
-
Replying to @mikeal
9 years ago is how many bootcamp/accelerator/"full stack" classes?
2 replies 0 retweets 10 likes -
Replying to @slightlylate
sure, we‘ve created more developers since then than existed at the time, but still, it’s still in the web community.
1 reply 0 retweets 0 likes -
Replying to @mikeal
But we didn't train them. We gave them no community beyond the JS pushers and no norms beyond personal success.
2 replies 0 retweets 12 likes -
Replying to @slightlylate @mikeal
We tried. Again, and again and again. That's one of the reasons I'm thinking of leaving the industry.
3 replies 0 retweets 4 likes -
This industry is f$^$ up. I have 20yrs exp., can literally start installing the os and go all the way up to FE perf. Yet, the only thing people wants now is someone who would do everything with React. Fuck that. Almost nobody NEEDS React. That's not for user's sake
#DXisBS1 reply 7 retweets 29 likes -
The thing I honestly don't understand (well, one of them) is that it isn't even a good developer experience! Install this huge pile of libraries? Set up this script? Run this command to watch changes and rebuild? How is that a better experience than "put files in a folder; done"?
3 replies 0 retweets 15 likes -
I think part of this is explainable by the fact that many have been doing most of this for years (arguably the beginning), and it moving into something js based and the nice parts of something like jsx instead feels like a better alternative
1 reply 0 retweets 1 like -
Replying to @briankardell @sil and
I locate this in the proprietary forks of HTML and JS that everybody is cool with suddenly. The tax that goes with them is high, and the build-time tax seems "better"
3 replies 0 retweets 0 likes -
Replying to @slightlylate @sil and
I get that, but at the same time, apples to apples: asp, jsp, php, moustache, velocity, freemarker, handlebars, pug, markdown, jstl, etc etc etc were not strictly HTML either though, right? <include..> was not HTML. And there were a million of them, based on whole diff models no?
3 replies 0 retweets 2 likes
They didn't come with the need for the web developer to run a build step; in fact, their design wisdom was explicitly in eschewing them!
-
-
Replying to @slightlylate @briankardell and
They either put building in the server (where it belongs) or made the client runtime bits close enough to the metal that their notjs/nothtml *was* the runtime artifact. That is, they layered on but didn't hard fork, conscious of the costs.
1 reply 0 retweets 3 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.