131–140 of 167 posts
Earlier quoted context omitted.
On a phone? Last time I tried adblocking on a phone I was super irritated by it. Some proxy setup that never quite worked and felt like it slowed everything down.
Adblock on firefox on android just works.
Earlier quoted context omitted.
This seems to be a European issue perhaps? I've never once been confused by a comma in a number. In fact, it makes them easier to read, not harder. Can you describe your experience with numbers? Are you a mathematician or in some other scientific field? Also, it seems odd to make a request like this of a (seemingly) random author on the internet. It feels similar to making a demand to change writing style. (ie, oxfor…
You must be American then because that's the American format. Different countries and languages have different format of numbers. That's one of the most common issue in internationalization. If you send a bill for a 5,000 dollars service, expect your international customers to send you back five dollars. The comma is broadly interpreted as the decimal separator.
Alternate answer : not as fast as Dan Luu website. https://danluu.com/
it's a pain to read it on desktop without reader mode. the width is just too wide.
One detail which I feel must be mentioned: if you block `ampproject.org` by default -- directly or by blocking 3rd-party javascript by default, -- you will be "punished" with a 8-second delay before the page becomes visible. This is an entirely artificial delay, implemented through an inlined style CSS animation in AMP-based pages: animation:-amp-start 8s steps(1,end) 0s 1 normal both} @keyframes -amp-start{from{visi…
Earlier quoted context omitted.
HN is seemingly incapable of rationally discussing AMP. AMP solves a very real problem, which is that our web stack is open to enormous abuse because it is sometimes too powerful for its own good. While we could make simple HTML that is as fast ( of course we can), the reality is that we don't, and many don't often for tragedy of the commons reasons. And the counter-argument that search rankings should just favor thi…
> many don't often for tragedy of the commons reasons. Google are some of the major culprits driving the creation of an unpleasant web experience loaded with tracking and advertising cruft, and now they're pushing this alternative format to supposedly fix the damage they wrought. That's why people are salty about AMP. It's an imperfect analogy, but imagine if some company had torn up the roads near your house by driv…
I despise ads, but blaming Google for the situation that we're in is seriously missing the mark.
Google wants the web to succeed, for their own selfish reasons. They don't want it to become a wasteland of zombie scripts, cryptomining, pop-overs, and abuse (which tends to be even worse on mobile, as an aside, abusers knowing that mobile users often have fewer tools). They have been pushing pro-web policies since the early days. AMP, as cynical as people can be about it, is one of those.
Earlier quoted context omitted.
> - would be implemented in a way that favours speed, not placing in search and inside Google's ecosystem How? How do you 'load' pages instantly without their search iframe hack?
Indeed. "Search iframe hack". That's basically all you need to know about their "instant loading" and "caring for speed". See, they are not really optimised for speed. They are optimised for being pre-loaded from Google's CDN in search results. Or, as OP's article says: "the incentives being placed on AMP content seem to be accomplishing exactly what you would think: they’re incentivizing AMP, not performance" Actual…
One detail which I feel must be mentioned: if you block `ampproject.org` by default -- directly or by blocking 3rd-party javascript by default, -- you will be "punished" with a 8-second delay before the page becomes visible. This is an entirely artificial delay, implemented through an inlined style CSS animation in AMP-based pages: animation:-amp-start 8s steps(1,end) 0s 1 normal both} @keyframes -amp-start{from{visi…
I'd assume that's probably done to prevent FOUC while it's waiting for the JS to load. What do you get if you override that style?
ampbyexample.com##body:style(animation: none !important;)
Earlier quoted context omitted.
Not just America uses dot as the decimal separator, see: https://en.m.wikipedia.org/wiki/File:DecimalSeparator.svg Blue uses the dot, green uses the comma. By population dot wins (since India and China use the American style).
The map is largely inaccurate. Things got very divergent in the last decades with the rise of computers. There are hard limitations in hardware and software that people have to live with. A keypad only has a dot key.
Answer: not as fast as the D lang forums. https://forum.dlang.org/
Truly impressive is https://www.gov.uk/ A government site, lightning fast, try the search! No bullshit design.
Earlier quoted context omitted.
Indeed. "Search iframe hack". That's basically all you need to know about their "instant loading" and "caring for speed". See, they are not really optimised for speed. They are optimised for being pre-loaded from Google's CDN in search results. Or, as OP's article says: "the incentives being placed on AMP content seem to be accomplishing exactly what you would think: they’re incentivizing AMP, not performance" Actual…
What's your point? Of course the user gets superior performance - you tap a link and it 'loads' instantly.
The only reason AMP is perceived to be fast/instant is because Google lies.