News for hackers. Stuff that matters.
Re:Why we switched from Python to Go by stuartaxelowen on Tuesday October 17, 2017 @10:09PM (#15496387)
For context, Instagram's primary web servers are Django.
Re:Why we switched from Python to Go by seabrookmx on Tuesday October 17, 2017 @10:33PM (#15496466)
And reddit. And a little thing called youtube (though to be fair last I read they're offloading a lot of the hot paths to golang and c via native modules).
Re:Why we switched from Python to Go by kbaker on Wednesday October 18, 2017 @01:42AM (#15497120)
Curious, where do you see that youtube is running Django? Python, maybe, but I don't think they run Django?
Re:Why we switched from Python to Go by techdragon on Wednesday October 18, 2017 @04:11AM (#15497618)
It's definitely python, but definitely not Django. I recall someone explaining to me that it actually predates WSGI standardisation so its not even WSGI its just all custom python from start to finish.
Re:Why we switched from Python to Go by seabrookmx on Saturday October 21, 2017 @09:10PM (#15524548)
My apologies, I thought OP said 'Python' not 'DJango'. You're correct. Youtube has their own framework and IIRC reddit runs a few different Pyramid modules rather than a full-fat framework.

Reddit has some scattered Engineering blogs and my insight into youtube comes from a previous HN article by the author of GrumPy (who works on youtube at Google) in case you're curious.

Re:Why we switched from Python to Go by mi100hael on Tuesday October 17, 2017 @10:21PM (#15496430)
Pinterest, too, I believe.