4 ms·
The only reason I can think of this collaboration is so Google can take advantage of WordPress ecosystem so can force AMP down to our throats by simply ignoring
by stephen82 9y ago
The only reason I can think of this collaboration is so Google can take advantage of WordPress ecosystem so can force AMP down to our throats by simply ignoring the open letter many people addressed to a while ago.
http://ampletter.org/ http://ampletter.org/
- devmunchies 9y agoMy initial thought was that blogs tend to be funded by ads. So more blog = more ads.
- chadwilken 9y agoWhat I want to know is why more blogs aren’t don’t resort to mining crypto using their users browser. It can be light weight and less intrusive than an add and you still get paid while embracing the future.
- ocdtrekkie 9y agoIt sounds like this is the bit here. Big websites have revenue needs to switch to AMP, since Google prioritizes them in search. WordPress blogs are most of the content that doesn't need to. But if Google can push AMP down the default install path for a WordPress blog, they manage to swallow the largest segment of content they aren't currently drawing in through other means.
- underwater 9y agoAgreed. Google seem to be very siloed internally. That manifests itself in confusing narratives like pushing PWAs (web) and Instant Apps (Java) simultaneously, or supporting both Chrome OS and Android. So instead of asking how this is good for Google as a company, you have to look at whether it's good for a single project within Google. PWAs and AMP seem like the most likely candidates.