Linked by bcavally on Mon 21st Dec 2009 17:18 UTC
Thread beginning with comment 400623
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Legacy architecture == bad?
by cycoj on Tue 22nd Dec 2009 01:14
in reply to "RE: Legacy architecture == bad?"
It's not so much that they weren't smart, but that there is 40 years of baggage to bog it down, with confusing layered complexity. That makes certain kinds of features take more man-hours than they otherwise could, and as such, often requires large groups to get along, which they may not do.
Can you give examples? What you write is so generic that I really don't understand what you're talking about. What are the confusing layers of complexity?
Also you could make the same argument about the C programming language, but it is arguably less complex than most e.g. C++ or C# or others. And it is still the language of choice if performance is important so 40 years can't have bogged it down too much.
RE[3]: Legacy architecture == bad?
by leavengood on Tue 22nd Dec 2009 01:25
in reply to "RE[2]: Legacy architecture == bad?"
Can you give examples? What you write is so generic that I really don't understand what you're talking about. What are the confusing layers of complexity?
X for example is a piece of crap:
http://www.art.net/~hopkins/Don/unix-haters/x-windows/disaster.html
All the Unix-like OSes just need to drop X like a hot potato. It is dragging them down and the flaws are so ingrained as to be unfixable. Even the X.org developers think it is a piece of crap. The hoops they have to go through to make it modern are pretty crazy.
Every other OS has a much better and more modern GUI system design (from Windows to Mac OS X to Haiku.)
Unfortunately the day when Linux and friends drop X probably won't ever come. Which is one reason of many I try to work on Haiku.
RE[3]: Legacy architecture == bad?
by cerbie on Tue 22nd Dec 2009 01:34
in reply to "RE[2]: Legacy architecture == bad?"
Xorg (and related cross-platform goodies), anything trying to be truly POSIX compliant, GNU C and CPP libraries, off the top of my head. Those then have libraries of their own, making great little webs of code in the shadows. There comes a point where you'd be more productive starting anew (note that I'm not saying better off, except where ALSA is concerned). In many cases, like any *n*x, that needs to be balanced against ease of portability, a large portable software base, and a history of reliable operation.
Likewise, with C as an example, just having old roots does not make something complex. C has grown with the times, and in a highly disciplined manner.





Member since:
2006-01-02
It's not so much that they weren't smart, but that there is 40 years of baggage to bog it down, with confusing layered complexity. That makes certain kinds of features take more man-hours than they otherwise could, and as such, often requires large groups to get along, which they may not do.