Live data from Hacker News

Python at Netflix

medium.com

161–170 of 250 posts

Re: Python at Netflix

#161
post #32
post #24

Wasn't Netflix a Node.JS shop two years ago when Node was popular and now when Python is the most popular they are a Python shop ? :P (sarcasm) It's good to use many languages as it favors a micro-service architecture.

Is Python the most popular language now? I'm not trying to argue, I'm trying to see how out-of-the-loop I am nowadays.

Python has seen an increase because most ML is done in Python and ML is a popular topic right now.

"most popular" is hard to measure or even define.

Re: Python at Netflix

#162
post #92

Earlier quoted context omitted.

C is weakly typed. Python is strongly typed. That's orthogonal to 'having types'.

There is no agreed-upon definition of weakly and strongly typed; It is a nonsense word. Any Haskell programmer would laugh at someone who calls Python strongly typed.

> There is no agreed-upon definition of weakly and strongly typed; It is a nonsense word.

Sure there is. Strong typing means a language doesn't permit implicit type coercions.

> Any Haskell programmer would laugh at someone who calls Python strongly typed.

I'm sure lots of programmers are not particularly educated on the topic; it doesn't mean the word is 'nonsense'.

Re: Python at Netflix

#163

Earlier quoted context omitted.

The only way to get hired at competitive companies is via referral - if you live in the Bay Area you probably know someone or know someone who knows someone at Netflix. Trying any other way is a lottery - and if you didn’t go to MIT/Stanford/CalTech/Harvard then your odds are pretty bad. The other way is already working at a famous company and having another famous company send you a recruitment email via linked in,…

I was not hired via referral. They reached out because they were using a node module I had written. Not sure how common that is, but tbh I think any general characterization of the hiring practices of such a large org is bound to be wrong in many ways.

That’s great, I’d put that in the lottery category.

I was also not hired by referral, but got lucky they liked my resume in some resume book at RPI.

For the places I applied online my interview response rate from companies was poor (or an instant rejection).

Re: Python at Netflix

#164

Earlier quoted context omitted.

Question: If they would be, don't you think Netflix would go that route? "Better" is contextually dependent. There's no silver bullet to anything we do in tech.

> don't you think Netflix would go that route? Not necessarily. Python has a few huge advantages that aren't (directly) related to the quality or utility of the language. For example, hiring and training people to use Python is going to be easier and cheaper than hiring and training people to use C++. Additionally, as mentioned in the article, Python has a massive and healthy ecosystem of high quality packages. And t…

You're supporting the parent's point that it's contextually dependant.

Re: Python at Netflix

#165
post #111

I fail to understand the use of python in a distributed environment while the language has such poor concurrency support (on top of the lack of a type system). You can make your application HA, but they are obviously not trying to squeeze out every CPU cycle.

> I fail to understand the use of python in a distributed environment while the language has such poor concurrency support (on top of the lack of a type system). You can make your application HA, but they are obviously not trying to squeeze out every CPU cycle.

You're conflating several things that are orthogonal imo. A system can be distributed without concurrency. A concurrent system need not be distributed. Either kind of thing can be built with or without a specific kind of type system. And CPU efficiency has nothing to do specifically with any of the previous things.

To expand on that: distributed systems are quite often constructed from simple single-threaded processes, and where concurrency is needed it is probably more often achieved through multi-processing than multi-threading. A single-threaded event-dispatched request-response service probably describes a big chunk of all the stuff running in distributed environments today. In a lot of these cases the workloads are i/o bound, and instructions per cycle is not even close to the top of the list of concerns. There are a lot of reasons why python fits into that world very well.

Re: Python at Netflix

#166

Earlier quoted context omitted.

Their job site is a big /dev/null however. I spent several years dutifully submitting for numerous jobs with twenty years experience in internet and VFX in Hollywood and didn't even get an "other direction" form-letter for my trouble. (They don't date their posts so you have no idea which are active.) Netflix is in biking distance, but instead I work for a company on the east coast, 4000km away, waking at the crack o…

The only way to get hired at competitive companies is via referral - if you live in the Bay Area you probably know someone or know someone who knows someone at Netflix. Trying any other way is a lottery - and if you didn’t go to MIT/Stanford/CalTech/Harvard then your odds are pretty bad. The other way is already working at a famous company and having another famous company send you a recruitment email via linked in,…

Thanks for saying this. This is so clearly observable that I'm surprised people still don't realize that's simply The Way the World Works

Re: Python at Netflix

#167
post #111

I fail to understand the use of python in a distributed environment while the language has such poor concurrency support (on top of the lack of a type system). You can make your application HA, but they are obviously not trying to squeeze out every CPU cycle.

> I fail to understand the use of python in a distributed environment while the language has such poor concurrency support Because it's a distributed environment probably is exactly why. Python has (arguably) great concurrency support apart from Multi-threading. https://www.youtube.com/watch?v=MCs5OvhV9S4 So if you need concurrency in the context of a single thread, then Python's GIL is a non-starter. But a distribut…

Even if your app is IO bound, Python's concurrency is painful. Because it's not statically typed, it's too easy to forget an `await` (causing your program to get a Promise[Foo] when you meant to get a Foo) or to overburden your event loop and such things are difficult to debug (we've had several production outages because of these class of bugs). Never mind the papercuts that come about from dealing with the sync/async dichotomy.

Re: Python at Netflix

#168

Earlier quoted context omitted.

> I fail to understand the use of python in a distributed environment while the language has such poor concurrency support Because it's a distributed environment probably is exactly why. Python has (arguably) great concurrency support apart from Multi-threading. https://www.youtube.com/watch?v=MCs5OvhV9S4 So if you need concurrency in the context of a single thread, then Python's GIL is a non-starter. But a distribut…

If you’re doing (data analysis|simulations|Image processing) you can offload computation to numpy, which releases the GIL. This allows nice multicore speedups with python and threading. The same holds for various CPU intensive standard library functions implemented in C. The GIL issue is real, but posts like this one confused me for years. Please, don’t exaggerate GIL issues.

Not everything is amenable to numpy and it's pretty easy to make performance worse by throwing numpy at every problem. For example, if your array contains Python objects that are part of an operation, you've likely just introduced a significant performance regression. Worse, there's no way to detect these regressions except to have performance tests. Please, don't understate GIL issues.

Re: Python at Netflix

#169
post #84

Earlier quoted context omitted.

Probably whoever made it just preferred Flask. django-rest-framework is nice because it's maintained well and it's consistent with the rest of Django, but plenty of people just prefer the Flask way of doing things, even if it's a scrappier set of tools in some ways.

I'm using DRF in a project and don't really like the code/magic I end up with. IIRC I was happier with Flask and SQL... (But of course, for the bits that maps properly into its model, DRF its awesome)

Yeah. You can always get into what you do/don't like about a framework, but the same can be said of Flask.

FWIW, I don't like DRF's reliance on serializers that do more than serialization.

Re: Python at Netflix

#170

Earlier quoted context omitted.

Important to you, not to me.

Least important. Now that I think of it, I've seen some of your passive-aggressive replies here before. Perhaps a maturation phase is needed before applying to notable companies, now that you've shown yourself as difficult to communicate with in a public forum. My intent wasn't to offend, rather set expectations for would-be applicants. Of course, things could be entirely different in Paris vs. Hollywood, so grain of…

Your comment is very arrogant in itself, also I'm mature enough to not type those kind of comments with my real identity, or police myself at work. HN is merely a fun forum, not a career.
Post reply on HN