Opera Slows Its Development On The iOS Platform (betanews.com) 61
Reader BrianFagioli writes: After searching for Opera in the Apple App Store, I noticed something odd -- none of the company's iOS browsers (Opera Mini and Opera Coast) had been updated in 2017. Since we are almost halfway through the year, I decided to ask Opera what was up. Shockingly, the company told me that it no longer has a team working on iOS. An Opera employee by the name of 'Rosi' sent me a tweet this morning, making the revelation. While the desktop version of the browser is still in development, the company has chosen to abandon its efforts on iOS. To show just how bad it is, the Opera Mini browser hasn't been updated in almost a year. Opera Coast was updated in December of 2016, however -- almost six months ago.
Update: Opera has clarified that while they're not currently working on iOS, they still plan to support it.
Update: Opera has clarified that while they're not currently working on iOS, they still plan to support it.
Re: Religion is the enemy (Score:2)
Yeah. Those pesky religious nuts that murdered 45 million people in China and 23 million in Russia and 1.7 million in Cambodia. Yup. Religion is definitely the problem.
Re: (Score:1)
Funny I was just thinking of this yesterday -- extremism is a problem, oppression is a cause
Re: (Score:2)
I was hoping for a comment (done), not a zero.
Re: (Score:2)
Opera had tabbed browsing really early on. It used to be pretty fast compared to everything, too. It had its day in the sun.
I think it had a spotless record as far as exploits go, too.
I never liked it; but there's something to be said for no exploits, ever...
Re: (Score:1)
If it it wants to be of anything useful it should take the Firefox source code and keep a XUL extension system running instead of web extensions.
There's already PaleMoon for that, which has been my default browser for about five years now.
Somehow this is bad for Apple (Score:3, Funny)
Re: (Score:3)
Maybe Opera are partners with the 3.5mm headphone jack and this is retaliation for Apple's courage.
Re: (Score:2)
Re: (Score:2)
Maybe if apple didn't want to be laughed at it wouldn't say and do such stupid things.
You mean like releasing a computer with no floppy and no serial or parallel ports in 1998? ...or releasing a phone with no keyboard?
Yeah, they were sure proven wrong there...
Re: (Score:2)
People can try to push those old jokes all they want, but the fact is that Apple did remove the standard 3.5mm headphone jack and they did call it "courage". If the technology to replace something is of lower quality than what it replaces, I don't call it "courage" I call it "stupidity".
Re: (Score:2)
People can try to push those old jokes all they want, but the fact is that Apple did remove the standard 3.5mm headphone jack and they did call it "courage". If the technology to replace something is of lower quality than what it replaces, I don't call it "courage" I call it "stupidity".
How would a digital interface with the chance to use a better DAC than the iPhone has internally be better than an analog interface with a nasty reputation for intermittent behavior?
Re: (Score:2)
Re: Somehow this is bad for Apple (Score:1)
Re: (Score:2)
I haven't figured out how it's bad yet, but I'm sure I will. Just give me a minute.
It means that Apple has just become another platform and it's not worth wasting a lot of resources over.
The whole "app" fad is coming crashing down as most phones are more than capable of doing most things you want in the browser. Certainly Android has had this capability for years. This means a company only has to manage 1 website instead of a myriad of apps in different stores with different programming languages.
iOS "Browsers" are all Safari skins (Score:5, Interesting)
Given that all browsers on iOS are required to use WebKit, and Opera's investment in Presto and fallout for supporting Blink, I can see why Opera would cut their losses and cease development on what is ultimately only a skin for iOS functionality.
Also, I expect that the additional complexity of offering an app-specific VPN to iOS users factored in to the decision.
nice skin then (Score:2)
For me the very best everyday browser on my iphone was coast. so it's too bad.
they did do mre than skin it by the way. They also compressed websites for faster transmission.
Re: (Score:2)
Re: (Score:2)
There are no browsers on iOS (Score:1)
So-called "browsers" on iOS are just skins. Why would anyone think Opera's skin is relevant?
Re: (Score:2)
Opera wasn't a skin (at least not for Opera Mini). The iOS requirement is misunderstood: it isn't a restriction on browsers or browser engines, it's a restriction on code execution (Javascript). Since Opera Mini ran the javascript on the server-side and not the client, it was allowed to use a custom layout engine.
Only Reskinned Safaru (Score:5, Interesting)
The only thing third party developers are allowed to do is reskin Safari, so it shouldn't be a surprise if the entities who make good, even better, browsers on other platforms just drop out.
Re: (Score:2)
Opera has always seemed to have a problem finding a place. When MS was still able to us the desktop monopoly to create a place for IE as an application front, and thus make everything compatible with on IE, Opera tried to get into the MS Windows browser space with a good b
Something to note (Score:4, Informative)
Opera, however, was different - they would render the page server-side as an image and then send that image to your phone. This let them ship a browser on iOS as well as get around Apple's no-rendering-engines rule.
But you can see the issue with this, right? Is Opera caching the images on their servers? Probably not but you can't know. For all you know, JPEGs of your bank website are on their servers. SSL doesn't matter as much anymore because the rendering isn't being done on your device.
So this is different than if they were abandoning an iOS web browser that was a WebKit wrapper like the others, this is Opera saying they no longer want to deal with this render-on-the-server mess.
To say nothing about the fact that Opera as a company has to be struggling right now, they've got less desktop market share than Edge, which no one uses on purpose. They have less market share than Safari which is only on the Mac. I think their switch from Presto to Blink was less that they agreed with Google's standards and more that they just couldn't afford to keep developing Presto anymore. It must be so weird to work for a company that makes a product so few people use.
Re: (Score:2)
Re: (Score:2)
My experience also. Opera is dramatically better on my old MacBook Air. It doesn't max out the memory or the CPU whereas Chrome and Firefox do that all the time.
There is no browser "alternative" on iOS (Score:2)
Re: (Score:2)
Death to 32-bit apps?! (Score:2)
Or maybe Opera couldn't switch their tool chain over to exclusively 64-bit iOS apps? Apple is planning to drop 32-bit apps from the app store. A friend who tests iOS apps told me that this is a big problem for some 32-bit app developers.
https://9to5mac.com/2017/04/09/32-bit-apps-ios/ [9to5mac.com]
Re: (Score:1)
Apple is planning to drop 32-bit apps from the app store.
In post-Soviet Cupertino, platform abandons YOU!
WKWebView doesn't support custom NSURLProtocol (Score:2)
Since iOS 8, Apple recommends everybody uses the new WKWebView which replaces UIWebView: https://developer.apple.com/re... [apple.com]
However, WKWebView is not as flexible as UIWebView; more specifically, there is no support for a custom NSURLProtocol. Basically to get the performance gains of using WKWebView, you can't do the things you want to do.
For Opera specifically, this bug filed against webkit lays out the features they would like to implement, but are unable to: https://bugs.webkit.org/show_b... [webkit.org]
Opera on iOS im
who cares (Score:2)
Hosted web browser in iOS (Score:1)
It's about time someone came up with an turnkey-solution front-end/back-end version of Firefox and Chrome.
The front end would work on iOS or for that matter any other operating system and the back end - which would do the rendering and provide the any UI elements prohibited by Apple's rules - would work on the "back end." The back end would work on my PC/macOS/Linux machine or more likely a cloud-virtual machine.
You say Apple wouldn't allow this? Oh, but they already do: Every remote-desktop/VNC/etc. too
It's all Safari anyhow (Score:2)
Who cares? (Score:2)
The market share of iOS is below 20% worldwide anyway. On;y in the US it is still comparable with Android, but in all other markets it is nearly dropping to the level of irrelevant.