Faceb OMEGALUL OMEGALUL k.
Rebuilding our tech stack for the new facebook.com
91–100 of 489 posts
Re: Rebuilding our tech stack for the new facebook.com
#92It uses scrolling as cookie consent, apparently.
Which is wrong as discussed here: https://news.ycombinator.com/item?id=23090393
Re: Rebuilding our tech stack for the new facebook.com
#93Earlier quoted context omitted.
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.
What makes you think React/Angular are products to increase user experience? Of course you won't find that, they are tools for developers to streamline development and make maintenance easier. Have you worked on a platform that uses nothing but pure JS and fetch calls? I have, and there's no way to make sense of a project that has to deal with so many things.
Anytime you need to stream data to or from a client, like audio/video or data. Single page apps have a much better experience.
From an architecture standpoint, it does also allow a much simpler separation of concerns.
That said, it does it get used more often that it should and can take more time to build than a multi-page app.
Re: Rebuilding our tech stack for the new facebook.com
#94Quite 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…
I guess they probably could build a nice and fast website if it was up to them. But there's probably a lot more requirements than just that. Things like https://twitter.com/wolfiechristl/status/1071473931784212480... are probably not decided on and implemented by the engineering team but are coming down as a requirement from the top. This is probably the case for a lot of other decisions that slow down the page ("We…
>Things like https://twitter.com/wolfiechristl/status/1071473931784212480.... are probably not decided on and implemented by the engineering team but are coming down as a requirement from the top.
I've always suspected that the Div-itis plaguing fb's website is a result of React's dependence on the 𝚘̶𝚟̶𝚎̶𝚛̶𝚞̶𝚜̶𝚎̶ misuse of higher order components.
Re: Rebuilding our tech stack for the new facebook.com
#95Earlier quoted context omitted.
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.
What makes you think React/Angular are products to increase user experience? Of course you won't find that, they are tools for developers to streamline development and make maintenance easier. Have you worked on a platform that uses nothing but pure JS and fetch calls? I have, and there's no way to make sense of a project that has to deal with so many things.
Humans have been using physical and mental systems to manage complexity for eons, I simply can't understand this argument. React doesn't automatically fix spaghetti code if you don't know how to organize a platform-sized code base efficiently in the first place.
Re: Rebuilding our tech stack for the new facebook.com
#96Quite 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…
Twitter's new design is pretty fast. Sure, it does a lot less than Facebook but it's using similar modern SPA tech.
Facebook is still pretty slow even on a Ryzen 3900x with 32GB of 3600mhz RAM. It's a lot better than it used to be though.
Re: Rebuilding our tech stack for the new facebook.com
#97Earlier 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.
I updated openEtG to use React instead of PixiJS. https://etg.dek.im https://github.com/serprex/openEtG
Fixed some UI bugs, made it straight forward implement features like better animations & replays, performance improved by removing stuff like a constant timer for UI & having a global mousemove handler tracking mouse coordinates
Re: Rebuilding our tech stack for the new facebook.com
#98Earlier quoted context omitted.
Comments like these remind of an old post on Slashdot, "What makes a good website?" Ask "geeks" what they prefer, it's usually minimalism, no images, consistent text styling. In the end, the ideal format becomes a text file without markup. I think we need to accept the opinions of techies are increasingly irrelevant in tech. It's like being fine artist getting paid to design flyers or a chef making burgers.
Everyone hates slow webpages. Not just geeks. We can all argue over whether minimalism or eye-candy is preferred. But if your site feels like running in mud, it's frustrating regardless of the design. And all these SPA, client-side rendered, sites seems guilty of this. You navigate to a page, and it loads up "instantly", except you see nothing but gray placeholder images. Then content starts loading in, but haphazard…
I hope we someday enter a period of reform where our field begins to apply more rigor to our process. We have the tools to make a fast, sleek web. The process is very, very broken from an engineering perspective. The money seems to never stop, which is why businesses can burn through developers without too much regard to whether they are doing the right things. Maybe that can't be fixed, because the people in charge are going to keep the status quo going if the money is coming in and they're made to look good. Optimization is a risk that companies of even modest size find to be too great.
Or perhaps people involved in a revamp/redesign/unification should be well compensated to the point where they are unlikely to leave in the middle of a multi-year project. I have a feeling based on my experience that a lot of these bad rebuilds are a result of too many engineers and designers coming and going.
Re: Rebuilding our tech stack for the new facebook.com
#99Do they still use PHP on backend. If so ick
They use Hack if you really needed to know.
Re: Rebuilding our tech stack for the new facebook.com
#100It looks a lot like the new Twitter. I guess the new trend is just to show multiple tabs from the mobile app at once as the desktop site.
I don’t get the hate for the new Twitter, to be honest. It loads fast, is simple, it’s to the point.
It's slow, requires JS, and fails around.. 50% of loads, I think?