Wow, nice vid, Charles. And nice question:
Charles wrote:
...of course on Windows I can run applications, right?
A few comments:
The file system run for benchmarks--was it FAT/FAT32/NTFS?
Closed processes: no dynamic code loading?! This seems like a weakness
from the developer's perspective. E.g., does this prohibit the ability
to load plug-ins? DLLs? Configuration-defined type loading? (Seems like a weak-ness...)
On choosing threads over event-driven architecture:
"You lose the structure of the code if you write it as a bunch of
event handlers. You know, each handler makes sense, but you don’t see
the big picture. You don't see the forest for the trees. And moreover
there's a lot of experience in, you know, windowing code, for instance,
that says that this is extremely difficult code for people to maintain,
because the first person who wrote it may have had a clear picture in
their mind but it goes away… and the next person coming along has no
idea what it is."
Amen. But shouldn't good design and design artifacts (comments,
documents, drawings, etc.) take care of some of that? Is that too much
to ask of developers?
ExHeap: very interesting.
Any chance Bartok and stand-alone compiled-to-native-code apps will
happen on XP/Vista in the next five years. (Gratuitous, feel-good
question.
)