Live data from Hacker News

Backend of Meta Threads is built with Python 3.10

twitter.com

31–40 of 458 posts

Re: Backend of Meta Threads is built with Python 3.10

#31

Ironic that a post about Threads backend is hosted on twitter.

If you want real irony here, it's this: powering an app called Threads with Python that's got a global interpreter lock which makes threading hard. Get it? Threads, threading...? OK, I'll see myself out.

I guess PEP 703 has to be auto-accepted now. I don't make the rules.

Re: Backend of Meta Threads is built with Python 3.10

#32
post #16

Ironic that a post about Threads backend is hosted on twitter.

Threads is a mobile-only app, like Instagram. You can't actually use Threads on a desktop browser, so that's probably why this is shared as a Twitter post. Even if it were a Threads post, it would not be submittable to HN.

Not exactly true. They have a read-only browser view.

In fact a Thread thread has already been on the front of HN.

https://news.ycombinator.com/item?id=36609632

Re: Backend of Meta Threads is built with Python 3.10

#33
post #16

Ironic that a post about Threads backend is hosted on twitter.

Threads is a mobile-only app, like Instagram. You can't actually use Threads on a desktop browser, so that's probably why this is shared as a Twitter post. Even if it were a Threads post, it would not be submittable to HN.

> Threads is a mobile-only app, like Instagram

Instagram can be used in a desktop browser just fine.

Re: Backend of Meta Threads is built with Python 3.10

#34
post #8

Would love to know more details about the rollout. Because it's adding well over a million new users each hour which is pretty staggering.

I would assume its massively overprovisioned at this point to cover first few weeks if not months of projected growth. But still there probably is all sorts of juicy details that would be neat to hear about

One of the "fun" things when I worked at a big company was thinking through how to make the very first launched version of something work at millions-of-users scale. There is no organic growth in traffic from zero when a non-negligible subset of billions of active users will try it out right away.

But I think on net it was still an easier problem than scaling a startup product from zero, because the tooling and processes to support huge usage is already so mature at these big companies.

Re: Backend of Meta Threads is built with Python 3.10

#35
post #24

Can we block Twitter links on HN? No point in supporting that user-hostile tire fire. This could have been on Mastodon.

It is on Mastodon as well, actually: https://mastodon.social/@ambv/110665808046065754

Could we get the mastodon link as the main link, please? Can actually view that one.

Re: Backend of Meta Threads is built with Python 3.10

#36

Earlier quoted context omitted.

A fair point about what? Threads is out for less than a day, I have 8 followers there so far. I originally posted this information on Mastodon, actually: https://mastodon.social/@ambv/110665808046065754 However, I have a much larger following on Twitter, so it was the tweet that got picked up by someone here on HN. We'll see how this looks like in twelve months.

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’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.

Re: Backend of Meta Threads is built with Python 3.10

#37
post #16

Earlier quoted context omitted.

Threads is a mobile-only app, like Instagram. You can't actually use Threads on a desktop browser, so that's probably why this is shared as a Twitter post. Even if it were a Threads post, it would not be submittable to HN.

> Threads is a mobile-only app, like Instagram Instagram can be used in a desktop browser just fine.

Let's imagine that I don't have an Instagram account because I don't. (I never really understood it because it just felt like a slightly differently flavored Facebook and I already had a Facebook account.) Up until this weekend, I could simply view a Twitter post regardless of whether I had an account. And while I've never been much of a Twitter user, I did find that useful as a lot of local news and weather type stuff would get posted and I could easily view them. Is there any analogy to that with Threads?

Re: Backend of Meta Threads is built with Python 3.10

#38
post #18
post #11

Earlier quoted context omitted.

Yet here it is ... powering a global scale app. Too weak for someones hobby project, strong enough for global scale.

My few years of personal experience of using Python with even small-ish scale professional projects have been... underwhelming so far. I wonder how Meta (and Google, and all the others who write serious Python code) manage to keep things running – and I'm not talking (only) of performance, but largely of bugs. My personal suspicion is that the secret sauce is simply to have a sufficient budget to hire an army of code…

I cannot find any substance in your comment. At minimum it should provide some rough examples instead of simply "underwhelming".

Re: Backend of Meta Threads is built with Python 3.10

#39
post #11
post #5

Always the same people that get their names in the news. I would say that the amount of tweaks that prop up Python is no cause for celebration.

Yet here it is ... powering a global scale app. Too weak for someones hobby project, strong enough for global scale.

But this is what FB/Meta are known for. They managed to scale PHP for years. They did fork it into Hack. They do have their own extensions. But they've put a ton of time and engineering effort into it. They didn't do it because they thought PHP was a great language. It was because they already had a massive infrastructure and tons of engineers that were already productive. Doing the math they realized it'd be cheaper to keep using PHP.

The same is true here. They spent so much money getting Instagram to scale. They created Cinder to try and fold their hacks/tweaks back into Python. Spinning up some Rust/Java/Nim/Zig/Pony/Whatever stack sounds like it'd be fun... but spinning up a stack with which you're already VERY familiar, sounds like a money-maker.

I'm totally agreeing btw, I realize this came off like it might be a counterpoint.

Re: Backend of Meta Threads is built with Python 3.10

#40
post #18
post #11

Earlier quoted context omitted.

Yet here it is ... powering a global scale app. Too weak for someones hobby project, strong enough for global scale.

My few years of personal experience of using Python with even small-ish scale professional projects have been... underwhelming so far. I wonder how Meta (and Google, and all the others who write serious Python code) manage to keep things running – and I'm not talking (only) of performance, but largely of bugs. My personal suspicion is that the secret sauce is simply to have a sufficient budget to hire an army of code…

You can write crap code in any language. To avoid it you need to enforce some decent set of best practices for that specific language. That also means not using best practices from language X in language Y and then complaining that language Y is crap.
Post reply on HN