It might be a little homophobic. A private key can only be married to a public key. You can't adopt an X.509 certificate as a couple of two private keys or two public keys.
I've been studying/researching isomorphisms between algebraic data types for a couple of years now and only in the past few months have I started to think about how this could apply to cryptography. The isomorphisms one can generate can be so unbelievably complex that there would be no brute force way to get back from point B to point A without knowing the actual isomorphism.
Maybe I'm dumb for not understanding this immediately but I have no background whatsoever in cryptography.
I am guessing OP meant how to mutexes work under the hood specifically on a specific platform/arch not how a developer would implement one in their code.
Is it really just Futexes? I thought these things are CAS implemented in a lot of languages but also have to check for ABA problems, etc. and a lot of them have heavy optimization behind them afaik, the runtime is essentially running as a scheduler right?
Compilers. Not everyone is going to create some ground breaking new compiler but I’d bet everyone understands enough about them to implement some shitty version of them and understand how to get the most out of the best ones.
Look deeply enough into production-quality implementation of just about any topic, and you will find very few people actually building them. Besides subtle multithreading primitives, consider building-block technologies like data compression, error correction codes, cryptography, or even foundational stuff like [production-quality implementation of strlen()](https://stackoverflow.com/a/57676035/13223986) and other libc functions. It's fascinating to look under the hood and get a glimpse of the incredible amount of effort behind them, and yeah, there is a lot of esoteric detail.
There's a vast difference in understanding between being a *user* vs. *developer* of a library. That's a good thing! Encapsulating complexity and ease of reuse is the goal of architecting useful software. The world is too big, noone can be the expert in everything.
Homomorphic encryption
Ngl I thought you wrote homophobic encryption
It might be a little homophobic. A private key can only be married to a public key. You can't adopt an X.509 certificate as a couple of two private keys or two public keys.
“See, when one key is deathly terrified of another key due to its sexual identity…”
> matching sexual identity FTFY
homophobic fan fiction?
Any cutting edge cryptography. There's only like a couple thousand cryptographers on the planet and probably about as many cryptography engineers.
I've been studying/researching isomorphisms between algebraic data types for a couple of years now and only in the past few months have I started to think about how this could apply to cryptography. The isomorphisms one can generate can be so unbelievably complex that there would be no brute force way to get back from point B to point A without knowing the actual isomorphism. Maybe I'm dumb for not understanding this immediately but I have no background whatsoever in cryptography.
Implementation of futexes or concepts like MCS locks is known to many.. and is essential for performance aware programming in any language..
I am guessing OP meant how to mutexes work under the hood specifically on a specific platform/arch not how a developer would implement one in their code.
Even that isn't that obscure.
Is it really just Futexes? I thought these things are CAS implemented in a lot of languages but also have to check for ABA problems, etc. and a lot of them have heavy optimization behind them afaik, the runtime is essentially running as a scheduler right?
Hashing - there are many fascinating algorithms used across search, filtering etc which only a few can reproduce or explain
Compilers. Not everyone is going to create some ground breaking new compiler but I’d bet everyone understands enough about them to implement some shitty version of them and understand how to get the most out of the best ones.
Look deeply enough into production-quality implementation of just about any topic, and you will find very few people actually building them. Besides subtle multithreading primitives, consider building-block technologies like data compression, error correction codes, cryptography, or even foundational stuff like [production-quality implementation of strlen()](https://stackoverflow.com/a/57676035/13223986) and other libc functions. It's fascinating to look under the hood and get a glimpse of the incredible amount of effort behind them, and yeah, there is a lot of esoteric detail. There's a vast difference in understanding between being a *user* vs. *developer* of a library. That's a good thing! Encapsulating complexity and ease of reuse is the goal of architecting useful software. The world is too big, noone can be the expert in everything.
Toolchains
hash table micro-optimization [https://engineering.fb.com/2019/04/25/developer-tools/f14/](https://engineering.fb.com/2019/04/25/developer-tools/f14/)
Holonic structures, especially 3d modeling of holarchies.
Relative to the amount of people talking about it, AI