Hi Gertrude,
Originally Posted by
Gertrude the Wombat
An operating system provides facilities to applications, thus making it easier for application writers than programming to the bare metal would be. An operating system that thinks it knows best and randomly refuses to do what it's told is a right pain to all concerned
Do you write Window applications by any chance? I guess that would explain an awful lot!
That's quite an interesting philosophy you have... and there I was thinking the computer's job was to help its owner get useful stuff done with a minimum of interference.
Who is "the user"?
The owner of the current session.
The writer of the application? No, you clearly don't think it's her. The owner of the kiosk?
Which kiosk are you talking about???
The only prior mention of kiosk mode I can see is in your previous post, and I'm not quite sure what it's there for. You said
This means you can, just to pick the first example that came into my head...
Apart from not knowing where you're coming from or of what that is an example, how does the ability to override window settings prevent you from having kiosk applications? The answer is: it doesn't (and e.g., KDE is there to prove it). Please understand that in a kiosk scenario, the bloke in front of the screen is not the session owner.
I'm sorry if I misunderstood you, but I get the impression you're trying to make the point that the OS should give the application writer complete control over the user's resources, regardless of that user's wishes. I do not agree with that, and I do not even think that is a Windows design policy either (regardless of deficiencies in the actual product). I'm happy to be corrected on that last (or any other) point, however.