On Sep 10, 2009, at 9:24 PM, Nasir Barday wrote:
The distinction between OS and Browser is becoming unimportant.
Except for the minor fact that without an OS you can't actually launch
a browser.
The main difference is in performance;
The main difference is that the OS actually runs the hardware, things
like your keyboard, mouse inputs, RAM usage, drawing to the computer
screen, etc. If the browser ran the hardware, then the browser would
be an OS.
if you need to do processor-intensive stuff
(design/development, making video, laying down tracks for your
latest album,
tricky features in productivity apps), a native-running app is the
ticket.
You've made a leap here. (One which is reasonable, fwiw.) You've gone
from talking about OS versus Browser App to talking about the
difference between Browser App versus Native App.
With strange animals like "SplashTop," a minimal OS for netbooks
that runs
Skype, Mozilla, and IM; Google's Gears and pending Chrome OS; and
especially
with Web 2.0's ability to save and use local data, as well as run
without an
Internet connection, what's the difference to the end-user? One runs
inside
the other, but what if the Browser ran alone? That's more of the
question
you're asking, right Kim?
I'd love to know how it's possible for a browser application to even
launch without an OS.
-Andrei
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
