fooyc

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

Apparently the new diagram is now a rip off of another one from Atlassian: https://bsky.app/profile/vurobinut.bsky.social/post/3mf52hmw...

add_v3() is the result of induction variable simplification: https://llvm.org/doxygen/IndVarSimplify_8cpp_source.html

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

Alternative interpretation: people with larger brains tend to nap more

There is a world between using AWS and buying your own servers

If you sell stable coins for USD and make a loss, you can write it off.

I feel that the joke may be about the implementation, maybe not the whole concept.

My understanding is that people don't invest in stable coins (like you don't invest in USD when you have USD on your brokerage account).

Stable coins can be exchanged against other crypto currencies on chain. So if you are willing to trade crypto currencies, stable coins are more practical than USD.

There are also tax implications: Depending on where you live, crypto-to-crypto profits are not taxable. You will be taxed if you sell crypto currencies for USD, but not if you sell crypto currencies for a stable coin.

I love this color scheme. I’ve just replaced the yellow color with some shade of blue, and it’s perfect.

Typescript is a static type system though

The article is well written and Haskell appears to have what’s necessary to work efficiently with algebraic data types (matching and overloading).

But in the end, it’s just fancy words for union and intersection types, or am I missing something ?

PHP has optional types as well, although types are enforced when present

Pretty sure they meant immutable in that quote.

    > jo normally treats value as a literal string value, unless it begins with one of the following characters:  
    > value  action
    > @file  substitute the contents of file as-is
    > %file  substitute the contents of file in base64-encoded form
    > :file  interpret the contents of file as JSON, and substitute the result

This will be a source of bugs or security issues for any script generating json with dynamic values.

If you can read environment variables of a process, can’t you also read its memory ?

PHP has a GC since 2009 (version 5.3). Its goal is precisely to collect reference cycles.

This would work if cookies was the only way to track people. There is also localStorage, ETag (and other cache-oriendted methods), fingerprinting, owning a browser, etc.

What we need is a low that forces websites to obey the "do not track" header.

"Is this a memory safe language" should be a critical question for any external facing application, too

Cookies are not the only way to tack you.

Websites can track you with localStorage, ETag headers and other cache-based methods, etc.

Some methods don’t event require any persistence on the client side, e.g. fingerprinting.

I totally agree that this should be a browser setting.

However it’s not only about cookies: What we abusively call the cookie law and cookie popups are about tracking, and there are many ways to track you without cookies, some of which are not easily blocked by browsers.

Ideally the browsers would indicate the user’s preference via a headers (e.g. the DNT header) and websites would be constrained by law to obey that.