Haskell simply makes you do a thing you should do: check that the thing you expect to be there is actually there. You can think of it simply as the compiler acting as a testing framework.
On the other side there are things like TypeScript where selecting the 'n' index of an array does not give you a type representing the fact that the item may not exist, and thus does not force you the check if it does. You may call this "getting out of your way", but I don't see how this makes software less complex - it makes bugs more difficult to track down and necessitates more tests, which could simply be removed by an adjustment in types.
TyoeScript/JavaScript is easier to learn, but dear God does it offer so many ways for your to shoot yourself in then foot.
I'm with you on the "Hard disagree", but I'd say something like: one of the great rewards to being a Mathematician is that things are named after you, and you get that legacy. God knows the pay ain't great.
I thought it was kind of rude, but it depends on context. Did H.G. Wells and Joyce have a friendship, or did Wells just decide to write him a letter out of the blue? It is kind of rude to tell another person out of the blue that his book isn't worth your time, especially when said book took like 17 years to write.
Either way, I'm glad this letter exists, as it validates my priors :)
I'm a full stack engineer with lots of experience. I prefer functional programming languages, but can work with anything. I'm happy with contract work, temp-to-full-time, and full-time.
my understanding is a qubit is roughly the equivalent of a transistor, so we've got a long way to go. That said, "53-qubit" seemed like a weird number and strayed from my understanding, so take my comment as a starting point for more investigation.
"hi, I exist", said the manager who still exerts pressure on developers to work overtime with compressed project timelines and explicit and implicit pressures but pays lip service to healthy living.
