Earlier quoted context omitted.
Click on the link, it's linked inside.
Seems to be behind login.
Backend of Meta Threads is built with Python 3.10
171–180 of 458 posts
Re: Backend of Meta Threads is built with Python 3.10
#172Earlier quoted context omitted.
You can’t link to threads? By design? I was seriously considering trying it out, but if there’s no search engine visibility, there’s no point. Most of the searches for my real name pull up tweets. Hopefully it’s just a missing feature that will be added later. Even TikToks are linkable, and those have very little google visibility.
I think Facebook/Instagram pioneered login walls for public post content.
Pay walls have been around longer than facebook
Re: Backend of Meta Threads is built with Python 3.10
#173Earlier quoted context omitted.
You mean the company that had to create their two PHP implementations and a translator to C++, to actually scale?
They ended up compiling PHP to assembly! Facebook is a company that will go to ridiculous lengths to avoid rewrites.
Was there a separate initiative for assembly, or are you thinking about HipHop? HipHop was for C++ and got a lot of attention back when it was released.
Re: Backend of Meta Threads is built with Python 3.10
#174Earlier quoted context omitted.
You mean the company that had to create their two PHP implementations and a translator to C++, to actually scale?
Lol. Do you think you are just going to use go and everything is going to scale to FB level size? Facebook was already at a scale larger than 99.99999 percent of sites before they had HHVM
Of course not. One uses Erlang and scales to Whatsapp scale.
Re: Backend of Meta Threads is built with Python 3.10
#175For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
Quite often, the choice of language is failing to see the forest for the trees. Saving nanoseconds or cycles because you chose C++ over Python pales in comparison to milliseconds spent at network barriers reading from a cache service or database
At Facebook scale those nanoseconds are worth millions in compyte, energy, etc.
Re: Backend of Meta Threads is built with Python 3.10
#176Earlier quoted context omitted.
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?
You simply can't beat Django's ORM for general stuff. It's too awesome. This alone makes it so hard to choose anything else. I know django doesn't have that "shiny factor" to it these days - but it's very reliable. > mixed messaging on best practices for scalable apps The WSGI stuff can be kinda confusing and is used across a lot of python frameworks including django and I think flask? My advice for "simple scaling"…
Ehh, Django ORM always was one of the worst parts of Django.
Re: Backend of Meta Threads is built with Python 3.10
#177Earlier quoted context omitted.
Gotten burned by that. Have a python utility that calls something that's very CPU intensive (GDAL) and I literally have to wrap this python process in java for real concurrency. Not a python expert by any means but I'd love to know what other people do when this happens. I'm assuming it's something revolving around containers and messaging (blech)...
Is your problem that the c part of GDAL isn't concurrent and you are calling it multiple times, or are you blocking on something you shouldn't? Python calling a concurrent c thing is super common. For more complex things there is multiprocessing, but that essentially is simplification of IPC.
Had a massive amount of images that I was trying to process for a specific purpose. I wound up spinning up multiple python processes within a java wrapper using concurrent linked queues. Got the job done but it's not the proudest moment of my life.
Re: Backend of Meta Threads is built with Python 3.10
#178For the “Python isn’t fast enough for production backend” crowd from the same company that brought you the largest social network built on PHP + MySQL.
Yep, Vanilla Python isn't fast enough so they have to do more:
"It's running on Instagram's #Cinder fork that includes a JIT, lazy-loaded modules, pre-compiled static modules, and a bunch of other interesting tweaks against vanilla Python 3.10"
From the Tweet.
Personally, I don't care what language people use. We all know that if you have money, you can just throw in more servers. Until your CFO and CTO decided that the next big thing is to do "Cost Saving" (in the eye of recession).
I'm surprised in 2023 people are still debating mainstream programming language "PROD" readiness.
It's like a "cool kid" competition.
Re: Backend of Meta Threads is built with Python 3.10
#179Earlier quoted context omitted.
You mean the company that had to create their two PHP implementations and a translator to C++, to actually scale?
Lol. Do you think you are just going to use go and everything is going to scale to FB level size? Facebook was already at a scale larger than 99.99999 percent of sites before they had HHVM
Remember when Twitter was written in Ruby?
Re: Backend of Meta Threads is built with Python 3.10
#180Earlier quoted context omitted.
Asking a question is having the impression that one is in a position of authority now?
No, but appealing to 'we' is. Not that 'we' in this case has much meaning, it actually could read 'you'.
What other pronoun do you want OP to use? "Can I ban..." - well, obviously not. "Can you ban..." who is "you" in that case?