5 ms·
Given the text of that first post, it's no wonder why there's been silence. What do you even do with that? It gives no details about why whatever the new feat
by chrsig 3y ago
Given the text of that first post, it's no wonder why there's been silence. What do you even do with that?
It gives no details about why whatever the new feature is bad, or what was good about the prior behavior. It's presumptive, antagonistic, and doesn't leave any room for discussion.
It really seems like OP is hoping that dogpiling on the issue will bring about positive change.
- cloin 3y agoOP isn't trying to provide constructive feedback, just an ultimatum. https://github.com/orgs/community/discussions/66188#discussioncomment-6930439 https://github.com/orgs/community/discussions/66188#discussi...
- troupo 3y agoThe first post is exactly what people see and feel. It is the enshittification of GitHub and needs no lengthy explanations [1] [1] https://twitter.com/dmitriid/status/1700908879486345622?s=20 https://twitter.com/dmitriid/status/1700908879486345622?s=20
- WirelessGigabit 3y agoLol, finally someone else who hates relative timestamps. One year ago... What does that mean? September 11th, 2022? Or a wider range?
- troupo 3y agoIt's especially bad for the history/commit view. "We had an incident in a large repo with multiple committers, let's narrow it down to a specific commit..."
- chrsig 3y agoThe departure from precise timestamps in UIs is unpleasant. It's not just github, gitlab does it as well.
- nomilk 3y agoI also prefer precise time stamps but am okay with time_ago_in_words as long as the full time stamp is available on hoverover
- marcinzm 3y ago>It gives no details about why whatever the new feature is bad, or what was good about the prior behavior. Isn't that the job of the PMs at Github and not the users saying they don't like the new experience?
- chrsig 3y agoSure, but if you're looking to have a dialog with the corporation about it, bringing specific actionable feedback is going to be met better than petulant foot stomping. Honey vs vinegar, and all.
- beeman 3y agoThe actionable feedback is that the old option should still stay available next to the new one.
- troupo 3y agoIf the corporation cared, it wouldn't have introduced the algorithmic feed with little to no usable info in the first place.
- chrsig 3y agoIf the corporation doesn't care, why are you spending energy complaining about it? Are you hoping to enact change, or are you just complaining?
- troupo 3y agoSometimes corporations budge due to outcry (or regulations [1]). GitHub's "designers" and PMs knew exactly what they were doing and they knew exactly what would happen. They still went ahead with it. No idea why you feel the need to defend them. [1] The algorithmic feed runs afoul of upcoming EU regulations regarding this crap
- chrsig 3y ago