The "two language problem" in the high performance numerical computation domain, in which you have a high level language that is easy to use as a glue (such as Python) and a low level language for anything that requires performance (such as C++). In Julia a program that looks like python can run at the speed of C (and as a bonus has the metaprogramming abilities of a Lisp minus s-expressions), and with only one high level language for everything you can much more easily create, understand, extend and debug anything.
But if you really want to write something that's fast you won't write it in Python, Julia, or these days - C. You would probably use C++ (in a non-C-ish, non-OOPish way), and in some cases (think DBMSes) you'd craft your own LLVM IR and have it JITed.
Why not just use Julia + a few crafty LLVM calls to get to the same place if you want to go that deep? That's essentially what you'd be doing from C++ there.
Very few people care about the issues raised by the author. From a practical pov, I think the best way to create something like this would be from some prebuild community that might care like Burning Man or something.
Kinda an obvious post; the name dropping of schools is a bit obnoxious in my opinion esp since the current highest valued private company is run by a UCLA dropout - something Suster would obviously have loved to invest in after the fact. I find the exceptionally smart "startup" people are very knowledgable about their competition and their companies relation to them and can project out to the future.
I agree there is not a great difference in the places I am mostly (SF and LA) but I think Uber was smart to bring on a lot of cheap capital the past few years.
I could see see something like Uber electric cars / golf carts where driving distances are small such as Sun City in AZ. Baby steps. Can't have a death in an accident though.
a bit of a strange argument. Twitter's salty environment is the nature of the beast in many ways. He seems to have some idealized nature of "how it should be" vs "how it is". Also, make clear distinctions about where you feel Twitter went wrong as a business and where you just don't like it ( <- this is by far my biggest pet peeve of engineers talking about other products). Pretty pointless article.
Because people upvoted it. Also this is a relatively significant release with some important new features, e.g. redis cache support and password helpers
