News for hackers. Stuff that matters.
Re:The Chrome Distortion: how Chrome negatively alters our e... by okket on Saturday March 26, 2016 @11:48AM (#11366049)
Such a "hype cycle" can only exist where the OS supports integration of 3rd party browsers (desktop only).

On mobile devices you can rarely switch browsers without losing access to major parts of the OS (read: 3rd party browsers can render/view web pages, but forget about integration).

Re:The Chrome Distortion: how Chrome negatively alters our e... by SomeCallMeTim on Saturday March 26, 2016 @11:59AM (#11366097)
>On mobile devices you can rarely switch browsers without losing access to major parts of the OS

You mean "on iOS", not on mobile devices in general. On Android at least all such integration is done with Intents, a broadcast message from the OS or one app to another, and those Intents can be remapped to target whatever app a user wants, meaning a third-party browser can be as integrated into the OS as Chrome. You can even replace the launcher (the home screen) by having your app accept the "Home" Intent.

Whether a particular browser respects the Intent linkage correctly is another story. But it's absolutely possible. Chrome is doing nothing secret and magic on Android.

The exception is WebViews embedded in apps, which are rendered using the Chrome engine (on recent Android versions). But as an app developer, let me tell you that having random third-parties replace the WebView in my app is a profoundly bad idea. It's hard enough to target all the Android versions without having to also target every random browser rendering engine.

Re:The Chrome Distortion: how Chrome negatively alters our e... by kuschku on Saturday March 26, 2016 @02:40PM (#11366826)
> Chrome is doing nothing secret and magic on Android.

> having random third-parties replace the WebView in my app is a profoundly bad idea

You haven’t heard of Chrome Custom Tabs, have you?

Re:The Chrome Distortion: how Chrome negatively alters our e... by SomeCallMeTim on Sunday March 27, 2016 @01:19PM (#11370656)
No, actually. Thanks for letting me know about that.

Regardless, my point stands: If I'm writing an app and I use a WebView or a Chrome Custom Tab, I'm going to want to know, for certain, that someone isn't switching out the underlying rendering engine.

Re:The Chrome Distortion: how Chrome negatively alters our e... by kuschku on Sunday March 27, 2016 @03:55PM (#11371258)
Well, but that’s the entire point of Chrome Custom Tabs. There are even Presto and Gecko based implementations of it.
Re:The Chrome Distortion: how Chrome negatively alters our e... by SomeCallMeTim on Monday March 28, 2016 @12:18AM (#11372707)
The "point" of Chrome Custom Tabs seems to be performance and better integration with the system browser.

I see that it's done via Intent, so it could potentially be swapped out, so you're right.

So then WebView is more of what I'm talking about, for when you want tight integration, or creating something like a Cordova app (though you can bundle a Cordova app with Crosswalk to sidestep WebView differences entirely); looks like Chrome Custom Tabs is more for when you want a good web experience, not a good embedded app experience.

Re:The Chrome Distortion: how Chrome negatively alters our e... by anon1385 on Saturday March 26, 2016 @01:05PM (#11366399)
>You mean "on iOS", not on mobile devices in general.

Also on FirefoxOS and ChromeOS where third party browsers aren't possible at all.

Re:The Chrome Distortion: how Chrome negatively alters our e... by lorenzhs on Saturday March 26, 2016 @01:17PM (#11366458)
The first of which is discontinued and the second not an OS for mobile devices (phone/tablet)
Re:The Chrome Distortion: how Chrome negatively alters our e... by anon1385 on Saturday March 26, 2016 @02:38PM (#11366815)
FirefoxOS still exists.

Anyway if we are criticising organisations for creating platforms that prevents switching browsers then I don't think FirefoxOS's failure to achieve any kind of market penetration should exonerate Mozilla. FirefoxOS is/was objectively worse than what iOS does in that regard.

Re:The Chrome Distortion: how Chrome negatively alters our e... by idle_zealot on Saturday March 26, 2016 @12:00PM (#11366105)
I'm not sure what OS you're referring to here. I mostly have experience with Android, and know that my browser experience is nothing like what you described. Is it really that bad on other OSes?
Re:The Chrome Distortion: how Chrome negatively alters our e... by thisislame on Saturday March 26, 2016 @12:14PM (#11366165)
Why would I ever want my browser to have access to anything outside its running context? In what universe is this a good idea?!

I don't even want it to have access to the clipboard until I affirmatively paste contents!

The browser is a window into an unsafe world of shit you don't trust or control (also known as THE WORLD.) It's SUPPOSED to be at a remove from your local resources. Lack of integration is a FEATURE.

Creating browsers (and add-ons) without this design tenet from the outset is how you end up with MSIE and Flash.

Re:The Chrome Distortion: how Chrome negatively alters our e... by swiley on Saturday March 26, 2016 @11:59AM (#11366099)
Opera works great on android (although I guess it's still largely WebKit based)
Re:The Chrome Distortion: how Chrome negatively alters our e... by johansch on Saturday March 26, 2016 @12:05PM (#11366127)
Opera on Android is 99.9% Chrome, with a different UI (which I designed together with a colleague when I worked there).

The differences in non-UI code mostly relates to memory usage optimizations - most of them should be upstreamed by now though.