The Google Chrome OS
The Google Chrome OS
Posted Jul 9, 2009 7:50 UTC (Thu) by renox (guest, #23785)In reply to: The Google Chrome OS by drag
Parent article: The Google Chrome OS
Given that in the 'Chrome OS' you'll use only web application, this will be 'solved' by not letting you use those traditional applications.
> getting new versions of firefox,
> installing favorite applications from Windows,
'Solved' again by not letting you use those applications.
> setting up printers,
The issue is the same here as the kernel is Linux the drivers are the same.
> setting up vpns, etc etc.
Solved by using https.
Now I must admit that I don't understand the interest of a Chrome OS compared to running Chrome on a normal Linux distribution.. You can already easily use Linux in a 'thin client' setup, so what's the interest of restricting it to running web application?
Posted Jul 9, 2009 8:13 UTC (Thu)
by drag (guest, #31333)
[Link] (3 responses)
Ha. :)
If you make it hard to use traditional applications it won't make people not want to use those applications, it'll just make them not want to run your OS.
> 'Solved' again by not letting you use those applications.
Yep. And users will 'solve' the problem the same way that they solved the problem for older Netbook "web centric" Linux OSes.. get somebody to install Windows over it.
> The issue is the same here as the kernel is Linux the drivers are the same.
Printer drivers are not Linux kernel drivers. They are userspace. You need to have some speciality programs to support crappy printers that are so dumb that they can't understand postscript, but even then they don't have anything to do with the kernel. It's done through things like libusb and printer port-over-USB and whatnot. It doesn't require much of anything from the kernel.
Then for smarter devices that can take postscript you still need ppd files and ghostscript-related stuff to modify and create printer-specific postscript pages on the fly.. that is if you want anything more complex then single sided page black and white print output. And for network printers you need to have SMB support, IPP, and all that sort of stuff. And then you need CUPS and you need to have applications to manage and configure them. Then you need to have a notification system so people can deal with printer queues and cancel print jobs and get notified when print jobs are finished.
Printer problems are all userspace problems. I wonder if Google is smart enough to figure out how to make a web application speek to a network'd laser printer... :)
> Solved by using https.
Except people very rarely use HTTPs for their work or even home VPNs. For the most part they are restricted to using whatever their work has set up for them or whatever came with their el'cheapo home router. Using something like IPsec, PPTP, or Cicso VPN will be much more common requirements.
Remember it's the user that sets the requirements for the OS. If the OS does not meet those requirements then the users are not going to change their requirements... they are simply going to use something else, and that something else is probably just going to be Windows.
:)
Posted Jul 9, 2009 16:39 UTC (Thu)
by khim (subscriber, #9252)
[Link] (2 responses)
Posted Jul 9, 2009 17:33 UTC (Thu)
by drag (guest, #31333)
[Link] (1 responses)
But it still doesn't really help much. You still need a way to edit postscript files on the fly to add in commands for color or front-to-back printing. Then you still need a way to deal with network printers. And no 'native code' drivers exist for dumb inkjet printer, etc etc.
In order to do printing with 'just a browser on a kernel' your going to essentially have to recreate all the functionality provided by gnome printer dialog, samba, cups, ghostscript, gnome notification system, usb hotplug, network autodiscover protocol support, and probably half a dozen other little things. Printers are a huge PITA and I hate them and they are relatively hard thing to support.
Now granted it's certainly possible to have a browser handle all that, but it would be rather insane.
It is my fondest wish that Google would simply let a distribution handle that and do something like run 'Chrome OS' on top of a Moblin Compliant OpenSuse or Ubuntu OS.
Posted Jul 12, 2009 10:29 UTC (Sun)
by efexis (guest, #26355)
[Link]
The Google Chrome OS
Why not?
Printer problems are all userspace problems. I wonder if Google
is smart enough to figure out how to make a web application speek to a
network'd laser printer... :)
You only need to extend browser a
bit to make it possible to access raw printer device from it - and then
printer supplier can run printer driver in a box...Why not?
"In order to do printing with 'just a browser on a kernel'..."Why not?
...you're going to need for your webapp / cloud server to understand how to output your document in your printers language, and you're going to need your browser to let you send that file to your printer.
Why would you need your printer drivers to be stored locally, if your documents aren't?