Why Netflix is embracing Python over Java

Post by eranation » Wed, Apr 08, 2015, 2:24 AM UTC

saryant wrote: post #7

eranation wrote: post #2

I agree that batteries (not) included is a big issue for Java. Yes, the batteries usually come in form of Apache Commons something (or Guava etc...) but I certainly understand why for some tasks Python is still chosen. (to get apache commons, you need to either donwload the jar, or figure out a maven project and setup XML that pulls that version, versus having it already in the core lib or if not, I assume, some "pip…

Scala is very much a there's-more-than-one-way-to-do-it language, which is why there's no official JSON library or HTTP client. Moreover, most of the big support behind Scala comes from the Java world where you're expected to pull these things in with your framework rather than from the stdlib. Using Play? You've got a JSON processor and HTTP client right there. Spray provided the same. So did Lift. Why provide the b…

Post by saryant » Wed, Apr 08, 2015, 2:29 AM UTC

eranation wrote: post #11

saryant wrote: post #7

Earlier quoted context omitted.

Scala is very much a there's-more-than-one-way-to-do-it language, which is why there's no official JSON library or HTTP client. Moreover, most of the big support behind Scala comes from the Java world where you're expected to pull these things in with your framework rather than from the stdlib. Using Play? You've got a JSON processor and HTTP client right there. Spray provided the same. So did Lift. Why provide the b…

Thanks. Yes, forgot about Rapture. It seems a little lacking on the docs side, but this is exactly the direction I'm looking for. Liked your talk on Akka by the way...