|
|
scott wrote:
> Yep, even on something relatively much simpler, like the radio in a car,
> it is the software that causes the biggest headaches. We can develop
> and test the hardware usually in two or three 6 month blocks, but it
> always the software that requires *way* more time and is usually the
> reason for requested hardware changes, extra builds and delays.
Exactly. Now, ask yourself, if the software is that painful, why have
software at all? Why not implement everything in hardware?
Because it's too complicated to implement in hardware. Software may be
painful, but it's the *least* painful way of doing something like that. :-)
--
Darren New / San Diego, CA, USA (PST)
Remember the good old days, when we
used to complain about cryptography
being export-restricted?
Post a reply to this message
|
|