It is a fact that a lot of what traditionally used to happen server-side has moved to the client. /1
-
-
Replying to @John_Idol @Pinboard
Tools are being developed to let people do client-side the same kind of stuff they do server-side, infrastructure wise. /2
2 replies 0 retweets 11 likes -
Replying to @John_Idol
okay, but on the server we don’t have 10 new frameworks a year and a huge build chain that constantly changes
5 replies 0 retweets 41 likes -
Replying to @Pinboard
I agree, but you can't stop people from making tools to their life easier the same way you can't stop people from adopting these framework.
1 reply 0 retweets 10 likes -
Replying to @John_Idol @Pinboard
I think the "constant change" is given from the fact that we are in a transitional/evolutionary phase. In few years I think it will settle.
2 replies 0 retweets 14 likes -
Replying to @John_Idol
so is it fair to say you think the situation is due to rapid change in the web, and moving complexity from backend to front?
1 reply 0 retweets 10 likes -
Replying to @Pinboard
Yes, pretty much. But "rapid change in the web" for me means rapid evolution of the tool-chain to make people lives easier.
2 replies 0 retweets 5 likes -
-
Replying to @Pinboard
Mine is in some ways, i.e. dependency management in js is a nightmare comparable to "dll hell" without some of these tools.
1 reply 0 retweets 6 likes -
Replying to @John_Idol @Pinboard
Or even modularisation of components etc is really hard to achieve in vanilla javascript. There's a reason why this stuff gets adopted!
2 replies 0 retweets 8 likes
thanks for this perspective!
-
-
-
Replying to @John_Idol @Pinboard
AFAICT I can get a multimodule build (npm+lerna) or one that might be reproducible (yarn) but not both. Really? Give me gradle back!
1 reply 0 retweets 0 likes - Show replies
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.
