Live data from Hacker News

Backend of Meta Threads is built with Python 3.10

twitter.com

371–380 of 458 posts

Re: Backend of Meta Threads is built with Python 3.10

#371
post #87

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

Pinterest felt especially egregious.

Re: Backend of Meta Threads is built with Python 3.10

#372

Earlier quoted context omitted.

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…

It just dawned on me that linking to Twitter is now impossible on the open web. Unless you have an account, a person can not see the linked material. This is a huge loss for the world, and makes me a bit angry. Edit: I had falsely assumed that because GP missed out on the JITing etc. described in the linked tweet, that Twitter was still inaccessible to the open web. However, trying again now, Twitter is again viewabl…

We are also in a transition period when most people and media have not realized this yet.

Yesterday, I read an article about Tour de France stage and it linked to about 4 tweets with videos which are not playable without an account.

I just hope this gets noticed by mainstream media and they change their practices instead of assuming that everyone has a Twitter account.

Re: Backend of Meta Threads is built with Python 3.10

#373

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

makes one wonder what the cost of needing bigger / more machines to make up for the slow runtime is though.

Re: Backend of Meta Threads is built with Python 3.10

#374
post #210

Earlier quoted context omitted.

Because it's not ironic. It's obvious. Twitter is just a medium to post stuff. Threads is as well. I can post this on mastodon even. Also: Europe still can't join in on the fun.

EU != Europe. Biggest country in Europe is Russia. Biggest population is Russians.

Yeah, that's up for debate. It's not as clear as you make it out to be. As a (EU) European, Russia is not. The western most part of it maybe, yeah. Same for Turkey.

Re: Backend of Meta Threads is built with Python 3.10

#375
post #221

Earlier quoted context omitted.

I think its pretty obvious they went with Instagram branding, as Facebook branding has been tarnished for a while.

I'm confused. It's Facebook by Meta. Instagram by Meta. Why isn't it Threads by Meta?

Threads by Instagram by Meta ... TIM for short.

Re: Backend of Meta Threads is built with Python 3.10

#376

Earlier quoted context omitted.

Curiously, VKontakte also started from PHP+MySQL but went another way. PHP is compiled ahead of time with something called KittenPHP. It's open-source. For databases they switched some parts to their own bespoke solutions in C that talk with PHP over the memcached protocol. These are called KittenDB (or "engines") for the simple single-purpose ones, and there was also a more generic MySQL replacement in development w…

I’m not sure why someone of facebook’s scale would want JIT instead of AOT. That’s a lot of servers all JITing the same thing that could be done once at build time.

Because they first tried to AOT, and a 2nd project with a JIT managed to get better performance out of it, with improved development workflow.

Re: Backend of Meta Threads is built with Python 3.10

#377
post #186

Earlier quoted context omitted.

It wouldn't. Databases are fast, python is slow.

Network is slow. So you are waiting on the db for most of a request lifecycle.

That depends on how much work is done in stored procedures instead of wasting network traffic and client CPU cycles to process the results.

Re: Backend of Meta Threads is built with Python 3.10

#378
post #156

Earlier 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?

I can't give Django enough praise. I never thought I'd be writing Python. I've mostly used Node, Java, and Rust, with about 12yrs experience now. Only about one year with Python and Django recently. I am so much more productive than anything else I've tried. Using anything else feels like a mistake for web apps or CRUD apis. I also use type hints. I use Django + django-ninja + django-unicorn for dynamic UIs. Building…

Is django-unicorn similar to htmx?

Re: Backend of Meta Threads is built with Python 3.10

#379
post #312

> 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. So not entirely just python 3.1.

Mind that Python 3.10 is nine major versions ahead of 3.1

Good point 3.10 != 3.1

Re: Backend of Meta Threads is built with Python 3.10

#380

Earlier quoted context omitted.

>True, but it's the best ORM currently available for any language. Better than Entity Framework? Consider me impressed.

Depending on what you consider important, and I haven't used Entity since... 2010 I think. For me, those two doesn't compare, the simplicity of the Django ORM makes Entity look dated, complex, like something out of the mainframe era. Entity is way more flexible, in the sense that you can use in any .Net project really. The Django ORM have no value outside Django, I have yet to anyone use just the ORM, without the res…

Early EF was GUI based complex one. Recent version is fine after they support "Code-first" API.
Post reply on HN