Re:Neither PWA nor AMP are needed to make a website load fast
by tyingq on Friday December 07, 2018 @08:39AM
(#18627517)
It also grabs a significant portion of the top of your webpage...which happens to be the reddest part of a heatmap for eyeballs.
Re:Neither PWA nor AMP are needed to make a website load fast
by dvfjsdhgfv on Friday December 07, 2018 @02:09AM
(#18625702)
> nonbiased entity (Google)
You probably meant it the other way round?
Re:Neither PWA nor AMP are needed to make a website load fast
by saagarjha on Friday December 07, 2018 @02:15AM
(#18625718)
Fixed, thanks.
Re:Neither PWA nor AMP are needed to make a website load fast
by izacus on Friday December 07, 2018 @02:49AM
(#18625843)
The web development community had plenty of time to fix these problems in better ways and it instead just spent time building bigger and bigger JS frameworks and background videos.
Re:Neither PWA nor AMP are needed to make a website load fast
by raxxorrax on Friday December 07, 2018 @07:55AM
(#18627234)
What problems exactly? The web works pretty well and the source of most problems is non-technical. AMP is cache + handcuffs. No, thanks. I am no web-developer, but pretty sure I wouldn't want to touch that. Is performance really an issue these days? It probably always is but there are worse ones. One specifically being closed web technologies administered by large companies like Google.
Re:Neither PWA nor AMP are needed to make a website load fast
by tonyarkles on Friday December 07, 2018 @08:45AM
(#18627552)
The number of times I open a news article (local/regional seems to be the worst) on my phone, start reading the article, and then 10-15 seconds later have the whole thing go blank, reflow, and start me back at the top of the page... I haven't spent any time investigating what actually causes it, whether it's a stylesheet or a big JS module or what, but it's absolutely enraging. I'm just reading what could be plain text content, and that flow gets horribly interrupted.
I'm really torn on AMP to be honest. I'm morally and technically opposed to it, but... the experience is often dramatically better than what I would have gotten without it.
* It's clearly driven by a biased entity (Google)
* It doesn't actually directly prioritize page speed
* It breaks websites