In 2009 RIM acquired TorchMobile which was the company I was working for. Due to the fact that I would be working on the WebKit library at RIM, RIM legal outlined various things I could/couldn't do on Arora. At the time I thought this would be less of a problem than it turned out to be. Development slowed and while today I merge in a patch here and there into Arora for all intents and purposes I have stopped developing Arora. For me personally the join of Arora was to push QtWebKit to its limits, to bring a WebKit browser to Linux, show that you can really have a multi platform app with Qt, and have fun. With the rise of Chrome and the fact that Chrome now runs on Linux (which I even helped get initially working :), being forbidden from contributing to Qt (Nokia and RIM are not exactly buddies), and not being allowed to develop any feature that didn't exist on another browser, the fun of Arora was zapped. What does this mean for the future of Arora? I am not sure, but so far no one has stepped up and said they want to keep it alive. Perhaps the QtWebKit devs want to take it over, or the Haiku devs or one of the various manufacturing companies (Arora was put on 30K TV's in Korea). If someone does come along and start taking over maintainer ship i'll transfer ownership of the GitHub account and the GoogleCode project, but with my retirement from the project there is a good chance that Arora might stay frozen where it is now.
I am proud of what Arora became. It is a decent solid browser with clean code. The development process worked well with only a few commits in the entire history that broke the build and the majority of components having unit tests and or manual tests. The best illustration of the code quality has to be when I discover code I originally wrote for Arora in other browser projects. Arora might have been missing features that FireFox or Chrome had, but the features it had were stable and worked. Which isn't to say it had no features, opensearch, click 2 flash, adblock, fast startup, translations, native theming, are just a few. Thank you to everyone who has contributed and made Arora what it is today I hope to work with you on future projects.
-Benjamin Meyer
Thank you for all your work on Arora, Ben! I never used Arora as my
main web browser, but it has been very helpful for me (as someone who
works on both client-side software and web development) to have another
clean, functional, effective browser in my toolkit.
Regards,
--dkg
I am formally announcing my retirement from Arora.
I have stopped developing Arora. and not being allowed to develop any feature that didn't exist on another browser, the fun of Arora was zapped.
I am proud of what Arora became. The best illustration of the code quality has to be when I discover code I originally wrote for Arora in other browser projects. ..that FireFox or Chrome had, but the features it had were stable and worked. Which isn't to say it had no features, ... adblock, ..
I hope to work with you on future projects.
-Benjamin Meyer