Camino is no more. The website now only displays a brief message:
After a decade-long run, Camino is no longer being developed …
Camino has been my first choice for browsing the web for a very long time. Some time after the release of Firefox 1.0, as I realised that the Mozilla project would never make Firefox a real Mac OS X citizen, the choices were rather limited. There was the early Safari, iCab or Omniweb. For various reasons, Omniweb never fitted in my workflows, neither did iCab. Back then, Safari still had many shortcomings in rendering webpages, and – major sin amongst all sins – it sported a brushed metal UI. Camino it was, then. It was the browser for the “rest of us” (to paraphrase Smokey Ardisson), fast, lightweight, build for OS X from the ground up, with an impressive pédigré –
Former Camino developers have helped build … Chrome, Firefox, and Safari. Gradually I got involved in helping out with support requests and debugging, later taking up the challenge of massaging pixels and colours to look pretty on icons and helping to fix myriads of small and bigger issues on the website.
But over the years, due to a dwindling number of contributors (the rise of iOS can partly be blamed for this…) and the increasing complexity of building a web browser, this all-volunteers project had a hard time keeping up with a competition that could rely on a large pool of paid developers. Then came the death knell with the Mozilla project announcing the end of Gecko embedding. Unfortunately, an attempt to use the WebKit rendering engine didn’t pan out.
Volunteering with the Camino community, working with the project leads and all the other contributors has always been a great experience. Even though the development has ended, Camino has succeeded in it’s purposes: from providing a great web browsing experience on Mac OS X when there was very little choice, to putting in motion the development of the many browsers available today. Thank you for this and that.
Ciao Camino. Rest well, old friend.