“if you really want fast rendering, nothing on the client side quite beats a server render.”adactio.com/journal/11512
Every front-end developer at Clearleft went to FFConf last Friday: me, Mark, Graham, Charlotte, and Danielle. We weren’t about to pass up the opportunity to attend a world-class dev conference right here in our home base of Brighton.
Normally FFConf would be a good opportunity to catch up with some Pauls from the Google devrel team, but because of an unfortunate scheduling clash this year, all the Pauls were at Chrome Dev Summit 2016 on the other side of the Atlantic.
I’ve been catching up on the videos from the event. There’s plenty of tech-related stuff: dev tools, web components, and plenty of talk about progressive web apps. But there was also a very, very heavy focus on performance. I don’t just mean performance at the shallow scale of file size and optimisation, but a genuine questioning of the impact of our developer workflows and tools.
He makes the point that if you really want fast rendering, nothing on the client side quite beats a server render.
Unfortunately, all too often, I hear people say that a progressive web app must be a single page app. And I am not so sure. You might not need a single page app. A single page app can end up being a lot of work and slower. There’s a lot of cargo-culting around single page apps.
Cell networks are basically kryptonite to the protocols and assumptions that the web was built on.
Today’s frameworks are mostly a sign of ignorance, or privilege, or both. The good news is that we can fix the ignorance.
adactio.com/journal/11512 cargo-culting single page apps
“Today’s frameworks are mostly a sign of ignorance, or privil… The good news is that we can fix the ignorance.”adactio.com/journal/11512
“if you really want fast rendering, nothing on the client side quite beats a server render.” adactio.com/journal/11512
“not everything needs to be a single page app” Couldn’t agree more. adactio.com/journal/11512
“He makes the point that if you really want fast rendering, nothing on the client side quite beats a server render.” adactio.com/journal/11512
“Not everything needs to be a single page app… nothing quite beats a server render” adactio.com/journal/11512
You might not need a single-page appadactio.com/journal/11512
“frameworks are (…) a sign of ignorance, or privilege, or both. The good news is (…) we can fix the ignorance.” YESSadactio.com/journal/11512
.@webrocker …or they’re a sign of “not everybody is a JS/CSS guru and they just use something ready-made to get the job done…”
so you’re using no framework? haven’t seen the talks yet but I don’t agree with this quote @patrickhlauke
afaiu boils down to ‘the right tool for the right task’ instead of blindly using $fashionableFrameWork b/c its hot @patrickhlauke
with that I agree… @patrickhlauke
but to decide if/which tool is the right one, wide + deep knowledge is needed, which excludes the ppl @patrickhlauke mentioned 1/2
2/2 which’ll lead to experts in usage of frameworkX, not in expert on working with the web, i’m afraid @patrickhlauke
experts … depends on what is to do and what is an “expert” at all @patrickhlauke
meant $expert for 140chars sake ;-) @patrickhlauke
to decide what to use you don’t need to be an “expert” but you should evaluate possible solutions. that’s all @patrickhlauke
well, if $expert and $framework are vague why this is worth discussing at all? @patrickhlauke
sure, possible for everyone, just give it a try and see if it suits @webrocker
if devs would not sometimes follow fashion we would still use the old DHTML things or maybe just plain HTML @webrocker
but now we’re talking about how to evaluate, in general, a much better topic and actually the correct, imho ;) @webrocker
“Today’s frameworks are mostly a sign of ignorance, or privilege… The good news is that we can fix the ignorance.” adactio.com/journal/11512
a great talk on SPA and web performance! adactio.com/journal/11512?…