They tell us what we want to hear, not what is right. Public speaking, leadership, campaigning are skills like any other fortunately.

How?

Wait, what? if lambdas are shit programming why did almost every language add them as a features in the last 5-10 years? including c++.

I think you have mostly missed my point, Scala has research oriented roots, and it you're not ok with that, fine. But if it makes you a more efficient programmer, it might just be worth the effort of picking up.

Also, this is what I mean by pattern matching:
http://docs.scala-lang.org/tut...
https://doc.rust-lang.org/book...
https://developer.apple.com/li...

This isn't necessarily an argument against Scala, using it well will have it's challenges, but this is true for most languages. Linkedin went through the same.
Some of the tradeoff's Twitter has had to make have changed. They moved away from Ruby, and for Ruby developers, Scala might actually have been easier to pickup than someone who has been doing Java since 1.4. You have to unlearn more OO practices to use Scala well, but you can write very rubyish or pythonic code in Scala. If I look at a project like finagle now from twitter (compared with gRPC from google), I can sort of see Krikorian's point, but finagle is still one of the best or the best RPC libraries out there if you know Scala. As far as language features, pattern matching, expressive types with inference, var/val immutability are all huge helps to write more concise programs. There are more CS-y features like tail recursion, laziness, um.. monads (any typelevel library), which can hurt or help the complexities in your program. As the Scala community has matured, developers and the language has gotten better at using/refining these features (specializations come to mind) and a few of the good and safe features have become more widespread (swift, rust, jave 8 lambdas)

The learning curve is steep for an OO developer to use the language well, but I like what this article says about the challenges:
https://www.infoq.com/articles...
"As explained in this article all these features are already available in Scala. Developers who want to try them out can explore early builds of Java 8 on most platforms. Alternatively, we recommend taking a look at Scala as a way of preparing for the paradigm shifts to come."

also, chill

It's also possible that in such a world there is no need for simulating anything since the perfect answers can all be found through quantum computers and looking elsewhere. Why simulate us or the universe? At that point, it's equally likely that there is a creator and/or that we are in a simulation.

The extent to which a simulation can be completely divorced from the abstractions running it, (i.e. quantization and the speed at which things happen) is just asking for more energy, orders of magnitude more, if possible at all in the first place, but I am sure Godel doesn't apply either.

I just want to know what the energy source is for the large scale simulation we're in.

Not so much, it's a bit more like turning every place you can recharge your phone into a bank deposit/withdrawal counter.

A balloon shaped like a blimp. The powered part would've cost more..

..you could just turn auto sync off, unless you really need it. Auto sync should realistically only be on when charging. If I want to see new tweets or mail, I will just swipe down on the app manually for sync.

Except for the countries investing more efficiently in their infrastructure.

http://stopthecap.com/2013/12/...

Fiber is the future, this is a stop-gap at best.

Those laws do exist in some states and the FCC also voted to ignore them.

http://www.newrepublic.com/art...

Competition from cities, which can and usually do own the right of way (ie. putting fiber cable on utility poles), is what will ultimately hit AT&T, Verizon and comcast's bottom line.

InGaAs Valley has a nice ring to it too.