News for hackers. Stuff that matters.
Re:Messenger.com Now 50% Converted to Reason by plausiblethrow on Saturday September 09, 2017 @08:30PM (#15209837)
How 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.
Re:Messenger.com Now 50% Converted to Reason by chenglou on Saturday September 09, 2017 @08:39PM (#15209879)
It'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.

Re:Messenger.com Now 50% Converted to Reason by PhasmaFelis on Saturday September 09, 2017 @09:15PM (#15209968)
Proving 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.
Re:Messenger.com Now 50% Converted to Reason by eecks on Saturday September 09, 2017 @08:33PM (#15209860)
What is the last part of your comment in reference to?
Re:Messenger.com Now 50% Converted to Reason by useeitherone on Saturday September 09, 2017 @08:47PM (#15209899)
Try having an issue with Google or Microsoft services and get back to me on that.