Re: Disobeying jet engines - why?

"John Larkin" <jjlarkin@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4f41q3hq25ra5ld18dfa5jvlcnkge8klnc@xxxxxxxxxx
If you use state machines, and don't multitask, you don't need
semaphores. If you don't allocate resources, you can't have deadlocks.

It's simple.

Unfortuntaely the "windows" (not just Microsoft Windows, but also, e.g., X
Windows and I would guess whatever older Macs used) paradigm makes it
difficult to not fire off multiple threads for even relatively simple
applications. For instance, if your serial interface API blocks for a
specified timeout period (e.g., 15 seconds if no response from some serial
device is heard), the GUI is going to be blocked as well for those 15 seconds
and your user will at best find this behavior annoying and at worst thing your
program is broken. While you could certainly argue that the guy who wrote the
serial API to block on a read was a nut bag, you're then into the discussion
of how much of someone else's tried and tested code you want to rip up and
re-do (which may not even be possible if you're interfacing to someone else's
hardware) vs. just using what's provided and still provide a "nice" user
experience regardless of how bogged up the provided API is.

Programmers want that fancy stuff on their resumes.

....because all of the "big guys" (Microsoft, Intel, HP, etc.) are ASKING FOR
that "fancy stuff." So these days your average college grad is likely to have
been exposed to a whole potpourri of various "cool" technologies but hasn't
necessarily had time to learn any of them particularly "deeply" or even just
understand how they work and thus how you'd build them from scratch if you had
to.

---Joel


.