6 ms·
Over the last 8 months or so I've found Messenger.com get slower and less stable. Killing browsers or tab processes, or having to refresh the page because it's
by danpalmer 9y ago
Over the last 8 months or so I've found Messenger.com get slower and less stable. Killing browsers or tab processes, or having to refresh the page because it's become unresponsive, has become more and more common.
This could well be completely unrelated, but it has been one of the driving factors to me moving more to WhatsApp's web interface.
- dawnerd 9y agoGlad I'm not the only one. For a messaging app it does the whole messaging part pretty poorly. Typing often becomes very laggy. And this is on a fully loaded MBP. I have a feeling it has to do with rich links. Noticed that chats with a lot of them over time become harder to use.
- eggs_and_avo 9y agoYou're correct. It performs terribly. On my 2016 macbook it takes 20.48 seconds just to load the interface from refresh according to Firefox devtools. Yes, a lot of this is network traffic. It's still terrible for a chat app. I have PS4 games that start in 20 seconds.
- RandomInteger4 9y agoThis is weird. I was skeptical at first, because I could have swore it wasn't this inefficient, but then I just went there and experienced similar results on a 2016 chromebook; 19.83 seconds. Could it be all the separate CSS files they're linking?
- chenglou 9y agoIt's unrelated. We're trying to track it down still. Sorry about that
- plausiblethrow 9y agoHow can you know something is unrelated and yet still be trying to track it down? Are you running two versions of the code, in production, where this live action comparison is possible? Because if not this response reeks of Google/Microsoft engineers who always shift the blame.
- eecks 9y agoWhat is the last part of your comment in reference to?
- useeitherone 9y agoTry having an issue with Google or Microsoft services and get back to me on that.
- chenglou 9y agoIt's not the Reason sections; if you've seen BuckleScript's output you'd know that the JS artifacts are almost like hand-written code. I've checked almost every diff. Not sure how much I can say, but the leak is somewhere in the subscriptions, which isn't in Reason. Ironically the goal is to convert that section to Reason so that refactoring can finally be done (I've left that part out of the blog post just in case). Messenger produced the grandfather of Flux; it's not the easiest thing to refactor.
- PhasmaFelis 9y agoProving that a given error isn't caused by X is a very different matter from working out what does cause it, and even after that, fixing it is another matter again.
- deleted 9y ago[deleted]
- foota 9y agoI'm sorry you have such a painful bug, that must be frustrating. Here's hoping you get it soon :)
- danpalmer 9y agoThat’s great to hear, and glad the team is working on it! Thanks!
- amedvednikov 9y agoTry out eul: https://eul.im https://eul.im It's a native desktop client for Skype, Slack, Facebook, WhatsApp and many others. It's only 4 MB, it has minimal CPU usage, and it can handle hundreds of thousands of messages without lag. Facebook support is coming tomorrow, WhatsApp is going to be supported next week.
- linkmotif 9y agoThank you for sharing. Do these services care that your app lets the user side-step their apps?
- throwaway613834 9y ago+1 to this. I'm worried he'll get shut down with a cease-and-desist letter.
- mnsc 9y agoI won't even try this since I'm certain he'll get shut down with a cease-and-desist letter.
- ComputerGuru 9y agoInteresting find. It opens an embedded browser window to OAth with Slack, but after that closes nothing happens to the main window (i.e. the account never gets added). Incredible how it has a seemingly from-scratch cross-platform UI without framework bloat; but it doesn't seem to work...
- amedvednikov 9y agoIt should work. Right now there can be a ~10 second delay for very large Slack teams. If you still get nothing after 10 seconds, could you please submit a bug report via the built-in '?' form? If it's a public team, please include the URL. Thanks
- 9y ago
- rocky1138 9y agoI really wish it didn't have any sort of logic around checking the user agent. I often spoof mine and it's annoying when messenger.com doesn't load because of it.
- spicyj 9y agoWhat do you spoof it to?
- rocky1138 9y agoAll sorts of crap. Since I'm on Desktop I don't select any mobile browsers. Firefox on Linux, etc.
- spicyj 9y agoWhat's your actual browser? The most common cause I can think of would be if we think you have a newer browser than you do and serve you too-new code as a result. If that's the case, using an older version in the string might help.
- marksomnian 9y agoIs there a reason you guys are doing UA sniffing instead of a Modernizr-esque strategy? Would it have too much of a runtime cost? Or is it just about syntax and serving a transpiled blob would make it bigger? Genuinely curious
- spicyj 9y agoWe do this both for polyfills and for different compiled code in some cases. Since we need this on the first request (and care about perf on that first request), it's less practical to use JS to decide. User-Agent works well in practice.
- rocky1138 9y agoChrome Version 60.0.3112.113 (Official Build) (64-bit) Windows 10