| PLEX86 | ||
|
Where should the type information be 331
now -- had commercial games Sigh! I'm not knocking them. I am commenting on what kinds of production may not occur when all the OS development is based there. I know they have an individualist streak. That becomes an impediment when new techniques have to be used to solve a problem. OH, no. I never intended to imply that India's culture is copy-based. Just the opposite, in fact. When I was a momentary tourist in China, one of the things that stood out was their long-term thinking and intention of implementing it all. Just the way they were funding the various infrastructure building told me a lot. Let me try to explain; please remember our discussions of how I clbuttify thinking into OS-thinking and compiler-thinking. The thinking styles I've seen don't fall into either category. Now for my DO-loop comment. Please note that this is very simplistic and is not meant to completely describe 100% of thinking but gives a hint. Where should the type information be 332 I'm not sure that the US' symptoms are caused by that. I'm beginning to play with the cause being specialization... When you write a DO loop, you implicitly leave the counting to code that you didn't write, can't control, and can't "watch". IME, this was extremely difficult for a person who grew up in Indian culture to allow. What happened was that a programmer would write inline code doing his own counting of times through a loop. This kind of program control never allows interrupts to "control" the end of any OS code. And everything in the OS biz is based on handling interrtupts well. Allowing one's code to be based on events means that you have to cede your individualism to react-mode and lose the "I need to have control of everything" mode.
BAH Where should the type information be 333 Obviously. The problem was not either of these terms; it was what you meant by them... Subtract a hundred and four for e-mail.
|
||||||||