#webkit

On the topic of huge iOS changes, here’s Mike Beasley:

When iOS 7 launched, developers discovered that their apps with built-in web browsers were unable to achieve the same level of JavaScript performance as the stock Safari app. This was because Apple restricted use of its improved Nitro JavaScript engine to its own app, leaving third-parties with a slower version.

As of iOS 8, however, it seems that decision has been reversed. All apps will now be able to use the same improved JavaScript engine that powers Safari. That means Google’s Chrome browser on iOS will now be just as quick as Safari, as will the pop-up browsers embedded in apps like Twitter and Facebook.

Unclear why this wasn’t always the case. But glad that it appears to now be the case. Next up: wondering if the rendering engine restriction will ever change…

lilly

lilly:

What we know for sure is this: monocultures always make more & faster progress in the near term when they’re stewarded by strong, vibrant leaders. But over time you get stuck. Companies change, sensibilities change. And then you’ve got all the technology, and all talent, and all of the best thinkers, all trapped on one technology stack.

Good thoughts.

A pretty damning report from Brian X. Chen for The New York Times. It essentially says that Palm and then HP were incompetent with their building and management of webOS.

But even more damning may be what it says about the “web versus native” debate. Quoting Paul Mercer, the former senior director of software for Palm:

“If the bar is to build Cupertino-class software in terms of responsiveness and beauty,” he said, “WebKit remains not ready for prime time, because the Web cannot deliver yet.”

This is interesting since Apple itself was vital in the development of WebKit and still uses it as the backbone of Safari. But consider this: when the iPhone first launched in 2007, Apple tried to get third party developers to make web apps for the iPhone since there was no native development SDK. A year later, they backed down from that and released the framework that created the most important element of the iOS ecosystem: third-party native apps.

It’s perhaps a bit too simplistic to say, but Palm didn’t have the luxury to pivot to native because “native” for webOS is the web. And Mercer argues that it’s still not ready to match native app development — a topic which is entering its fourth year of debate.

I can’t speak from the developer side of things, but all I know is what I see as a user: native apps still destroy web apps. Starting this week, I’m sure we’re going to hear how that’s poised to change (yet again) in 2012. But I doubt it. And that’s why webOS is still screwed. 

The guy who had been doing the absolute best weekly Chromium/WebKit rundowns has been scooped up by Google — to work on yes, the Chrome team. Very savvy move by them.

Sadly:

Right now I have the liberty to write about anything I find, seeing that I don’t have access to internal information. As this is going to change, I’ll have to be a lot more careful about the things I write about.

Chromium is fully open source — but Chrome itself is not, remember. Though I’ve been told that’s mainly for licensing/marketing purposes. As in, Google doesn’t want people to peddle crap with the Chrome name/logo.

Like the Cr-48.

Zing! Ouch. Sorry. Trackpad is getting better with each update. Machine still way too slow though.