Linked by Thom Holwerda on Sat 15th May 2010 08:49 UTC, submitted by kragil
Thread beginning with comment 424683
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 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-07-06
...throughout recent history. I think products tend to be "ruined" by the tendency to make things more complex than they need to be. At least that is my experience with software development.
Something starts out clean, simple, solid vision... then slowly morphs into some monster over a period of several years until someone says "let's do it over!" Then the cycle begins again.
Often the question "what can we do to improve our product" is thrown out there when it isn't needed... when the customers are perfectly satisfied with the current product.
I know I am getting off-topic, but the arguments above about how advanced the Amiga was vs. some near-equivalent products today just sparked that thought in my mind. Really, what innovation has there been since the 80's with the interface? With the general functionality?
Yes, hardware gets faster, rendering is prettier, but all the basic paradigms are still in place and a "computer" is still just a bunch of programs running on hardware accepting input and producing managed output.
Nothing really changes and in that sense the Amiga is still as good as anything out there today. The old uVAX I developed on was "advanced" in that sense as well.
Every OS has some unique (well, I suppose some don't) way of handling a problem that might be tackled differently by another OS. Sometimes that way might very well be OBVIOUSLY better (more streamlined, more efficient, more effective somehow) but in general there can be several ways to implement shared libraries, or file/directory management, or what-have-you, but in the end we still have shared libraries and a need for file management.
This is also why when someone tries to patent something silly like "oh I invented borders that are 3MM wide around a UI port - I call it a narrow border" (yeah I made that up but you get the idea) is just so ridiculous. And then to file suit over it. Ugh.
Sorry for the wide-ranging rant. I am going out geo-caching. Have a nice weekend!
[edit: oh, my totally missed point was that complexity does not equal innovation or even superiority... it's just more complex.]
Edited 2010-05-15 17:06 UTC