https://bugs.kde.org/show_bug.cgi?id=443410
--- Comment #9 from K.J. Petrie <kde.b...@kjpetrie.co.uk> --- It appear to be, but since most of the discussion has happened here I'm not sure which is the best way to merge them without risking these comments being lost from sight. I do think arguing about resources misses the point. The question is what is the purpose of a desktop? Is it to be a vehicle for its authors to write elegant code or to provide functionality to users? I can quite understand the desire to streamline code. that's always a good thing to aim for, but I would question whether that should be done in a way which deprives users of features they need, at least if it doesn't provide something of equivalent utility. If users came first, wouldn't the correct approach be to rewrite or replace functionality first so it were ready for the new streamlined code when that comes along? The approach of break it first and then see whether we can provide something similar later might be OK as a development approach, but not in released production versions. In my first-year woodworking class at school the teacher gave us the assignment of designing a toast rack. We all set to work drawing things we thought we could make which would do the job, until one boy asked the teacher "How big is a slice of bread?" The teacher congratulated him on his inside. Good design begins with purpose - identifying the required function - and that produces a specification the design needs to fulfil. You shouldn't start from what you want to make, but what it needs to be to achieve its purpose. Form follows function. It's a good principle to bear in mind. -- You are receiving this mail because: You are watching all bug changes.
