fooyc

Online and in-store payments will follow in 2027, as per the article

The author cites this to justify the need for Records:

> Most Java objects set every field to be private and make all fields accessible only through accessor methods for reading and writing.

> Unfortunately, there are no language enforced conventions for defining accessors; you could give the getter for foo the name getBar, and it’ll still work fine, except for the fact that it would confuse anybody trying to access bar and not `foo'.

Scala supports pattern matching on objects implementing the `unapply` method.

Is this considered harmful? Why didn’t Java follow this route?

Yes it will

WEI won’t even stop the bad bots. They will simply use "legitimate" devices.

Consider this scenario:

- Content sites implement Web Integrity API to block bots

- But they still allow Google crawlers, because Google is their source of traffic

- Google competitors are locked out

How do attesters solve this problem?

Not only adblocking, but also crawling. They want to kill competition.

How does that work? The binary format embeds variants of the same program?

Maybe JIT compilers can take profit of this immediately, since they target a single machine?

Not only Reader, but also the RSS support in Chrome and Firefox (whose Google used to be the primary source of funds). And Feedburner.

Google would do anything to make it harder for others to crawl the web. Killing RSS was part of that strategy.

News sites will implement these DRMs, but of course they will still allow Google because it is their source of traffic. Alternative search engines and good bots will be locked out.

The article mentions race conditions