we already collectively dislike a substantial number of 0.18+'s UI decisions, most of which are minor but are already adding up to be that much more annoying collectively. maybe we can sand some of these off with theming in the future. for now though please hang with this and petition them to merge better decisions in the future, thanks
if lemmy can’t handle us personally saying we dislike a significant number of the software-wide UI choices made by 0.18+, an upgrade that mind you we can’t go back on, i feel like that speaks to a much less healthy ecosystem than this post. in any case, they’re busy, we’re busy, and most of the fixes we want aren’t in the pipeline at all because they’re administrative in nature, not cosmetic.
Not being able to revert the change is annoying, but can’t you stage these upgrades first? Seems like a good idea to find out if the UI is going to seriously regress before deploying it to every user.
we basically did do that–almost all of the problems here jumped out after we upgraded because we were latecomers to doing so. unfortunately these are essentially one-way decisions–especially 0.17.4 to 0.18±-for both software and practical reasons. the two versions have a bunch of differences that make going back a huge headache (we tried) and our site already didn’t work with a bunch of apps by using 0.17.4, so a lot of people would have to compromise using the site on mobile if we reverted/continued to not upgrade. also all of the 0.18.1 rcs so far have catastrophic bugs which seem to make the site unusable for some people, so that’s not great! overall, that we even got it to this state without losing a bunch of user data is kind of a miracle, and we’re gonna spend most of today trying to sort out all the new problems updating caused that aren’t just cosmetic