3 ms·
Okay so this actually goes straight to the heart of everything that's wrong with the web development communities obsession with PWAs. The technologies behind PW
by madeofpalk 9y ago
Okay so this actually goes straight to the heart of everything that's wrong with the web development communities obsession with PWAs. The technologies behind PWAs are fine, but people need to learn how to properly assess these buzzwords and learn if their suitable for the particular use cases of their site.
The main use case of Twitter is to look at your timeline, yet Twitter Lite somehow screwed that up and made it slower, even on subsequent loads. Not only that, the particular implementation provides arguably a worse experience, doing things like showing three different 'loaders' on the path to the timeline (Twitter icon 'splash screen' (wtf, I thought this was all preached?), spinner for the whole 'app', and then spinner for the timeline).
Reminds me a lot of people's obsession with Webpack and code-splitting - I'm sure a huge majority of projects will find >75% of their JS bundle weight being their dependencies.