It doesn't have Hindley-Milner type inference, but it has very strong type inference.
We will get linearity soon thanks to and as part of the Capybara[1] effort.
Refinement types are already long a reality.
The whole new effect tracking thing is based on delimited continuations.
The Unison style content addressability comes up now and then, maybe it will become a reality at some point. It's though mostly not a language thing but more a build system thing.
Scala is already great for for LLMs also for other reasons:
Why would anybody use a vibe-coded and vibe-desinged language which effectively does not exist yet instead of an established one with such features, like Scala?
> * The first and most important item is the access to hardware accelerators and hardware devices whose technical interface can only be accessed from the kernel mode / supervisor state of the processor. Such support cannot be used from user space except through AF_ALG.
> * When using user space libraries, all key material and other cryptographic sensitive parameters remains in the calling application's memory even when the application supplied the information to the library. When using AF_ALG, the key material and other sensitive parameters are handed to the kernel. The calling application now can reliably erase that information from its memory and just use the cipher handle to perform the cryptographic operations. If the application is cracked an attacker cannot obtain the key material.
> * On memory constrained systems like embedded systems, the additional memory footprint of a user space cryptographic library may be too much. As the kernel requires the kernel crypto API to be present, reusing existing code should reduce the memory footprint.
I can't judge whether this is a good justification, but there is one.
Is this the mathematician's variant of "my language is better than your language", or what does this post actually discus? Something fundamental in the philosophy underpinning things or just the way to express them?
Looks like the Chinese are, again, winning the long game.
There is simply nothing that could compete with their open models. At the same time more and more corps got "AI addicted", so they will either have to pay ridiculous amounts of money, or use the Chinese stuff.
The "quality" Apple delivers is by now a complete joke. It's going south since over a decade, and this never stopped.
It's like that because people are still buying. Even for the ridiculous prices Apple asks for.
So why would Apple actually care? They get away with this "quality", so from a business standpoint there is simply nothing that needs investments or even just attention.
It's a race to the bottom. Like everywhere else. That's simply how the system which people created works.
This "test" makes no sense. Cyan, and especially turquoise are neither blue nor green, they are a mix (similar to orange between red / yellow).
I had actually a very hard time to answer the questions, needed to overlay most of the color with some mostly white / light gray window and only squint at the color around it to decide. In the end my result was 176, which is almost the exact turning point for most people (and that even while my monitor is set to be more cold than default; but like said I had whatever my monitor shows as "white" to compare; even that "white" is likely technically slightly blue-ish).
Color perception is anyway much more influenced by contrasts then anything else. (Likely similar to acoustic tones, which are very hard to name / locate absolutely than when comparing to some reference tone.)
Besides the things mentioned in the about popup, blue is AFAIK the color we have the most receptors for. So it's imho quite "natural" that most people perceive cyan—which is technically the exact middle—as blue-ish, and of course the color left to it, turquoise, is green-ish (and as it seems, for most people, the mentioned turning point).
> GrapheneOS had to sign some sort of non-disclosure for them, in order to roll them into updates.
So doesn't this mean GrapheneOS is effectively controlled by Google now?
Also, how is keeping anything secret under NDA possible at all if you want to know what's in a security update and be actually able to build that update yourself from source?
I've liked it nevertheless for context, as augmentation to parent's post.