So, IRC is only input. RSS is only input. Browser is interactive. In that case, it makes sense the browser is full screen. But the interaction between RSS and browser is minor. So these can run full screen as well, or transparent in a sortof gadget mode (difficult).

If you compare the way how settings are changed between MicroB and Fennec, or the way a bookmark is accessed compared between the 2, how can you not understand most people will prefer the Fennec way once they're used to it? Because they think visual, in pictures? Maybe because programmers and geeks are bad designers!

I use the term gestures instead of mouse gestures because not necessarily a mouse is used.

If I want to not harass other people with my sound, I simply put it off. My brightness I would rather not touch back and forth because I have better things to do than that.

You misunderstood.

(And, actually, some computers do what you describe, both GNOME and KDE support this; kiosk mode; often used on thin clients.)

Various applications always run on the computer. Some might run in the UI. I'm not arguing only one application is allowed at a time. I'm arguing a user, in general, wishes to focus on one application instead of seeing multiple.

IOW, a kiosk mode which does allow (several) background tasks [multitasking] and does allow non-full screen [desktop environment] but not by default. It is assumed the user has full focus on the application. This way, the application can take more advantage of touch screen, finger-based and there is more space more e.g. virtual keyboard besides the actual application.

Speaking of the virtual keyboard. Have you tried the Python + QEdje virtual keyboard? The focussed key pops up, and its not selected until the user leaves the finger off the touchscreen. This is also a good, usability related feature. The designer can assume the user approaches the key the user wishes to tap, but not necessarily accurately. Hence, this is a good solution for this problem. Here is another demo, showing QEdje + QZion (by INdT developer). This shows even more the powerful possibilities of QEdje. And don't forget... Edje is fast!