3 ms·
That only makes AMP worse. Many publishers are already squeezed with dev resources, the last thing they need is yet another standard to support instead of putti
by manigandham 10y ago
That only makes AMP worse. Many publishers are already squeezed with dev resources, the last thing they need is yet another standard to support instead of putting that time towards the original HTML that is universally available to all users and devices.
- pdimitar 10y agoAbsolutely. You know, in a perverse way of seeing at it, I kind of feel good that Google forces AMP; they are like "Hah, you all stupid motherduckers couldn't get your own crap together for 15 years, guess it's time for you to be ruled, if you can't make use of your freedom". If you look at it that way, it makes sense. Still, maybe it's time the web development in general gets its crap together indeed. One can dream, right?
- manigandham 10y agoYes. Most often, it's a business management and priority issue than anything technical. It's far easier for developers to point to AMP limitations and just say "its just not supported" rather than try to argue against adding more cruft to the page and get overruled anyway.