On Thu, 6 Jan 2000, David Schwartz wrote:
> Design obsolesence into the hardware and then blame it on the software.
> Wonderful. IMO, anything we can do to make this technique work better is
> ultimately self-destructive. If you design in just the hardware that the
> software needs today, your embedded system should break.
Well, money talks and ... you know the rest.
The writing of efficient program and the writing of clean programs are not
mutually exclusive. Of course, your attitude is what allows me and others
to get nicer margins - a lot of people design unecessarily expensive
hardware.
If you manefacture anything in larger scale the manefacturing price is
everything. Most devices are not really changed or at least their taks it
not changed. I have no interest in having my elevator control being able
to play mp3:s, I just want it to move me between floors safely.
Anyway, I am convinced there will still be a lot of older architectures in
use by 2038.
Peter
-- Peter Svensson ! Pgp key available by finger, fingerprint: <petersv@psv.nu> ! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF <petersv@df.lth.se> ! ------------------------------------------------------------------------ Remember, Luke, your source will be with you... always...- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jan 07 2000 - 21:00:07 EST