We should rebrand REST to Rest to emphasize that the original meaning is lost and that we just use it as a shorthand for a http like API. When it comes to web it's best to set our standards as low as possible because being right doesn't seem to have any advantage over being wrong wrt adoption.
Same setup as him, I'm working on llvm. It's very nice to be able to test the compiler by running and simulating on a threadripper CX3990, means I don't have to run everything past the build server
You're confusing strong and static typing (javascript has neither). In more sophisticated languages such as scala, C# or haskell you can let the compiler infer the types for you, and you can then ask your IDE which type that is. This way you don't need to type out all the boilerplate, you get to see what a functions signature is, and you get compiler errors rather than runtime errors.
I think this is a well written post, but I'm incredibly puzzled at eschewing scalas syntax for type parameters and instead having parentheses do double duty. Other than freeing up brackets for indexing what is gained from this?
Other than that I actually think this is a language that deserves to exist so the ideas can be tried out in practice, if nothing else to influence the current OO languages to be better.