I hate chatbot for situations like this but I get the reasons here. That said, I was hoping to get info on how it actually performed - nothing. There is nothing to suggest there is a clear metric for success and no hint of one either.
It’s just the euphoria of building something, but zilch about impact.
> Its a common term for the USA that has no other meaning
Except, you know, the only “other” meaning of “America” is just literally the alternative name for Americas, both continents. Here is an obscure link to the description [0]. Even if you want to refer to North America, what about Mexico and Canada?
ESA is one of the largest space agencies in the world. There’s nothing opaque about calling it ESA especially in a title. We wouldn’t use initialisms if everything had to be expanded all the time.
Personally I would prefer to call it "Roscosmos/ESA connects..." than "Russia/Europe connects". It adds information for free while keeping it short, just put it in the title. ESA is more specific than Europe or EU, so why make the title more generic and opaque than needed? It tells you it's not a random team of "Europeans", it's not an amateur hacker in the backyard, or some intelligence agency.
The expansion isn't really needed when it's a "household name" in the field. If you read a title about space industry there's no need to expand or explain NASA, ESA, Roscosmos, maybe not even for ISRO or JAXA, although I can see how some of these wouldn't be the most familiar for people in the West even when they have some interest in space news.
Publishers could create efficient fast-loading web pages if they prioritized it (and a rare few do) but its just not a priority for most even though its in their best interest.
You can have ads loading on a web page, even with header bidders, if you structure it correctly. In fact you can implement an ad solution that allows for fast loading pages and better optimize your ad revenue - whether you're doing pragmatic or direct.
I know this because I've done this before. At a past employer we cleaned up their mobile version (they used the "m.example.com" format, so we could push this as a separate rogue experiment) and saw ad revenue grow by over 30% while giving readers a better, faster overall UX.
I actively monitor top publisher article pages and you can see how bad (and good) it is:
I started on this when project when I was at The New Yorker. I had just manage to convince people to give us space to do web performance optimization - and then we had to drop it quickly to work on AMP. Very frustrating.
This site was created to give developers and pms some ammunition to work on improving load speed
I would love to hear more about this “open secret” - especially the guidance on how to “mask the output” etc. because as someone who works in news/media it’s news to me.
It’s just the euphoria of building something, but zilch about impact.
reply