News for hackers. Stuff that matters.
Re:Rebuilding our tech stack for the new facebook.com by notyourwork on Friday May 08, 2020 @12:52PM (#23116815)
Agree whole heartedly, Facebook is a disgrace of a website and has been for years. Crazy how slow it is to load.
Re:Rebuilding our tech stack for the new facebook.com by lancesells on Friday May 08, 2020 @12:58PM (#23116882)
I think you could add Twitter and New Reddit to the list as well.
Re:Rebuilding our tech stack for the new facebook.com by edhelas on Friday May 08, 2020 @01:05PM (#23116970)
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 takes seconds to search a simple item on it.

To compare, just try the same search on the Dutch equivalent, MarktPlaats, https://www.marktplaats.nl/. The experience is way snappier, way lighter, the features are the same, and it's just HTML + CSS + a bit of JS.

We made a mistake with React/Vue/Angular. And we should really go back and stop using those frameworks.

Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @01:26PM (#23117213)
> 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 by kolanos on Friday May 08, 2020 @03:16PM (#23118362)
> 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.

If the creators of React can't get it right, then what hope is there?

Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @04:01PM (#23118833)
React is bloated and slow, but there are dozens of frameworks other than React.

https://krausest.github.io/js-framework-benchmark/current.ht...

Re:Rebuilding our tech stack for the new facebook.com by deanCommie on Friday May 08, 2020 @02:13PM (#23117727)
Please name some.
Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @04:02PM (#23118836)
Some good React alternatives?
Re:Rebuilding our tech stack for the new facebook.com by mhoad on Friday May 08, 2020 @06:35PM (#23120296)
I’ve been plying around with lit-element lately and am finding it a much simpler experience overall. Likely a lot faster as well https://youtu.be/uCHZJy2n8Qs
Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @07:44PM (#23120752)
Lit is excellent.

It's also possible to use htm with Preact for developing without a bundler if your target users support ES6.

https://github.com/developit/htm

Re:Rebuilding our tech stack for the new facebook.com by goatlover on Friday May 08, 2020 @03:22PM (#23118421)
What's the reason for redoing a website that provides the same functionality? Why use an SPA for basic website features?
Re:Rebuilding our tech stack for the new facebook.com by neop1x on Sunday May 10, 2020 @05:43AM (#23131412)
They made the same with local Czech eBay-like website https://www.aukro.cz/ . Previously it was a fast website. Transition to the webapp was painful, their filtering component was not working properly on mobile. It still takes several seconds until the initial white page switches to the rendered DOM. They lost many customers due to this painful transition. I think they fixed some of the problems (I know filtering component works ok now) but I basically stopped using it since that transition too.
Re:Rebuilding our tech stack for the new facebook.com by fbnlsr on Friday May 08, 2020 @02:40PM (#23118002)
Thank you for this post. I yell at my screen each time I have to use leboncoin.

It was super ugly, but it did the job. Now it's super ugly, but it steals my focus at every opportunity, refreshes parts of the UI I'm about to click, or has select inputs that love to play hide and seek with my cursor. It's a UX nightmare.

I must say their new payment system is nice. But boy do we have to suffer when looking for something to buy now.

Re:Rebuilding our tech stack for the new facebook.com by julosflb on Friday May 08, 2020 @01:15PM (#23117081)
Could not agree more. It is barely usable now. The exact opposite of the original spirit. A complete failure.
Re:Rebuilding our tech stack for the new facebook.com by girishso on Friday May 08, 2020 @01:13PM (#23117050)
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.
Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @01:27PM (#23117224)
You know it's possible to use any of the modern JS frameworks without SPA, right?
Re:Rebuilding our tech stack for the new facebook.com by amedvednikov on Friday May 08, 2020 @01:36PM (#23117342)
It has 96 .js scripts on a single page.
Re:Rebuilding our tech stack for the new facebook.com by pyronite on Friday May 08, 2020 @01:55PM (#23117547)
This used to be a bigger deal before HTTP/2 increased the number of concurrent requests to be virtually unlimited.

Unless I'm missing something, it's "optimal" for a site to have many split files. If their JavaScript were 1 file, a change to a single character would mean the need to re-download every bit of JavaScript. Instead, with 96 files, it would mean 95 of them are still cached client-side and only 1 is need of downloading.

Re:Rebuilding our tech stack for the new facebook.com by thomaslord on Friday May 08, 2020 @03:10PM (#23118300)
It looks to me like these scripts are asynchronously-loaded components that load only once they're needed. In this case it looks suspiciously like they're nested and each script download causes another script to be downloaded once the component renders, which would make HTTP/2 a moot point. I can even watch the requests pile up in the dev tools when they're cached, so my guess is if they dumped everything in one file (or even 10 files, just not 95) they'd get noticeably improved performance.
Re:Rebuilding our tech stack for the new facebook.com by troughway on Friday May 08, 2020 @01:13PM (#23117046)
Twitter and the new Reddit aren't in the same category. Twitter is still somewhat usable.

Reddit, on the other hand, is an absolute clusterfuck from layout and usability perspective. The choices made were not made for monetary gain, they are simply really bad design choices that for one reason or another have not been fixed.

Re:Rebuilding our tech stack for the new facebook.com by mrweasel on Friday May 08, 2020 @01:38PM (#23117360)
Aah, the Reddit redesign. I still can't use it. I check up on it once in a while, but my 7 year old MacBook Pro still don't like it. It remains slow, regardless of the number of times Reddit claims of have improved the speed.

On the phone it's even worse, a large number of subreddit now require that you use the app... unless you just go to old.reddit.com.

The point of the reddit redesign still alludes me. Sure the old design isn't mobile friendly, so I can understand that they would want to fix that. Then again they mainly use the redesign to push the app. And the new design isn't that mobile friendly anyway. Certainly not if you value battery life. Comments are now also hidden by default, which is just weird. But you have infinite scroll, which seems to be the main selling point. I'm not sure I needed that though.

Re:Rebuilding our tech stack for the new facebook.com by pier25 on Friday May 08, 2020 @01:28PM (#23117245)
Totally agree.

It's incredible that ugly old.reddit.com with RES still provides a better user experience.

Re:Rebuilding our tech stack for the new facebook.com by v7p1Qbt1im on Friday May 08, 2020 @05:11PM (#23119505)
I like the redesign actually. The default view is terrible, though. Once you start using classic or compact view it‘s usable.

Like 80% of my reddit usage is on mobile by now, though. So it doesn‘t matter that much to me.

Re:Rebuilding our tech stack for the new facebook.com by TechBro8615 on Friday May 08, 2020 @01:25PM (#23117201)
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 by ljm on Friday May 08, 2020 @02:41PM (#23118020)
I sort of tolerated New Reddit at first, until I experienced first hand their (to the user) cynical reasons for doing it. Namely: throwing mobile app prompts in your face, blocking some reddits unless you're logged in, inserting ads masquerading as proper posts...

Even then, I could cope with some of it, except that they just totally broke the experience with shitty infinite scrolling. You can't click a damn thing and hope to go back to where you left on a post. Sometimes even old.reddit.com will redirect you to the new version now.

These redesigns would suck less if they were more about being functional and not about scraping every last morsel of engagement from unwitting visitors, through whichever devious methods they can imagine.

Re:Rebuilding our tech stack for the new facebook.com by notyourwork on Friday May 08, 2020 @01:46PM (#23117445)
Yes! I use old.reddit.com and am not a twitter user so I don't have much exposure there.
Re:Rebuilding our tech stack for the new facebook.com by SilasX on Friday May 08, 2020 @07:27PM (#23120653)
Yes, in particular, for large discussions, when I get a notification about a comment I made on it, and I click to jump to that comment, it takes a while to load -- and in a way oddly proportional to the size of the discussion and frequency of the posts on that group.

I'll always see the very top post of the group, and its whole page load, and then slowly my discussion will come up and then it will scroll down to that comment; and if I do anything, that breaks the whole process.

It's like no one ever considered the concept of just loading a piece of the discussion, like reddit does.

What's more, there are all kinds of UX nightmares, like how, if I open the messenger in one Facebook tab, it opens in every tab, blotting out content I want to read.

Or how a FB livestream event will just randomly stop playing, giving me no indication that I'm lagging behind the current video -- I've done trivia nights that way and I only find out I'm behind after my team members suggest answers to questions I haven't heard yet.

Re:Rebuilding our tech stack for the new facebook.com by notyourwork on Friday May 08, 2020 @06:27PM (#23120247)
Not sure why I'm being downvoted, in what way is Facebook's performance not atrocious?