quarterto

they (and only they) get to still track users

Wrong. https://www.ampproject.org/docs/reference/components/ads/amp...

Wouldn't that be nice. But Google don't control how relevant or fast something is, they can only decide how to rank them.

As soon as Google stops providing value to publishers, they lose their power in the industry. For now, we work with what we have.

As somebody who has implemented AMP for a major newspaper, these are in fact things that publishers want.

Sure, speed should be a ranking factor, but I'd much rather have a slow site that's relevant than a fast one that isn't.

That is a sticking point for me. Alternative AMP caches (with alternative UX, e.g. Ampersand generally keeps users on your site when they bounce) go some way towards solving this, but they're not (yet?) first-class ecosystem citizens:

But these are just guidelines, and Google can’t guarantee they’re behaving well, so they’re not first-class citizens.

I’d love for this to be something you could statically verify, just like AMP HTML, so that anybody could add a Cache to the ecosystem and get a lightning bolt on Google search results and Cloudflare links and Twitter Moments™, but I’m pretty sure this reduces to the Halting Problem.

Can you write a carousel without JS? A live blog? Lazy loading images and ads? A stateful e-commerce product page?

Have a look through the list of AMP components, you'll be surprised what's possible. https://www.ampproject.org/docs/reference/components

Google gonna Google. They’ve been dangling carrots in front of publishers for twenty-one years.

The page is still yours. You have absolute control over the branding, the analytics, the monetisation. Just because it happens not to be served from your domain doesn't mean it's not yours.

Let's also not forget that AMP is actively encouraging alternative caches: Cloudflare Ampersand[1] was announced literally an hour after my post. It's a whitelabelled AMP cache aimed at solving this exact problem.

[1] https://www.cloudflare.com/website-optimization/ampersand/

But that's the point: AMP allows far richer pages than just totally cutting out Javascript. Like it or not, the web is an application platform.

If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?

Node has supported all of ES6 except modules since 6.0.

Post with more comments than upvotes are penalised as a proxy for controversiality (remember HN doesn't have downvotes for posts)

It's Datasette that created the site

But the charging cable can still be used for IO, as demonstrated by that new LG display

npm treats the package.json engines field as advisory, but yarn is strict about it. maybe that's you're problem

Just need to add a Math.abs: https://www.dwitter.net/d/457

I'd wager that most of LibreOffice's brand recognition is by people who are aware of the fork

Philae is the lander, not the comet.

Okay, but you made it sound like Messenger was intercepting an incoming "normal phone call".

Your friend chose to contact you via Facebook Messenger, for whatever reason. It didn't "reroute" anything. Phone calls are phone calls. If they'd actually rung you instead of using Facebook Messenger, your phone would still have rung.

It's because element queries are undecidable in the general case. A better approach is a constraint solver, which is how GSS[1] works.

[1] https://gridstylesheets.org/

Well, it has been around for about that long. The "one year" is since the stable release 1.0.

This isn't really the same thing as Refined Github though. It's just redirecting to the new Mobile Twitter. I've yet to notice a missing feature (although there are things missing that I don't consider "features", like trending topics and moments). It also works far more reliably for me: for example, try scrolling several dozen tweets down the feed in both Mobile and Desktop Twitter, clicking on a tweet, then clicking back. I've yet to see Mobile lose my place, whereas Desktop does more often than not, and when it doesn't it has to spend a minute triggering its own infinite scroll.

Developer working in large international media company here. Views not my employer's etc etc.

This looks fantastic.

It's never going to get anywhere.

Most (if not all) large newspaper CMSs are either a) large cumbersome things that have been in use for decades and are never going to be replaced because Stockholm Syndrome, or b) custom in-house-built and fit the particular editorial workflow of that organisation perfectly because the developers have taken time to listen to the journalists and implemented exactly what was needed. I don't know of any news organisation that's successfully migrated from one third-party CMS to another.

It's using Electron, so there shouldn't be much of a barrier to a Windows version (or other Linux)

Make is from 1977. GNU Make is somewhat younger.

This was explained in the original announcement thread. It'd be easy for a bunch of countries to turn round to Apple/Google and say "we don't want this app in our country", especially given the... breadth of Reddit's content. They're rolling out slowly to reduce the amount of firefighting they have to do.

https://www.reddit.com/r/announcements/comments/4dqxgt/reddi...

Well, IE8 is the most recent version that's supported on Windows XP, which is still used in a distressingly large amount of corporate environments. There's also still a load of corporate IT on Vista and 7 that won't upgrade past IE8 because reasons. IE9 and above is effectively evergreen, and Edge explicitly is, but we're gonna have a load of people stuck on IE8 for a while to come.

The answer seems to be "install it from the Ubuntu Precise repository": https://berezovskiy.me/2015/02/update-git-on-debian/