Linked by Thom Holwerda on Mon 5th Sep 2005 13:38 UTC, submitted by Erik Harrison
Permalink for comment 29194
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-06-30
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.