The Following User Says Thank You to cheve For This Useful Post: | ||
|
2011-05-12
, 18:53
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#122
|
That is exactly the issue that may prevent cloud to be "universal" for everyone. People have different requirement/expectation and use cases; as a result, App developer would get complaints due to offline mode being not sufficient to support the use case of those making the complaints and the developer will end up re-writing(over the life time of the product) the application to execute entirely on the client side.
So, in my view, if things are going to be cloud base, then everything should be in the cloud; otherwise, allowing things to execute in both the cloud and on local client will be an on-going headache/heartache.
Actually what make this cloud thing different from the X-windows of the 'older' days?
cheers,
The Following User Says Thank You to Capt'n Corrupt For This Useful Post: | ||
|
2011-05-12
, 19:06
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#123
|
|
2011-05-12
, 20:34
|
Posts: 362 |
Thanked: 143 times |
Joined on Mar 2008
|
#124
|
...
The cloud-thing is very similar to the X-windows of old in that they act as 'thin clients', with a few important distinctions:
1) It's widely supported -- most user computers have access to the network in one form or another and also the web.
2) There exists the possibility to do client-side processing via javascript/flash/NaCL as well as accelerated content WebGL/HTML5-video/etc.
3) Bandwidth has improved dramatically since the early days of X as well as the methods of connection
It borrows the thin-client aspect of X, but there are other attributes that make the web unique.
The Following User Says Thank You to cheve For This Useful Post: | ||
|
2011-05-12
, 22:31
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#125
|
I guess we are sort-of back in a full circle....central control of mainframe with thin client(of the 'yester-year' ) ==> full feature local control of clients(aka. age of Personal computer) ==> back to central control of the cloud with thin clients(the NET, the Web and all that)...
cheers,
The Following User Says Thank You to Capt'n Corrupt For This Useful Post: | ||
|
2011-05-13
, 00:26
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#126
|
|
2011-05-13
, 00:33
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#127
|
|
2011-05-13
, 02:02
|
Posts: 482 |
Thanked: 550 times |
Joined on Oct 2010
|
#128
|
That would be interesting! Currently there's no ARM variant of Chrome, and the Javascript engine (at least) relies x86, so a port would be challenging.
Chrome OS is just a browser, so any HTML5 capable browser should have access to the same apps that chrome does.
Chrome just makes it a bit easier to discover apps by way of the chrome web store, and Chrome OS forces users to operate exclusively on the web as the only accessible userland app is -- Chrome.
The Following User Says Thank You to skykooler For This Useful Post: | ||
|
2011-05-13
, 03:26
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#129
|
Hmm... It is open source, and Hexxeh has compiled it for the iPad, which AFAIK has an ARM processor, so it should be possible...I am not quite knowledgeable to attempt that though.
|
2011-05-13
, 12:37
|
|
Posts: 3,524 |
Thanked: 2,958 times |
Joined on Oct 2007
@ Delta Quadrant
|
#130
|
Tags |
awesome sauce, chrome os, chromebook, go away, long and boring, oh yeah!, quite enough, talking2myself, webgl, yaaaaaaaaaaawwn |
|
So, in my view, if things are going to be cloud base, then everything should be in the cloud; otherwise, allowing things to execute in both the cloud and on local client will be an on-going headache/heartache.
Actually what make this cloud thing different from the X-windows of the 'older' days?
cheers,