Live data from Hacker News

LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

engineering.fb.com

21–30 of 333 posts

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#21

Here's a way in which they can save 100% of the size: Stop stubbornly barring mobile clients from using the web interface. This is why I don't use Facebook Messenger at all.

But then they don't have permissions to slurp up all of your contacts, watch all of your SMS, and listen to your microphone...

I really wish iOS would allow you to select which contacts/photo album to give an app access to, instead of all hundreds/thousands of them.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#22

Here's a way in which they can save 100% of the size: Stop stubbornly barring mobile clients from using the web interface. This is why I don't use Facebook Messenger at all.

For some reason I can access the chat using Firefox Mobile on iOS but not through Safari.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#23
post #3

This seems like an incredibly low bar to hurdle. FB Messenger on iOS is legendarily bloated. In the couple of weeks I had it installed it also managed to be the biggest battery drain on my phone, even more than some 3D games.

Low bar or not, they had to rewrite the entire app to get those gains. I think it's still technically impressive.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#24
post #16

Earlier quoted context omitted.

Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...

Consider two competing apps. One looks 5% nicer but uses 1000% more memory, cpu and battery. That one will be preferred by users. And this is why things are how they are.

Looking pretty is hardly that expensive.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#25

Earlier quoted context omitted.

Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...

Have you seen how much memory and CPU time Signal uses on the Desktop? Or Slack? The era of running a chat app for almost no resources is gone unless you're an IRC holdout.

> Have you seen how much memory and CPU time Signal uses on the Desktop? Or Slack?

Aren't those using Electron?

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#26
post #25

Earlier quoted context omitted.

Have you seen how much memory and CPU time Signal uses on the Desktop? Or Slack? The era of running a chat app for almost no resources is gone unless you're an IRC holdout.

> Have you seen how much memory and CPU time Signal uses on the Desktop? Or Slack? Aren't those using Electron?

I think that's the point.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#27
post #18

Not sure how much impact this will have, most of the people I know and have discussed this with fall into two camps: people who use FB a lot an will put up with a bad mobile client, and people who don't want FB on their phone, ever. I have to go years back to think of someone who told me they just couldn't take the bad UX of the clients so they deleted it.

It's probably not meant for us, but instead the third world phones where they've gotten to the point that it might not even install on a large part of their user base.

Like I've heard from peace corps folk about how a large part of the third world thinks of messenger as "the internet", which is absolutely terrifying.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#28

Earlier quoted context omitted.

But then they don't have permissions to slurp up all of your contacts, watch all of your SMS, and listen to your microphone...

I really wish iOS would allow you to select which contacts/photo album to give an app access to, instead of all hundreds/thousands of them.

Maybe group-based, and some apps only get the selected.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#29

From: https://engineering.fb.com/data-infrastructure/messenger/ > We accomplished this by using the native OS wherever possible Does this mean this application does not use React Native?

I can't decide if seeing the pendulum swing that drastically would be hilarious to see, or not.

Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app

#30

From: https://engineering.fb.com/data-infrastructure/messenger/ > We accomplished this by using the native OS wherever possible Does this mean this application does not use React Native?

> We also embraced platform-dependent UI and associated tooling

It would seem that way.

Post reply on HN