We spent an enormous amount of time working on bug-fixing and polishing tasks for Plasma 6.1 this week. It was a big release, and there were some rough edges around the new edit mode. So we put qui…
I wish the team would just spent an entire year of bug fixing and refining user experience without adding new features or making big changes such as the new desktop edit mode. Don’t get me wrong, this is super exciting too, but for the complex nature of KDE it would be good if they keep a bit of focus after a major release.
I swear I think of this every time someone mentions kde should just fix bugs. I follow Nate’s blog weekly and try to keep track of any other work that is going on. 90% of any kde release is polishing, bug fixing, and refactoring or outright replacing old code that was causing issues. For some reason, people seem to consider colors changing from blue to red a new feature.
I guess you meant this as a joke, but for clarification, I meant no big changes such as new desktop edit mode. I wish the team would just focus of bug fixes and enhancements without introducing new elements or changing things up in a big way like this.
This isn’t a joke. Often times rewriting features like this will allow the code to be more streamlined and use the latest KDE library features. This is brining new features using modern and more maintable code that solves long standing issues. Fixing the old code sometimes isn’t worth the effort for a variety of reasons (based on unmaintained libraries, the original code might have been written a while ago so it’s had many revisions of fixes that necessarily complicated the code, etc.)
You misunderstand me. They can write new code and be ready when the bug hunting phase is over. The end user only gets bug fixes. Later they can backport any new feature after the phase.
I wish the team would just spent an entire year of bug fixing and refining user experience without adding new features or making big changes such as the new desktop edit mode. Don’t get me wrong, this is super exciting too, but for the complex nature of KDE it would be good if they keep a bit of focus after a major release.
It seems like a lot of the new features also fix old bugs by replacing the way they function.
well the “new desktop edit mode” was refining the user experience and fixing bugs
I swear I think of this every time someone mentions kde should just fix bugs. I follow Nate’s blog weekly and try to keep track of any other work that is going on. 90% of any kde release is polishing, bug fixing, and refactoring or outright replacing old code that was causing issues. For some reason, people seem to consider colors changing from blue to red a new feature.
I guess you meant this as a joke, but for clarification, I meant no big changes such as new desktop edit mode. I wish the team would just focus of bug fixes and enhancements without introducing new elements or changing things up in a big way like this.
This isn’t a joke. Often times rewriting features like this will allow the code to be more streamlined and use the latest KDE library features. This is brining new features using modern and more maintable code that solves long standing issues. Fixing the old code sometimes isn’t worth the effort for a variety of reasons (based on unmaintained libraries, the original code might have been written a while ago so it’s had many revisions of fixes that necessarily complicated the code, etc.)
You misunderstand me. They can write new code and be ready when the bug hunting phase is over. The end user only gets bug fixes. Later they can backport any new feature after the phase.
deleted by creator
How dare you say that. We need more options that most people will never use