HI,
Rusky wrote:
I'm not trying to demean your system for non-technical reasons- Ready4Dis and kiznit have got it right. There are several existing systems, not just HTML, that try(ed) to do what you're doing, and all of them have these same performance problems. You have not said anything about your system that convinces me it would be any different.
I can't see why there'd be a significant difference in performance; and you've consistently failed to provide any rational reason for it.
Rusky wrote:
On the other hand, you seem to have a habit of calling low-level details "irrelevant pus" or other such colorful hyperbole, and hinting that once you let applications see them, then all applications will have to deal with them all the time, which is just as false as your assertions about high-level interfaces.
The entire point of drivers (and higher levels on top of them) is to abstract hardware details, so that applications don't need to worry about things like cylinder/head/sector and can just use a "file IO" abstraction, don't need to care what the USB controllers is and can just receive keyboard/mouse events, don't need to care about specifics of a network card and can just open a socket, etc. For a general purpose OS; failing to abstract these low level details is a massive design failure - they *should* be irrelevant (from an application's perspective).
All my applications will be 3D (there will be no 2D at all anywhere on my OS); which means every application will need to deal with the 3D graphics API.
Rusky wrote:
Whenever someone calls you out on this, you start arguing about why libraries and all possible replacements for them are bad. You haven't convinced me there, either.
Nobody (including me) has mentioned libraries or possible replacements for them in this entire (6+ pages) discussion.
Cheers,
Brendan