Live data from Hacker News

Rebuilding our tech stack for the new facebook.com

engineering.fb.com

101–110 of 489 posts

Re: Rebuilding our tech stack for the new facebook.com

#101

Do they still use PHP on backend. If so ick

AFAIK they use 'Hack', a language designed to be very similar to PHP.

https://hacklang.org/

PHP is a lot better than it used to be now though! It's got a bad rep but newer versions are fast and surprisingly modern-feeling.

Re: Rebuilding our tech stack for the new facebook.com

#102

Earlier quoted context omitted.

Agree whole heartedly, Facebook is a disgrace of a website and has been for years. Crazy how slow it is to load.

I think you could add Twitter and New Reddit to the list as well.

Mobile twitter website gives me an “oops, something went wrong” or “you’re doing that too much” error probably about 50% of the time I open a link to it.

Re: Rebuilding our tech stack for the new facebook.com

#103
post #12

> as little as possible I just opened FB with the cache disabled and it downloaded 5.85MB (19.76MB uncompressed). Most of it happens after the page has rendered, which is great, but that's a lot of stuff. There are 13.74MB of uncompressed JavaScript.

For reference, vscode ships as 13.3MB of uncompressed JS. (Not including builtin extensions, but that wouldn't add much)

Re: Rebuilding our tech stack for the new facebook.com

#104
post #50

Earlier quoted context omitted.

Sorry, I won’t take blame for that. Still haven’t found a use case for React/Angular or SASS/whatever. If I’m guilty of something is not recognizing the validity of those tools, as I’m sure there are. But 2MB CSS is simply inconceivable to me.

Big +1. I would be really interested to find one, only ONE, website where React/Angular was really bringing a better experience and better final product than a standard pure JS with simple Ajax system.

It sounds to me like you may have never worked in a codebase with thousands of JS files. On a major application, organizing code in vanilla JS is all but impossible. I agree it's better for a very small case, and I agree react slows things down, but that's a worthy trade-off for having organized, legible code.

Re: Rebuilding our tech stack for the new facebook.com

#105

Quite sincerely, it's a total failure. I got the chance to try the new interface, and it's so slow that it's barely usable. It's even slower than the old website, that was already painfully slow. Loading a random profile takes 8 seconds. Opening a messenger discussion takes 6 seconds. It reminds me of the new Reddit website. Facebook was more enjoyable to use 12 years ago. It's really sad that in 2020, 10k+ engineers…

All this and the chronological sort mode is still totally broken. Third post in my feed is 3 days old followed by one 2 hours. Total joke.

Re: Rebuilding our tech stack for the new facebook.com

#106
post #58

Earlier quoted context omitted.

I think you could add Twitter and New Reddit to the list as well.

In France we have a Craiglist-like website. They recently moved to ReactJS : https://www.leboncoin.fr/ The website features didn't changed in between. It's basically a pagination + a search based on radius (so DB related) + name (so DB related) + categories (so DB related). The complete website could be build in pure HTML + CSS and a bit of JS + Ajax to refresh parts of it. But no, it's build with ReactJS, and it tak…

> And we should really go back and stop using those frameworks

I think you are cherry picking.

There are plenty of examples in the modern web of terrible React/etc implementations but that doesn't mean the approach in itself is bad.

Re: Rebuilding our tech stack for the new facebook.com

#109
post #58

Earlier quoted context omitted.

In France we have a Craiglist-like website. They recently moved to ReactJS : https://www.leboncoin.fr/ The website features didn't changed in between. It's basically a pagination + a search based on radius (so DB related) + name (so DB related) + categories (so DB related). The complete website could be build in pure HTML + CSS and a bit of JS + Ajax to refresh parts of it. But no, it's build with ReactJS, and it tak…

Agreed. SPAs only make sense for few websites like Trello, for most other websites plain dynamic HTML with dash of ajax here and there are much better.

You know it's possible to use any of the modern JS frameworks without SPA, right?
Post reply on HN