> I think a minimal core is a feature. Not minimal in the sense of trying > to squeeze out the last op, but minimal in the sense that an operation > whose time to completion is going to swamp the overhead of calling out > into native code is implemented externally rather than as an op. Any kind > of I/O falls into that category, IMO.
I disagree on this. The IO operations themselves are generally slow, period. On general, I prefer to having a very fast mechanism to call native code, which is an important feature in common sense. If it can be proved that the native functions are still to slow for IO calls, we can use opcode for them. But I don't see the need for now. Hong
