Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Backend of Meta Threads is built with Python 3.10

twitter.com

Post reply on HN
Print view View original

321–330 of 458 posts

Re: Backend of Meta Threads is built with Python 3.10

#321

Post by nimithryn »

IshKebab wrote: post #277
shortrounddev2 wrote: post #143

Earlier quoted context omitted.

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

The difference between C++ and Python is not nanoseconds. And I have definitely seen projects fail due - in part - to language choice. Of course projects can succeed in almost any language but that doesn't mean the language choice is irrelevant.

Example? I'm curious

Re: Backend of Meta Threads is built with Python 3.10

#322

Post by o1y32 »

andrewstuart wrote: post #262
paulddraper wrote: post #260

Earlier quoted context omitted.

Using a compiled languages for web stuff is like using a Ferrari for a commute. It's better, but not the limiting factor.

Threads is intended to be massive scale. I’d use the analogy of a Japanese bullet train as the compiled language and a diesel train as Python. Python is my primary language along with JS but if I was building a new service for Meta I wouldn’t use either at the back end.

...and apparently Meta won't care a tiny little bit about your opinion, because they have a product that is running quite well.

Re: Backend of Meta Threads is built with Python 3.10

#323

Post by mellow-lake-day »

_fdsfs12123 wrote: post #296
thewataccount wrote: post #136

Earlier quoted context omitted.

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"…

> Use celery immediately if you have any "long lived" tasks such as email Hey, quick question from a relative newbie who is currently trying to solve this exact problem. Besides Celery, what are good options for handling long-running requests with Django? I see 3 options: - Use Celery or django Q to offload processing to worker nodes (how do you deliver results from the worker node back to the FE client?) - Use a lib…

I use celery/redis, it's perfect for my use case.

Re: Backend of Meta Threads is built with Python 3.10

#324

Post by smrtinsert »

amethyst wrote: post #212
PartiallyTyped wrote: post #195

Earlier quoted context omitted.

What exactly do you do? This sounds like a JIT/Interpreter/Language dev job. Is this correct? If so, do you have any recommendations or suggestions for someone getting their feet wet on this?

It's mostly foundational work around developer tooling and infrastructure that isn't already covered by other dedicated teams (eg, there is a dedicated Cinder team). My latest work has focused around formatting and linting, and includes open source work on µsort, our import sorter [1], and fixit, our custom linter [2] that makes it easy for teams to build and deploy their own custom lint rules with autofixes. Some of…

What do people use for the editor? Are they not all standardized on Intellij?

Re: Backend of Meta Threads is built with Python 3.10

#325

Post by zitterbewegung »

amethyst wrote: post #263
zitterbewegung wrote: post #194

Earlier quoted context omitted.

I have ported code from Cinder to CPython . The fork has some optimizations that can be easily put in CPython and Facebook is open to port features. I’m not sure if Facebook wants to continually have a fork but CPython is open to have those features merged in if they make sense.

The Cinder team's longterm goal is to upstream as much as we can, and make the rest available as pip-installable extensions that anyone could theoretically install and use on CPython. The fewer internal changes and patches we need to maintain, the faster we can adopt upstream Python releases and all of the associated performance and tooling wins.

Okay cool thanks for the clarification

Re: Backend of Meta Threads is built with Python 3.10

#326

Post by amethyst »

smrtinsert wrote: post #324
amethyst wrote: post #212

Earlier quoted context omitted.

It's mostly foundational work around developer tooling and infrastructure that isn't already covered by other dedicated teams (eg, there is a dedicated Cinder team). My latest work has focused around formatting and linting, and includes open source work on µsort, our import sorter [1], and fixit, our custom linter [2] that makes it easy for teams to build and deploy their own custom lint rules with autofixes. Some of…

What do people use for the editor? Are they not all standardized on Intellij?

Keep in mind that many/most of these tools also need to work in diff review and CI tools, not just in an editor. That said, we primarily support developers using VS Code (with internal LSP/plugins/integrations) or our internal version of Jupyter notebooks. We also have a non-negligible number of folks that prefer alternative IDEs or editors like pycharm, vim, or emacs. We try to build our tools such that they are accessible by CLI or APIs, so that they can fit into any of these systems as needed.

Re: Backend of Meta Threads is built with Python 3.10

#327

Post by caeril »

Aside: I see a ton of hype about threads.net all over HN and elsewhere, but it's still useless thus far.

It loads a javascript-driven animation of what appears to be a galaxy, any not much else. There is a QR Code at the bottom right corner that appears to be invalid.

Not sure what I'm missing. 10MM+ signups through what mechanism? There is no signup form as far as I can tell. Do they restrict full content access for linux-hosted browsers?

edit: after saving and reversing saturation, I've resolved the QR Code to https://www.threads.net/download/redirect, which only offers binary download options, and only for mobile platforms.

Where is the web interface?

Re: Backend of Meta Threads is built with Python 3.10

#328

Post by wilg »

caeril wrote: post #327

Aside: I see a ton of hype about threads.net all over HN and elsewhere, but it's still useless thus far. It loads a javascript-driven animation of what appears to be a galaxy, any not much else. There is a QR Code at the bottom right corner that appears to be invalid. Not sure what I'm missing. 10MM+ signups through what mechanism? There is no signup form as far as I can tell. Do they restrict full content access for…

There is no web interface, but they will almost certainly add one. MVP baby!

Re: Backend of Meta Threads is built with Python 3.10

#329

Post by o1y32 »

n_ary wrote: post #58
blitzar wrote: 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.

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

Anything that is available in over 100 countries is global to me.

Re: Backend of Meta Threads is built with Python 3.10

#330

Post by DoesntMatter22 »

pjmlp wrote: post #179
DoesntMatter22 wrote: post #142

Earlier quoted context omitted.

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?

Remember how Shopify is still processing hundreds of millions of transactions in Ruby on Rails without an issue currently?
Post reply on HN