No tweaks mentioned at all inside. The title is wrong. Kinda weird to start a new project that needs to scale with Python though (I use Python most of the time).
Backend of Meta Threads is built with Python 3.10
101–110 of 458 posts
Re: Backend of Meta Threads is built with Python 3.10
#102Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
Interesting and lovely to hear they decided to use Django. What is your source, though?
Re: Backend of Meta Threads is built with Python 3.10
#103Earlier quoted context omitted.
Interesting and lovely to hear they decided to use Django. What is your source, though?
How is Django now? I’m a long time python dev (data eng space) but new-ish to web dev. I started a Flask project 2 years ago and found it to be pretty full of footguns, mixed messaging on best practices for scalable apps, and the ecosystem feels overbloated with vapor ware extensions. Is this just a Flask problem, or does Django have the same issues?
If you want to purely make APIs though, give FastAPI a try.
Re: Backend of Meta Threads is built with Python 3.10
#104Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
Re: Backend of Meta Threads is built with Python 3.10
#105Earlier quoted context omitted.
Yet here it is ... powering a global scale app. Too weak for someones hobby project, strong enough for global scale.
Off-topic: it is not yet [global scale] because it is only available in US. Here in EU, I still get “not available in your country”.
It's not only available in the U.S. It's available in 100 countries. There's more to "global" than the E.U.
Re: Backend of Meta Threads is built with Python 3.10
#106Earlier quoted context omitted.
A fair point that it's stupid to implement a mostly plain text publishing site that doesn't support linking to any of the text published there. Edit: Someone kindly pointed out that you can see the content in the browser without an account from following a direct link. (You just can't have the app installed or it will open that and drop you on the login page.) This makes me a lot happier with the product!
You can link to it, what are you talking about? An example fetched from a verge article -> https://www.threads.net/t/CuVaOg1PgU4/
They just extracted Instagram comments and threw them in a sea of whitespace. No thought is given to anchoring content by importance or context, nor is there any esthetic apeal to it.
Re: Backend of Meta Threads is built with Python 3.10
#107Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
Thanks for your comment. I'm really interested in this topic. How do you know the web server is Django? I searched but couldn't find this. Why would they use Django? I did some small projects in it but I assumed it wasn't very fast and wouldn't be suitable for a big app like this. I would like to know the pros and cons. Why didn't they build up something in C++ or Rust? Won't python limit the speed of responses despi…
Re: Backend of Meta Threads is built with Python 3.10
#108Python is just the web server. All the truly performance-sensitive components--edge proxy, load balancers, backend services, databases, caches, and storage services--are mostly C++.
Re: Backend of Meta Threads is built with Python 3.10
#109Really, all the performance intensive parts are in various c++ aggregator and recommendation type services. But the webserver is Django, yes.
Interesting and lovely to hear they decided to use Django. What is your source, though?