[deleted]
Introducing the Google Chrome OS
81–90 of 180 posts
Re: Introducing the Google Chrome OS
#82I wonder just how Google Native Client will fit into this, especially extended with things like USB support and OpenGL. There's games, obviously, but what about a NaCL port of iTunes? It's not that far-fetched.
Google has already indirectly "extended" Native Client with native 3D graphics using their O3D API ( http://code.google.com/apis/o3d/ ). It's just a matter of time until someone codes up a library to expose that API through JS interop in Native Client. I think we can expect very close integration of Native Client into the Chrome OS as soon as or right after it goes public. To the level of accessing hardware ports to…
But will Native Client work on ARM?
Re: Introducing the Google Chrome OS
#83I've an AA1 running Linpus, which is buggy and slower than I anticipated. It's bloated down with superfluous software that I don't need, and that you have to follow a series of complex guides to remove. (Even then you risk screwing up parts of Linpus which are dependant on it.) All I use it for is browsing and light coding on the move. Windows, and the likes of Ubuntu Netbook Remix are all too 'big' for that. It soun…
I get the impression that the only native application it will run is Chrome. So how are you going to edit your source code, push/pull your changes, test it, run it? I've seen web-based ssh clients, and someone might be able to write a web-based vnc / remote desktop client, but I can't see it being useful for offline coding.
You're grossly over-complicating my needs.
None of my websites (that I would edit on the netbook) are business critical / make money / have any real world importance whatsoever. I can log in via cpanel, roll out some coding amends live and worry about breaking things as and when it happens.
Re: Introducing the Google Chrome OS
#84Let's hope this also means that a Linux version of Chrome is around the corner.
If you haven't tried out the chromium nightly desktop builds, they're actually quite nice. The team is still nailing down the plugins, but the browser itself is wicked fast and pretty stable (given its alpha nature)
Even for a minimalistic web-browser Chromium is still rather lacking. While what used to be butt ugly font-rendering has gotten better, at least to the point of readable, as far as I can tell there is still no plugin support.
The only way you can fully configure the browser is still trough running gconf-editor for some parts, and configuring Firefox and then importing settings from there.
That being said, my biggest issue with the current chromium builds is that performance is truly horrible and majorly unstable. Sometimes things just works, snappy, as expected. But in more than 50% of the cases when opening a new page the entire browser locks, for what can be periods of up to 5 to 10 seconds. Wasn't process isolation supposed to fix this?
If this browser is going to be the "OS" for the web, in it's current state its closest equivalent would be Windows 3.11.
IMO Firefox 3.5 is a much better browser, while peak performance being somewhat slower, at least it performs predictably.
Re: Introducing the Google Chrome OS
#85Earlier quoted context omitted.
If you haven't tried out the chromium nightly desktop builds, they're actually quite nice. The team is still nailing down the plugins, but the browser itself is wicked fast and pretty stable (given its alpha nature)
If you're a Mac user, you can also download the latest nightly build here: http://build.chromium.org/buildbot/snapshots/chromium-rel-ma... (scroll all the way down to the latest build directory) And yes, it is wicked fast . On my system, it doesn't even bounce in the dock before opening. It just opens. Plugins aren't supported yet, but I just open any sites that require Flash in Safari.
> On my system, it doesn't even bounce in the dock before opening.
I think it doesn't bounce for a different reason. For example, Firefox doesn't bounce when it autoupdates. Everything should bounce for at least one time in normal conditions.
Re: Introducing the Google Chrome OS
#86Earlier quoted context omitted.
Google has already indirectly "extended" Native Client with native 3D graphics using their O3D API ( http://code.google.com/apis/o3d/ ). It's just a matter of time until someone codes up a library to expose that API through JS interop in Native Client. I think we can expect very close integration of Native Client into the Chrome OS as soon as or right after it goes public. To the level of accessing hardware ports to…
But will Native Client work on ARM?
Re: Introducing the Google Chrome OS
#87Earlier quoted context omitted.
Google did for Android so they could standardize around the Apache License for userspace. But who knows, they may not bother here. The netbook market is decidedly different than the mobile phone market, so they probably do not have the same constraints.
No one's developing for userspace—the "application" developers for GCOS will be writing web apps.
Or Native Client apps.
Re: Introducing the Google Chrome OS
#88Earlier quoted context omitted.
I get the impression that the only native application it will run is Chrome. So how are you going to edit your source code, push/pull your changes, test it, run it? I've seen web-based ssh clients, and someone might be able to write a web-based vnc / remote desktop client, but I can't see it being useful for offline coding.
You're grossly over-complicating my needs. None of my websites (that I would edit on the netbook) are business critical / make money / have any real world importance whatsoever. I can log in via cpanel, roll out some coding amends live and worry about breaking things as and when it happens.
Ah, right, I misinterpreted what you meant by "light coding".
Re: Introducing the Google Chrome OS
#89If ARM and x86 are targeted, this means no Flash (not surprising, given how poorly it runs on Linux), which presumably means YouTube will be operating in full-on HTML 5 video mode by the time these devices launch. If netbooks continue their meteoric ascent, and if Chrome OS grabs a significant share of the market, we may finally see the realization of the mythical Year of Linux On the Desktop. The ironic aspect, of c…
Flash has a few small problems on Linux, but generally is usable.
While it's not unusable, the performance issues are not trivial. At least on slower CPU:s.
Re: Introducing the Google Chrome OS
#90Is this a response to bing? If you go after my market, I'll go after yours.
It's not only the Chrome OS thing. Google Apps out of beta could mean that Google is serious about competing in the groupware segment.