4 ms·
I agree on AMP, you can just pack less JS and be done with it. But AMP is REALLY about rich search results online. Google creates more interactive search resul
by androidgirl 8y ago
I agree on AMP, you can just pack less JS and be done with it. But AMP is REALLY about rich search results online.
Google creates more interactive search results for AMP pages than non-AMP versions.
As for PWA's, I'm honestly a fan, to a certain limit. I really like Gatsby.js, especially because the rendered pages work with Javascript disabled.
Django/Rails/$FRAMEWORK with Turbolinks.js is also great, for the same reason I like pwa's. If you aren't a fan of the JS ecosystem (totally fair), Turbolinks is a great way to get some ""snappyness".
- lern_too_spel 8y agoMicrodata is for rich search results. AMP is for instant (not fast, as the author mistakenly stated) loading from a search results page or content aggregator.
- androidgirl 8y agoTrue! But Google incorporates more microdata from AMP pages in Search results (as in more fields), or at the least their Rich Search Results documentation makes it out to be that way. I may be wrong, this just was my understanding from reading all the Google search guides last week.
- benbristow 8y agoNot a fan of Turbolinks really. Usually one of the things I remove in a default Rails install. Just means JavaScript stuff needs to be re-init every page load etc and means extra messing about to get stuff to work