News for hackers. Stuff that matters.

oscrperez

Re:Ask HN: Why is Linux not a mainstream OS? on Monday September 04, 2017 @10:55AM (#15168613)
IMO, in the late 90s and early 2000s it wasn't as simple to get Linux working. There was a lot of tweaking involved and a lot of headaches to get your hardware to work properly. Device manufacturers supported Windows (and sometimes Mac), rarely Linux. Big software labels didn't see the incentive in building software for Linux, it was always for Windows and Mac. Once Ubuntu came out this situation changed, and many people began replacing Windows installs with Linux. Specially for under-powered computers that couldn't run the latest version of Windows. This, combined with the popularity of web apps helped Linux on the desktop be usable. But, at that point it was too late, the desktop can today pretty much be considered legacy and mainly used for specialized cases such as content creation and other ultra-high-performance use cases.

Once you look at the post-desktop world, Linux is mainstream. The cloud, mobile, IoT devices. Linux has very large market-share in all of these.

Re:Build command line apps using PHP 7 on Sunday September 03, 2017 @03:53PM (#15163472)
I mean, great exercise. But let's stop and think, is PHP the right tool for this job? :P
Re:The Why and How of Google AMP at Condé Nast on Thursday August 31, 2017 @02:43PM (#15142726)
AMP content does look different, even across our own brands. I'm talking about the experience of tapping on a link from Google's search results. For non-AMP content some publishers might show you an interstitial ad, or a banner ad that pushes down the content as you start reading it, some publishers don't/can't do caching correctly, can't optimize images cross resolutions, etc. It's a frustrating experience for the web, specially when you compare it to the Apple's News app for example. Let alone if you're trying to search for web content on a 2G connection...

AMP incentivizes publishers to implement behavior and functionality that results in a better and consistent experience for the Google end user, this is a fact. Sure, the incentives for the publisher often boil down to SEO and ensuring their content is discoverable on the Google platform (as mentioned in the post when we talk about visibility and discoverability).

We can discuss how ethical or unethical it is for Google to use SEO incentives in order to push publishers to deliver AMP content, but that's a different conversation. I fully believe in the open web, when compared to Apple News and Facebook Instant Articles, AMP is clearly the more open solution. Even thought AMP is not perfect, I truly believe the benefits for the end users on the Google platform are there.

Condé Nast does have full control over our content and sites. Don't forget, the majority of the traffic to our business is non-amp. Our regular sites perform really well (specially when compared with other players in our space) and we're constantly improving them. We're absolutely doing the hard work there and will continue to do so. We will also continue to distribute content to other platforms besides Google AMP whenever it makes sense.

Re:The Why and How of Google AMP at Condé Nast on Thursday August 31, 2017 @12:05PM (#15141265)
For real... Tnx!
Re:The Why and How of Google AMP at Condé Nast on Thursday August 31, 2017 @12:04PM (#15141257)
This post is not meant to be a critical piece addressing the issues people have with AMP. That's not the goal here. The goal is to show the reason why we serve AMP content and the tech behind it.

There's a lot of conspiracy theories and misunderstanding about how AMP works in the community. AMP is by no means perfect, but its dangers are greatly exaggerated. If you don't trust Google's CDN, no one is forcing you to use Google. The benefits for non-tech users (e.g. my cousin in a 3rd world country with a 2G connection) are there and are clear.

Re:The Why and How of Google AMP at Condé Nast on Wednesday August 30, 2017 @11:20PM (#15137938)
You're specifically talking about Google's AMP viewer, and your concerns are UX opinion about their UI which hopefully the AMP team will improve.

The reasoning behind consistency and experience which we talk about in the post are mainly with regards the AMP content itself. Valid AMP content (passing the AMP validator) from different publishers behaves very similar to each other. Meaning you won't have any surprises as the content loads, and it will load very quickly. The experience benefits revolve around the AMP Runtime loading advertisement and embeds on-demand without blocking the main content itself from displaying properly or causing it to re-layout as the user starts reading.

Re:The Why and How of Google AMP at Condé Nast on Wednesday August 30, 2017 @11:08PM (#15137895)
Vanity Fair launched 6/23/2016, the first brand on the Autopilot stack. Sorry if I didn't mention brands that launched AMP on Wordpress. That would have probably added confusion to readers outside the company that do not know about our Wordpress -> Autopilot migrations.