34 ms·

"Messenger used to receive bugs reports on a daily basis; since the introduction of Reason, there have been a total of 10 bugs (that's during the whole year, no

"Messenger used to receive bugs reports on a daily basis; since the introduction of Reason, there have been a total of 10 bugs (that's during the whole year, not per week)!" That's truly amazing. Interesting how Elm is inspiring other frameworks and languages. First Redux and now Reason's error messages.

deleted 9y ago
[deleted]
Cyph0n 9y ago
Was the bug reporting tool also ported to Reason? Because it could itself be faulty... /s Sounds like an amazing accomplishment for the Messenger team.
brandonbloom 9y ago
I'm not saying that Reason doesn't deserve some of the credit, but surely some of this must be attributable to relative maturity of Messenger. Right?
- chenglou 9y ago
  (Hey Brandon!) The JS part of messenger.com bugs a lot more.
desireco42 9y ago
I had similar experience with Elm. I didn't have app like Messenger, but it takes a little longer to start, but it is rock solid and refactoring is a breeze.
kibwen 9y ago
Elm was a big inspiration for Rust's error messages as well.
_pmf_ 9y ago
Sounds like the combination of the product being mature already and the introduction of static typing that makes maintenance much more safer.
dmitriid 9y ago
It also shows how deeply "it compiles and runs without bugs, it's awesome" is ingrained into software developers. I could write a 100-page essay on all the ways the web-version of messenger fails in subtle and not so-subtle ways, and how it cannot keep the pace of development with the mobile version. The dev team hasn't received bug reports though. Must be nice.
- chenglou 9y ago
  We (objectively) haven't received (many) bug reports (on the Reason section, on the web, where Reason is). See my comment right above. We do receive a ton on the rest, plus for the server side.
  - dmitriid 9y ago
    See, you don’t even understand what I’m saying. The fact that your code doesn’t break in production doesn’t mean it’s behavior is correct. - messenger.com is a subpar experience compared to mobile - there are multiple behavior issues: — it fails to reconnect when connection is lost — it randomly fails to unfurl urls which display correctly on mobile - it may unfurl a url in one chat and not unfurl the same url in another chat - it may lose connection and not even notify about it (mobile chat updates, web chat doesn’t, reloading helps) - try searching. good luck discovering where “load previous” is hidden - it may get stuck in a scroll position displaying an old message at the bottom of the chat Shall I continue? I use messenger.com exclusively throughout the day. Your pride in “not receiving bug reports” for the Reason code doesn’t amuse me.
    - lilactown 9y ago
      Bug reports are a way to measure how well the behavior is approaching correct. You seem to not be satisfied with messenger.com's experience; valid, it seems. It's a large app with bugs. But your point is obscured by the fact that you seem to be poo-pooing one of the few ways that the development team can get feedback on what users actually experience on a day-to-day basis. chenglou is doing a bit of massaging of the numbers; the claim that there's "only been 10 bugs" isn't quite true. Their code base is 50% ReasonML and 50% JS, and in the ReasonML portion, they've only had 10 bugs - a signification reduction! But they haven't commented on how many bugs are reported in the JS side; we can probably infer that there is many more (since the implication is that there were many more bugs in the old JS code they replaced). You seem to be frustrated that the messenger.com experience is not up to par and have latched on to the idea that, since the team says they're seeing improvements since introducing ReasonML, that they think they're perfect now. I guarantee you that's not the case. It sounds like you have some very valid complaints, though, and as a daily user I bet they'd love to hear your feedback. So maybe fill out a bug report with what you just wrote? :)

deleted 9y ago

[deleted]

Cyph0n 9y ago

Was the bug reporting tool also ported to Reason? Because it could itself be faulty... /s Sounds like an amazing accomplishment for the Messenger team.

brandonbloom 9y ago

I'm not saying that Reason doesn't deserve some of the credit, but surely some of this must be attributable to relative maturity of Messenger. Right?

chenglou 9y ago
(Hey Brandon!) The JS part of messenger.com bugs a lot more.

desireco42 9y ago

I had similar experience with Elm. I didn't have app like Messenger, but it takes a little longer to start, but it is rock solid and refactoring is a breeze.

kibwen 9y ago

Elm was a big inspiration for Rust's error messages as well.

_pmf_ 9y ago

Sounds like the combination of the product being mature already and the introduction of static typing that makes maintenance much more safer.

dmitriid 9y ago

It also shows how deeply "it compiles and runs without bugs, it's awesome" is ingrained into software developers. I could write a 100-page essay on all the ways the web-version of messenger fails in subtle and not so-subtle ways, and how it cannot keep the pace of development with the mobile version. The dev team hasn't received bug reports though. Must be nice.

chenglou 9y ago
We (objectively) haven't received (many) bug reports (on the Reason section, on the web, where Reason is). See my comment right above. We do receive a ton on the rest, plus for the server side.
- dmitriid 9y ago
  See, you don’t even understand what I’m saying. The fact that your code doesn’t break in production doesn’t mean it’s behavior is correct. - messenger.com is a subpar experience compared to mobile - there are multiple behavior issues: — it fails to reconnect when connection is lost — it randomly fails to unfurl urls which display correctly on mobile - it may unfurl a url in one chat and not unfurl the same url in another chat - it may lose connection and not even notify about it (mobile chat updates, web chat doesn’t, reloading helps) - try searching. good luck discovering where “load previous” is hidden - it may get stuck in a scroll position displaying an old message at the bottom of the chat Shall I continue? I use messenger.com exclusively throughout the day. Your pride in “not receiving bug reports” for the Reason code doesn’t amuse me.
  - lilactown 9y ago
    Bug reports are a way to measure how well the behavior is approaching correct. You seem to not be satisfied with messenger.com's experience; valid, it seems. It's a large app with bugs. But your point is obscured by the fact that you seem to be poo-pooing one of the few ways that the development team can get feedback on what users actually experience on a day-to-day basis. chenglou is doing a bit of massaging of the numbers; the claim that there's "only been 10 bugs" isn't quite true. Their code base is 50% ReasonML and 50% JS, and in the ReasonML portion, they've only had 10 bugs - a signification reduction! But they haven't commented on how many bugs are reported in the JS side; we can probably infer that there is many more (since the implication is that there were many more bugs in the old JS code they replaced). You seem to be frustrated that the messenger.com experience is not up to par and have latched on to the idea that, since the team says they're seeing improvements since introducing ReasonML, that they think they're perfect now. I guarantee you that's not the case. It sounds like you have some very valid complaints, though, and as a daily user I bet they'd love to hear your feedback. So maybe fill out a bug report with what you just wrote? :)