Old joke:
Every program can be (memory)optimized by at least one byte and has at least one bug in it.
It therefore follows that every program can be reduced to a single byte that doesn't work.
LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
31–40 of 333 posts
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#32Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#33Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#34how does one manage to make a chat app bloated in 2020?
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#35Earlier 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.
I wish Android/iOS would let the user decide individually on every single file/contact/etc access, at least in an optional setting.
Would be interesting to see how many seemingly harmless apps start to break, I would expect similar results to surfing the web with a JS blocker.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#36From: 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?
Wow! So the OS frameworks are there for a reason? Who would have thought?!
Mind = blown!
One can only hope that Slack and other Electron apps reach this point eventually...
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#37Earlier 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.
For photos, I wish iOS would not require a permission at all in the case where I just want it to open an OS-controlled file picker and then give the app the one photo, akin to copy-pasting it. No reason to give access to every photo when only N are picked.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#38Earlier quoted context omitted.
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.
If you know exactly how you want your app to look forever, sure. But you don't. So you want a flexible app that can easily be redesigned. And that means prioritizing developer comfort very high. Which means bloated frameworks.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#39From: 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?
Yeah, that's how I am reading that.
Given the headaches caused by Apple finally barring UIWebView (the basis of frameworks like Cordova) from new App Store submissions beginning in April, I'm not surprised FB would do this. There is plenty of rumor-mongering that Apple is going to make it increasingly difficult for apps based on hybrid frameworks through the submission process.
Re: LightSpeed: Rewriting Messenger’s codebase for a faster, smaller, simpler app
#40This 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.
Is this incompetence or aggressive data mining? I fail to see how a texting client is that complicated...
I think they went through a period (or still are, I honestly moved over to messenger lite a couple months into it) where they were seemingly intent on making messenger the WeChat of the west. It got real chunky real quick. It was around the same time everyone was excited about conversational ui and Microsoft announced their bot framework.
It may have been slow and bulky before that, but that's when I started to notice.