Feeds

Apple store kneecaps rival browser

Bookmarklets considered harmful

Boost IT visibility and business value

Exclusive Apple has ordered the developer of a web browser for iPhones and iPads to disable vital functionality. The gatekeepers at the iTunes store, which sells the highly rated browser German browser iCab, ordered it to disable Javascript. The developer says he'll comply.

iCab was launched two years ago, and brings many more features to iPhones and iPads than the vanilla Safari shipped with the device. It also ships with around 25 "modules", which are used to ease integration with services such as Twitter. They are documented here. iCab's "modules" are simply Javascript code.

The developer Alexander Clauss says he'll comply with Apple's wishes by disabling third-party code. But he's puzzled by the Jobsian logic.

"I really can't say that I like Apple's decision, and technically it doesn't make much sense," he wrote on the iCab blog. "'Modules' for iCab Mobile are simply a more comfortable variation of bookmarklets, and these are still allowed by Apple (and I assume Apple cannot forbid that the user will save and use bookmarklets)."

iCab on the iPad – click to enlarge

He continued: "Maybe if I would have called the modules 'smart bookmarks' and would have made installing them much more complicated, Apple would have never asked to remove the ability to download them from the internet ... The great user experience of installing modules has probably created a suspicion that these modules are more than just a piece of JavaScript code. From a pure technical point of view, if Apple does not allow to download modules (JavaScript code), Apple would also have to disallow to load web pages in general, because these do also contain JavaScript code."

At one level, it really isn't so surprising. Apple forbids third-party code interpreters, such as Java or Flash, from being delivered through the App Store. And Javascript is a code interpreter. Apps such as Instapaper make quite a lot of use of Javascript – but it must use Apple's Javascript engine, not anybody else's. iCab uses Apple's WebKit for rendering pages.

You can find iCab here.

iCab has a long history. It started out as CAB on the Atari, moving to the Mac in 1999. It was the only browser in development for the original MacOS, long after every one else had moved on. Clauss released a Cocoa version for Mac OS X three years ago. ®

5 things you didn’t know about cloud backup

More from The Register

next story
Why has the web gone to hell? Market chaos and HUMAN NATURE
Tim Berners-Lee isn't happy, but we should be
Linux turns 23 and Linus Torvalds celebrates as only he can
No, not with swearing, but by controlling the release cycle
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Sin COS to tan Windows? Chinese operating system to debut in autumn – report
Development alliance working on desktop, mobe software
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
This is how I set about making a fortune with my own startup
Would you leave your well-paid job to chase your dream?
(Not so) Instagram now: Time-shifting Hyperlapse iPhone tool unleashed
Photos app now able to shoot fast-moving videos
prev story

Whitepapers

A new approach to endpoint data protection
What is the best way to ensure comprehensive visibility, management, and control of information on both company-owned and employee-owned devices?
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Maximize storage efficiency across the enterprise
The HP StoreOnce backup solution offers highly flexible, centrally managed, and highly efficient data protection for any enterprise.
How modern custom applications can spur business growth
Learn how to create, deploy and manage custom applications without consuming or expanding the need for scarce, expensive IT resources.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.