quarterto

10 ms·

1.
by quarterto 10y ago
> they (and only they) get to still track users Wrong. https://www.ampproject.org/docs/reference/components/ads/amp...
2.
by quarterto 10y ago
Wouldn't that be nice. But Google don't control how relevant or fast something is, they can only decide how to rank them.
3.
by quarterto 10y ago
As soon as Google stops providing value to publishers, they lose their power in the industry. For now, we work with what we have.
4.
by quarterto 10y ago
As somebody who has implemented AMP for a major newspaper, these are in fact things that publishers want.
5.
by quarterto 10y ago
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.
6.
by quarterto 10y ago
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:
7.
by quarterto 10y ago
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.ampproj
8.
by quarterto 10y ago
> Google gonna Google. They’ve been dangling carrots in front of publishers for twenty-one years.
9.
by quarterto 10y ago
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 a
10.
by quarterto 10y ago
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.
11.
by quarterto 10y ago
If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?
12.
You Don't Get AMP(blog.153.io)
10 points by quarterto 10y ago|34 comments
13.
by quarterto 10y ago
Node has supported all of ES6 except modules since 6.0.
14.
by quarterto 10y ago
Post with more comments than upvotes are penalised as a proxy for controversiality (remember HN doesn't have downvotes for posts)
15.
by quarterto 10y ago
It's Datasette that created the site
16.
by quarterto 10y ago
But the charging cable can still be used for IO, as demonstrated by that new LG display
17.
by quarterto 10y ago
npm treats the package.json engines field as advisory, but yarn is strict about it. maybe that's you're problem
18.
by quarterto 10y ago
Just need to add a Math.abs: https://www.dwitter.net/d/457
19.
by quarterto 10y ago
I'd wager that most of LibreOffice's brand recognition is by people who are aware of the fork
20.
A Crash Course in React(blog.153.io)
3 points by quarterto 10y ago|0 comments
21.
by quarterto 10y ago
Philae is the lander, not the comet.
22.
by quarterto 10y ago
Okay, but you made it sound like Messenger was intercepting an incoming "normal phone call".
23.
by quarterto 10y ago
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 s
24.
by quarterto 10y ago
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/
25.
by quarterto 10y ago
Well, it has been around for about that long. The "one year" is since the stable release 1.0.
26.
by quarterto 10y ago
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&quo
27.
by quarterto 10y ago
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 tha
28.
by quarterto 10y ago
It's using Electron, so there shouldn't be much of a barrier to a Windows version (or other Linux)
29.
by quarterto 10y ago
Make is from 1977. GNU Make is somewhat younger.
30.
by quarterto 10y ago
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&

More ›