Earlier quoted context omitted.
Part of why I don't advocate for CDNs when you don't need them is because I want to build robust sites that work for years untouched. For timespans over a year, anything not on your server is brittle. Oops, CDN changed its URL/didn't update their ssl ciphers/went bust and shut down completely and now {js-framework}/{css-library} is missing and my site is broken. What an unforeseeable circumstance!
That's why I like to map one of my own subdomains to the cdn service. So everything is at cdn.example.com and if I change providers, it's just a dns record change and everything is ready, even if I want to just host my own content.
AMP for email is a terrible idea
101–110 of 483 posts
Re: AMP for email is a terrible idea
#102Related reading: Against an increasingly user-hostile Web , https://www.neustadt.fr/essays/against-a-user-hostile-web/ >It all comes down a simple but very dangerous shift: the major websites of today's web are not built for the visitor, but as means of using her. Our visitor has become a data point, a customer profile, a potential lead -- a proverbial fly in the spider's web. In the guise of user-centered design, we…
I'm not 100% sure if it's a vanity metric for Google or not.
...Google does have some of the greatest statistical minds in the world, just maybe not the best product/UX minds.
KPI's can be highly misleading when it's disconnected from raw UX. It's difficult to measure user emotional experience, especially when you have a monopoly on user attention with Google Search and total product lock-in with Gmail. When users don't have alternative options analytics stats can be deceiving.
And just because a user completes X task a hundred milliseconds faster it doesn't necessarily mean the UX was better. And just because the UX was made incrementally worse doesn't mean I'm going to use Google/Gmail any less. But enough of small cuts can build up into a serious wound.
Re: AMP for email is a terrible idea
#103I don't know the technical details of what Google is planning, but if they build something that eases the pain of building cross platform HTML emails, that's a welcome innovation in my opinion. Building emails that "work" even just okay is a ridiculously hard task. Every company I've been at has made some attempt with mediocre results at best (oh, you're using _Outlook_?). I'm not holding my breath for something good…
Re: AMP for email is a terrible idea
#104Wave 2.0?
Re: AMP for email is a terrible idea
#105Some relief for frogs that make it out of the pot:
Re: AMP for email is a terrible idea
#106Related reading: Against an increasingly user-hostile Web , https://www.neustadt.fr/essays/against-a-user-hostile-web/ >It all comes down a simple but very dangerous shift: the major websites of today's web are not built for the visitor, but as means of using her. Our visitor has become a data point, a customer profile, a potential lead -- a proverbial fly in the spider's web. In the guise of user-centered design, we…
Ubiquitous banner ads, "free" 56k if you use our browser and click links, cookie bonanza, link hijacking etc... have been part of the web since day one.
Re: AMP for email is a terrible idea
#107>What Google wants to do is bridge that moat, essentially to allow applications to run inside emails, limited ones to be sure, but by definition the kind of thing that belongs on the other side of the moat. How is this bad? I do not understand the hate? If you do not like the product then move on. I can see this working well on a mobile devices, not sure how it will work on other platforms, but I'm definitely open to…
Oh, the hate is just the new version of the ASCII ribbon against HTML email...
Re: AMP for email is a terrible idea
#108Wave 2.0?
Re: AMP for email is a terrible idea
#109Re: AMP for email is a terrible idea
#110Earlier quoted context omitted.
That's why I like to map one of my own subdomains to the cdn service. So everything is at cdn.example.com and if I change providers, it's just a dns record change and everything is ready, even if I want to just host my own content.
Doesn't that kill the possibility that a visitor will already have common content cached when visiting your site for the first time? I know that's not the only reason to use a CDN, but it's a pretty big one.