21 ms·

This promo site is a bit blurry on what it actually does. A browser with a focus on gestures sounds like it could be very useful, if done right. I haven't seen

by sspiff 13y ago

This promo site is a bit blurry on what it actually does. A browser with a focus on gestures sounds like it could be very useful, if done right. I haven't seen that many apps or platforms get gestures "right" though. I wonder what this browser is built from (Blink? What JS runtime?)

jvzr 13y ago
WebKit. Or else it wouldn't have been approved by Apple (or it's using a server-side engine, which I doubt).
- Facens 13y ago
  Let's keep in mind that opera purchased Skyfire a while ago, which is a lot about server-side engine browsers.
  - rplnt 13y ago
    And Opera has years of experience with server-side rendering, even on iOS.
- deleted 13y ago
  [deleted]
bla2 13y ago
Apple's app store doesn't allow apps that execute downloaded JavaScript without using the system WebKit library.
- do-it-good 13y ago
  And it doesn't run the JIT compiler. Which means all 3rd party browsers in non-jailbroken iOS are slower than Safari and Phonegap apps are a lot slower than native apps.
  - sspiff 13y ago
    I had heard about the JS runtime restriction (which is why I was interested if Opera had avoided it somehow), but never heard about the JIT restriction. Is the JIT disabled for all third party apps? I was going to make a joke about Soviet app stores, but realized this isn't the place.
    - rahoulb 13y ago
      The JIT restriction is because the OS won't let you mark data pages as executable for security reasons (Safari, as a trusted app, is the only exception). EDIT: changed wording for clarity
      - sspiff 13y ago
        Thanks for clarifying. I learned something new today.
  - captn3m0 13y ago
    Just noting that a "Nitrous", available on Cydia for jailbroken iPads, enables Nitro (JIT compiler for Safari) on all browsers.
  - bla2 13y ago
    It means javascript execution is slower in 3rd-party browsers. They can make up for that by e.g. using better networking libraries: http://www.guypo.com/mobile/ios-browsers-speed-bakeoff/ http://www.guypo.com/mobile/ios-browsers-speed-bakeoff/
    - sspiff 13y ago
      That still means it's a very asymmetric competition: by default, Apple has a significant head start because of the JIT. If others have to do some crazy engineering on networking libraries, nothing stops Apple from reusing the concepts the competition implements. The competition does not have this possibility with javascript engine improvements.
Indyan 13y ago
It is Webkit powered. And perhaps the TechCrunch article can help you get a sense of what Opera is going for: http://www.techcrunch.com/2013/09/09/opera-launches-coast-its-new-webkit-based-ipad-browser/ http://www.techcrunch.com/2013/09/09/opera-launches-coast-it...
- skue 13y ago
  That TechCrunch article includes this quote: > Kleinhout also noted that the team looked at how to keep users safe without having them evaluate lots of icons in the browser’s URL bar (which Coast doesn’t have). Instead of having to know what HTTPS is and how certificates work, Coast puts a very clear safety warning on the screen when it recognizes that the user is trying to access an unsafe site. I'm very curious to know how that works. I sure hope they don't simply show certificate errors but otherwise treat pages the same whether they are secure or not.

by sspiff 13y ago

jvzr 13y ago

WebKit. Or else it wouldn't have been approved by Apple (or it's using a server-side engine, which I doubt).

Facens 13y ago
Let's keep in mind that opera purchased Skyfire a while ago, which is a lot about server-side engine browsers.
- rplnt 13y ago
  And Opera has years of experience with server-side rendering, even on iOS.
deleted 13y ago
[deleted]

bla2 13y ago

Apple's app store doesn't allow apps that execute downloaded JavaScript without using the system WebKit library.

do-it-good 13y ago
And it doesn't run the JIT compiler. Which means all 3rd party browsers in non-jailbroken iOS are slower than Safari and Phonegap apps are a lot slower than native apps.
- sspiff 13y ago
  I had heard about the JS runtime restriction (which is why I was interested if Opera had avoided it somehow), but never heard about the JIT restriction. Is the JIT disabled for all third party apps? I was going to make a joke about Soviet app stores, but realized this isn't the place.
  - rahoulb 13y ago
    The JIT restriction is because the OS won't let you mark data pages as executable for security reasons (Safari, as a trusted app, is the only exception). EDIT: changed wording for clarity
    - sspiff 13y ago
      Thanks for clarifying. I learned something new today.
- captn3m0 13y ago
  Just noting that a "Nitrous", available on Cydia for jailbroken iPads, enables Nitro (JIT compiler for Safari) on all browsers.
- bla2 13y ago
  It means javascript execution is slower in 3rd-party browsers. They can make up for that by e.g. using better networking libraries: http://www.guypo.com/mobile/ios-browsers-speed-bakeoff/ http://www.guypo.com/mobile/ios-browsers-speed-bakeoff/
  - sspiff 13y ago
    That still means it's a very asymmetric competition: by default, Apple has a significant head start because of the JIT. If others have to do some crazy engineering on networking libraries, nothing stops Apple from reusing the concepts the competition implements. The competition does not have this possibility with javascript engine improvements.

Indyan 13y ago

It is Webkit powered. And perhaps the TechCrunch article can help you get a sense of what Opera is going for: http://www.techcrunch.com/2013/09/09/opera-launches-coast-its-new-webkit-based-ipad-browser/ http://www.techcrunch.com/2013/09/09/opera-launches-coast-it...

skue 13y ago
That TechCrunch article includes this quote: > Kleinhout also noted that the team looked at how to keep users safe without having them evaluate lots of icons in the browser’s URL bar (which Coast doesn’t have). Instead of having to know what HTTPS is and how certificates work, Coast puts a very clear safety warning on the screen when it recognizes that the user is trying to access an unsafe site. I'm very curious to know how that works. I sure hope they don't simply show certificate errors but otherwise treat pages the same whether they are secure or not.