> The BASIC language eliminated much of the complexity of FORTRAN by having a single number type. This simplified the programming model and avoided a class of errors caused by selection of the wrong type. The efficiencies that could have gained from having numerous number types proved to be insignificant.
DEC64 was specifically designed to be the only number type a language uses (not saying I agree, just explaining the rationale).
> In iOS 26, controls insist on animating themselves, whether or not the user benefits. Carousel dots quietly morph into the word Search after a few seconds.
This has been the case for several years now (started in iOS 16 IIRC); it is not new in 26.
No it isn't. This line of comments is explicitly in response to your claim:
> Isn't a larger issue the number of immigrants who are NOT contributing to the economy, living at taxpayers' expense
No one has yet mentioned illegal immigrants except you.
In any case it doesn't matter, since GP was specifically replying to:
> In my experience, immigrants have low paying jobs and regularly use cash to avoid paying taxes. Most have no sense whatsoever of cohesion with the country they live in and instead make groups of similar culture that don't really try to fit in.
They were simply giving their own opposite experience on the subject of immigrant wages and taxation, which is equally as valid.
If this thread was actually about illegal immigrants, both comments would be equally off topic. I find it interesting which one you decided to respond to.
Yeah I consider that one to be a trick question. I knew same-quote-style nested f-strings were coming, I just didn't know which version, and I still use the `f'{f"{}"}'` trick because I want my code to support "older" versions of python. One of my servers is still on 3.10. 3.11 won't be EOL until 2027.
> > If after the above I created an array like so `char str[n]` and then assigned such that it pointed to the same region of memory that malloc() returned, then would the provenance of both pointer be equal?
> Yes.
Uh, no. This is flatly untrue. You cannot "assign an array such that it points to a region of memory". Arrays are not pointers, they do not point to anything.
> With Safari providing this, it can be used by some providers, but nobody can block or behave differently with unattested clients.
What mechanism prevents websites from blocking or behaving differently for unattested clients? The article doesn't make that clear.
Also: Apple's attestation implementation introduces an external real-time single-point-of-failure, but given that the failure mode is just "show a captcha", it doesn't seem too severe. Is it even possible to implement a broader attestation infrastructure without introducing a similar single point of failure? TLS PKI, for example, does not rely on an external "live" server; the private keys live on the origin.