3 ms·

Is it that much different than the mobile browsers that rendered the page on a server and just sent a compressed representation to the phone? A variant of opera

by onli 6y ago

Is it that much different than the mobile browsers that rendered the page on a server and just sent a compressed representation to the phone? A variant of opera did that and worked so much better than regular browsers on weak phones. This targets different devices, but it could work equally well.

stephc_int13 6y ago
I know this is not a new idea, and this is precisely why I think we should know better. If our computers are not fast enough to run thin clients (what a web browser is) to display documents then I think we should do something about it instead of trying to offload the bloat somewhere in the cloud.
- Axsuul 6y ago
  > If our computers are not fast enough to run thin clients (what a web browser is) to display documents then I think we should do something about it instead of trying to offload the bloat somewhere in the cloud. Except you might be stuck waiting forever for this to happen. Mighty provides a practical solution, today.
Kwpolska 6y ago
Opera Mini would send binary markup and heavily compressed images [0]. The final rendering and any interactions happened on the user’s device. This service is basically remote desktop (RDP/VNC) to a copy of Chrome running in The Cloud. Opera Mini was also the most popular in a different Internet landscape (no SPAs, smaller sites overall, tiny non-touchscreen dumbphones). [0]: https://en.wikipedia.org/wiki/Opera_Mini#Functionality https://en.wikipedia.org/wiki/Opera_Mini#Functionality
- 83457 6y ago
  On a related topic, I actually chose my phone around ~2004 based on the full Opera Mobile browser being included (Nokia 3650 I think it was). The ability to bring up and use almost any site and browse around in a 2 inch screen like a little portal into the web was great. It was much much better than any other mobile browser I had used because it was fully rendering instead of converting for mobile (though that may have been an option). Was one step away from what people started to experience with the touch phones that came out a few years later.

by onli 6y ago

stephc_int13 6y ago

I know this is not a new idea, and this is precisely why I think we should know better. If our computers are not fast enough to run thin clients (what a web browser is) to display documents then I think we should do something about it instead of trying to offload the bloat somewhere in the cloud.

Axsuul 6y ago
> If our computers are not fast enough to run thin clients (what a web browser is) to display documents then I think we should do something about it instead of trying to offload the bloat somewhere in the cloud. Except you might be stuck waiting forever for this to happen. Mighty provides a practical solution, today.

Kwpolska 6y ago

Opera Mini would send binary markup and heavily compressed images [0]. The final rendering and any interactions happened on the user’s device. This service is basically remote desktop (RDP/VNC) to a copy of Chrome running in The Cloud. Opera Mini was also the most popular in a different Internet landscape (no SPAs, smaller sites overall, tiny non-touchscreen dumbphones). [0]: https://en.wikipedia.org/wiki/Opera_Mini#Functionality https://en.wikipedia.org/wiki/Opera_Mini#Functionality

83457 6y ago
On a related topic, I actually chose my phone around ~2004 based on the full Opera Mobile browser being included (Nokia 3650 I think it was). The ability to bring up and use almost any site and browse around in a 2 inch screen like a little portal into the web was great. It was much much better than any other mobile browser I had used because it was fully rendering instead of converting for mobile (though that may have been an option). Was one step away from what people started to experience with the touch phones that came out a few years later.