Urbit

This guy made a distributed operating system: https://github.com/urbit/urbit

Or at least, I think that's what's going on here, because he's all full of mysticism and goes on and on about traditions and instincts. Meanwhile I can't understand half a word of his sparsely documented source code. The language he made up seems to borrow all the worst parts of Befunge and APL, and even his C is kind of obfuscated. It's like trying to read a newspaper in Hmoob.

Am I just too intellectual to understand reality? Is my brain poisoned by the academic ivory tower's harmful theoretical concepts, /prog/? How can I ever unlearn the toxic ability to think?

>>20

Haskell is slow and leaks memory. GHC's inefficient stop-the-world GC does not scale. Despite being statically typed, Haskell can't deliver the bare metal speed, with typical Haskell code being 30x to 200x times slower than C/C++ (http://honza.ca/2012/10/haskell-strings http://www.mail-archive.com/haskell-cafe%40haskell.org/msg25645.html). A good understanding of evaluation order is very important for writing practical programs. People using Haskell often have no idea how evaluation affects the efficiency. It is no coincidence that Haskell programmers end up floundering around with space and time leaks that they do not understand. Functions take time to complete and debugging for time leaks is much more difficult than to debug for type errors. "The next Haskell will be strict." -- Simon Peyton-Jones