3 ms·

That's the politically correct way to look at it but I don't think you're right. With the advent of the $30 smartphone, by the time these countries have dispos

That's the politically correct way to look at it but I don't think you're right. With the advent of the $30 smartphone, by the time these countries have disposable income that you can indirectly or directly profit from, its likely that one of their first purchases is a better phone with a capable browser. Until then they're a waste of time and resources. On Black Friday you could get a Moto E, unlocked and off contract, for $10. This phone has a quad core processor, an LTE radio, a gig of ram, and a 5 megapixel camera. Ten dollars gets you something that can outperform flagships from 2 years ago.

zAy0LfpBZLC8mAC 11y ago
And which magic exactly does that phone perform to reduce the bandwidth prices of their provider?
- nickysielicki 11y ago
  The same exact "magic" of MITM optimization that Opera performs is available in Chrome for Android. [1] But even putting that aside, you're ignoring the fact that as these developing nations develop and have money that's worth going after, bandwidth is certainly going to become cheaper as well. [1]: https://support.google.com/chrome/answer/2392284?hl=en https://support.google.com/chrome/answer/2392284?hl=en
  - mahouse 11y ago
    You really can't compare both.
    - nickysielicki 11y ago
      Um, why not?
      - mahouse 11y ago
        I guess Chrome compresses the HTML and maybe recompresses the images. But what Opera Mini delivers to the user's browser has nothing to do with HTML, is completely stripped from any JS, etc
      - seba_dos1 11y ago
        You can compare what Chrome does with Opera Turbo feature from Opera Mobile and desktop Opera, but not Opera Mini. It was definitely inspired by experiences from Opera Mini, but it's absolutely not comparable at all. Opera Mini doesn't render webpages, it's all done server side. What's sent to the browser is a pile of highly compressed layers containing text and images and some metadata about what's clickable - and that's it. From HTML, JS and CSS point of view Opera Mini is a highly optimized, non-real time remote desktop client. I've heavily used J2ME Opera Mini on my S40 dumbphones many years ago. Back then it was awesome. Today, when the only way to keep sanity when browsing the web on desktop is using NoScript, I doubt that using it would be as awesome as it was back then, and that's not really Opera Mini fault. After all, when using Opera Mini, you don't expect everything to work and render as it would on desktop browser - as long as content is shown and can be accessed properly, it's fine. However, in a world where crazy people use SPA frameworks for their blogs, it cannot be taken for granted.
usrusr 11y ago
A faster smartphone won't reduce traffic. Even if you had the latest and greatest flagship phone you might still want to install opera mini if traffic cost per byte is sufficiently high.

zAy0LfpBZLC8mAC 11y ago

And which magic exactly does that phone perform to reduce the bandwidth prices of their provider?

nickysielicki 11y ago
The same exact "magic" of MITM optimization that Opera performs is available in Chrome for Android. [1] But even putting that aside, you're ignoring the fact that as these developing nations develop and have money that's worth going after, bandwidth is certainly going to become cheaper as well. [1]: https://support.google.com/chrome/answer/2392284?hl=en https://support.google.com/chrome/answer/2392284?hl=en
- mahouse 11y ago
  You really can't compare both.
  - nickysielicki 11y ago
    Um, why not?
    - mahouse 11y ago
      I guess Chrome compresses the HTML and maybe recompresses the images. But what Opera Mini delivers to the user's browser has nothing to do with HTML, is completely stripped from any JS, etc
    - seba_dos1 11y ago
      You can compare what Chrome does with Opera Turbo feature from Opera Mobile and desktop Opera, but not Opera Mini. It was definitely inspired by experiences from Opera Mini, but it's absolutely not comparable at all. Opera Mini doesn't render webpages, it's all done server side. What's sent to the browser is a pile of highly compressed layers containing text and images and some metadata about what's clickable - and that's it. From HTML, JS and CSS point of view Opera Mini is a highly optimized, non-real time remote desktop client. I've heavily used J2ME Opera Mini on my S40 dumbphones many years ago. Back then it was awesome. Today, when the only way to keep sanity when browsing the web on desktop is using NoScript, I doubt that using it would be as awesome as it was back then, and that's not really Opera Mini fault. After all, when using Opera Mini, you don't expect everything to work and render as it would on desktop browser - as long as content is shown and can be accessed properly, it's fine. However, in a world where crazy people use SPA frameworks for their blogs, it cannot be taken for granted.

usrusr 11y ago

A faster smartphone won't reduce traffic. Even if you had the latest and greatest flagship phone you might still want to install opera mini if traffic cost per byte is sufficiently high.