Opera Says Their iOS Updates Are Still Coming - Just Slowly (twitter.com) 36
Slashdot reader BrianFagioli has posted an update about his communication with Opera over their plans for iOS. They'd originally tweeted Thursday that "at this moment we don't have a team working on IOS which is why we haven't released any updates." But Friday they clarified that "It does not mean we give up development on iOS. It's just that now our resources are on Android."
They reiterated that point in an email.
We would like to clarify that Opera does not abandon iOS... We plan to keep developing it as Opera Min[i] provides unique features that other browsers do not have, such as data saving for both webpages and video, ad-blocking, built-in newsfeed etc. And people love using it. As most of the engineering resources are now on Android, our update on iOS is slow at this moment. Please bear with us and do stay tune for our next updates.
The tweet Friday also emphasized that "We will update iOS for sure."
The tweet Friday also emphasized that "We will update iOS for sure."
Translation: Yeah but not really (Score:3)
Re:Translation: Yeah but not really (Score:5, Funny)
Funny, I read that as "Android is so shitty that we need all our programmers to work on Opera for Android. The iOS version works just fine."
Re:Translation: Yeah but not really (Score:4, Interesting)
Re: (Score:2)
I think it's the reverse, actually. Android has both a much larger userbase and supports Blink, Opera's native web engine. In contrast, iOS only supports Apple's version of WebKit. Why would Opera want their programmers working for a smaller userbase that would require more work to achieve less functionality?
That would mean the app requires a lot less work to maintain. In any case, the Opera value proposition is not related to the web engine but supporting features around it - data compression, ad blocking etc.
Re: (Score:2)
Fun fact: it is impossible to publish a iOS app which renders HTML without WebKit.
Re: (Score:2)
Its easy to make something fine when all you're allowed to do is put a skin over someone else's Safari code.
Re: (Score:1)
It's not surprising. iOS's market share is plummeting while Android's is skyrocketing. Apple keeps the lion's share of the profits off the app store, so companies are leaving it in droves. It's just not worth developing for iOS any more.
Re:Translation: Yeah but not really (Score:4, Funny)
Good, maybe they'll go back to making real computers instead of fashion statements.
Re: (Score:3)
Re: (Score:3)
Windows phone? Is that a thing?
I know about Windows, the gaming operating system. Is that what you're talking about?
Re: (Score:2)
He's talking about the smartphone you have in your pocket.
Re: (Score:2)
Careful, he's one of only three remaining, which makes him an endangered species. He can't get any more lumias, so should his perish, he'll perish with it.
Re: (Score:1)
GNUmmunists?
Re: (Score:1)
The last distro I tried (Debian?) did not include route or even nslookup. So my network connection wasn't working and I had no way to even install this package short of downloading it from somewhere else and transferring by USB. No guarantees that will work either as it probably needs a dozen dependencies.
Re: (Score:3, Informative)
Re: (Score:1)
So what was wrong with the old route? Did it not play nice with systemd or something?
Re: (Score:3)
What's the point? (Score:3)
Opera presents a critical alternative to the internet ecosystem many thanks to using Presto as it's rendering engine. Given how Apple forces all browsers to effectively become a re-skinned Safari with Webkit underneath there's no point to using Opera on iOS.
Re: (Score:2)
I wish. Opera dropped Presto years ago, becoming yet another Webkit/Blink skin.
Re: (Score:2)
On the desktop they did.
On the Opera Mobile it was only dropped recently.
On Opera Mini Presto continues to be the rendering engine.