Comment by ductyl on 25/01/2017 at 20:37 UTC*

74 upvotes, 2 direct replies (showing 2)

View submission: Out with 2016, in with 2017

View parent comment

EDIT: Oops, nevermind!

Replies

Comment by honestbleeps at 25/01/2017 at 20:38 UTC*

11 upvotes, 4 direct replies

I can certainly see it both ways, but the way it is worded I've had several people messaging me asking "WTF is with that?" because they interpreted it the way I interpret it (before my reply was written)...

if he meant it your way, he didn't do a good job of articulating it in my opinion...

Even if you as the RES developer are fine with them breaking RES with site improvements, there are a ton of users who would scream bloody murder if RES stopped working because of some perceived "worthless change" to the site.

they'd scream at us, though, not reddit... almost assuredly...

they've broken RES in the past and this is what happens... and we live with it as a part of the volunteer job, even if it's not fun.

Comment by lexarexasaurus at 26/01/2017 at 00:43 UTC

2 upvotes, 0 direct replies

I don't think he was blaming RES as much as he was just using it as an example of what kinds of things they've had to take into consideration with the code and be mindful of. If anything I thought it was just them saying they would rather work together with RES and the such to do it, which is good, but takes more time.