Camino 1.5
Mac users have a dizzying array of web broswers to choose from, which makes finding a favorite a tricky thing. My browser of choice has been Camino for a long, long time. It just looks like a Mac app, and it uses the Gecko rendering engine so I get all the goodness of FireFox …
Context & Ripple Effects
Camino 1.5 lands at a moment when Mac users genuinely have to choose between browsers rather than default to one, and this reviewer's pick has long been Camino precisely because it refuses to trade one virtue for another: it wears a fully native Mac interface while running on Gecko, the same rendering engine Firefox uses.
The release is documented in detail on caminobrowser.org the same day, which matters because Camino occupies a specific niche in the 2007 Mac landscape — it is neither Apple's bundled Safari nor Firefox itself, but a third path built by borrowing Mozilla's engine and wrapping it in Cocoa-style chrome.
First-order effects
- Mac users weighing Safari, Firefox, and smaller alternatives get a refreshed option whose pitch is unchanged: Gecko-level page rendering without giving up a native-feeling Mac application.
Second-order effects
- Mozilla benefits indirectly every time a Camino user loads a page, since each non-Firefox deployment of Gecko extends that engine's footprint on macOS against Apple's WebKit-based Safari.
Third-order effects
- If the pattern holds, Mac browser competition shifts from who owns a rendering engine to who integrates one best — engines like Gecko becoming shared infrastructure while differentiation migrates to interface polish and platform fit.
The trend: Mid-2000s Mac browsing is consolidating around a handful of shared rendering engines, with independent browsers like Camino competing on native integration rather than core technology.