After more than 11 years, development on the open-source Camino Web browser has ended. Back in the dark ages of Mac OS X, before Safari and Chrome, the Camino Project was established to graft a Mac-native interface onto Mozilla’s Gecko rendering engine. Many of Camino’s developers were later hired by Apple and Google to work on their respective browsers. Web browsing on Mac OS X wouldn’t be what it is today without Camino, and for that, we thank the developers, salute them, and wish them the best in whatever they do next.follow link
Thoughtful, detailed coverage of the Mac, iPhone, and iPad, plus the best-selling Take Control ebooks.
Schedule Fetch to Work Automatically
Although Fetch doesn't have a built-in scheduler, you can use iCal along with Fetch's Mirror command or Automator support to automatically upload or download files at a specified time. To find out how...
- ExtraBITS for 3 June 2013 (03 Jun 13)
The End of the Line for Camino
Sad to read this. Until a year or so ago Camino was my main browser. I started using it when it was called Chimera. Now I use Chrome and wonder how much data Google is collecting from me.
This is sad news, indeed. Camino was my browser of choice for many years. Firefox was bloated and a memory hog, Chrome a bit too intrusive, and Safari (without the Debug/Developer menu) not very reliable. Firefox still requires restarting from time to time, and the others have improved, but Camino always struck me as a "real" Mac browser.
Sad. I still use it for some sites. It was my main browser for many years.
I've long used Camino as my clean test browser; I imagine it will continue to work in that role for some time, though eventually I'll need to switch to Opera or the like for something that can be completely reset for testing.