To view parent comment, click here.
To read all comments associated with this story, please click here.
It's not anachronistic, it's just one way of doing things. Either you have systems that attempt to do everything as an all-in-one solution, or you have small modular linkable programs that do one thing and do it well.
KDE more or less follows the small modular linkable programs idea- the supposed bloat seems to come from the fact that they include small modular programs for every purpose under the sun, that they distribute in large bunches. Well, that and the way that all the interconnected libraries, once loaded, take up a lot of room.
The UNIX mechanism of redirecting untyped data through pipes and massaging it as text through a number of intermediaries is anachronistic. Component-oriented development has evolved considerably on all platforms, including both Windows and KDE. Suggesting that a methodology is valid because it's "UNIX-like" (that can either mean any historical snapshot of the platform's lifetime since the '70s or it can continually change meaning as the platform evolves) is stupid, whereas justifying it based upon advantages is quite sensible. If I said component-oriented development was great because it was Windows-like, I think you'd see the obvious silliness a bit better.




Member since:
2005-06-30
Frankly who cares how "UNIX-like" something is? What matters is what's most convenient for people to actually use, not worrying about how something compares to an anachronistic snapshot of behavior.