You can read our discussion and reasoning for this here.
Lemmy Support
Support / questions about Lemmy.
Not dense enough. I stick to old.lemmy.world even with all its bugs.
-
It's buggy. Submitting a post sometimes takes half a second, and sometimes it takes 30 seconds. Logs show a plethora of errors. The Docker container will eventually crash and restart. It's all part of the Lemmy instance admin experience.
-
No options to collapse/customize side panels.
-
UI doesn't refresh after saving settings.
-
Settings aren't sticky from page to page on occasion.
If I could code I'd pitch in and help. Heck, I'd learn, but the documentation is pretty sparse.
1 I have never seen. The backend was incredibly buggy in 0.18 and early 0.19 versions. Maybe the frontend was too? I've only been running it for a short time but I've never seen it crash yet.
2/3/4 I count as polish things. Yes, they're not ideal. How is a rewrite into a new core supposed to make that better, as opposed to throwing the maturity level back to square 1 and introducing a whole plethora of new little polish things to worry about in addition to those?
I'm not saying you're wrong. Maybe about 1 in the present-day codebase. I definitely see things that could be improved and this is a good list of items, but what I'm asking about was the decision to abandon the codebase and start fresh specifically.
There's some personal preferences at play here. I enjoy the Lemmy UI as well, even on mobile, but I've heard people who vastly prefer other front ends or mobile apps
About the rewrite, there was some debate at the time, I'm curious to see what the rewrite will look like