Live data from Hacker News

Camino browser reaches its end

caminobrowser.org

21–30 of 127 posts

Re: Camino browser reaches its end

#22

Earlier quoted context omitted.

IE for Mac? That has to be an oxy moron of some sort.

It also was the most standards compliant and performant IE of its time, being a totally different code base.

Possibly because they had to please Apple AND Microsoft?

Re: Camino browser reaches its end

#23
post #3

I loved Camino back in the 10.1 / 10.2 days. It was truly epic , and so much better than the god awful IE for Mac.

IE for Mac? That has to be an oxy moron of some sort.

For a surprisingly long window of time, IE Mac was the best browser around. Apparently, it did not share a code base with Windows IE, which explains why IE Mac had all the features people were drooling over in 2001 like full PNG transparency and good CSS support. PNG support even included color correction, and IE Mac did not suffer from the "box model" bug that affected IE on Windows.

I think the Mac version of IE had something like 99% compliance on the first Acid test, before other browsers had robust CSS support. You could even find a copy of the Acid test in an easter egg in the browser.

It was a fantastic browser at the time, but didn't align with Microsoft's future interests and the development team was reassigned.

Re: Camino browser reaches its end

#24

Earlier quoted context omitted.

I want to like Firefox, I really do, but the experience on OS X is awful. It doesn't fit well with the aesthetic of a native Mac app, and certainty doesn't' function like one. Multi-gestures in Safari are so much smoother. About a month or so back when the Firefox team was soliciting feedback for something here on HN, one of the designers or developers at Mozilla had screenshots of a version of Firefox that looked re…

did it look like this [1]? that's the UX nightly available at [2]. it's a new theme they're working on, but it's got a few versions to go before it makes it into stable. i'm loving it, but they're removing/changing a couple of customization features so people are freaking out. we'll see what the final product ends up looking like. [1] http://i.imgur.com/Gfns2MS.png [2] http://people.mozilla.org/~jwein/ux-nightly/

It's not just the user interface, it's that (for example) they don't QUITE completely ignore mac (emacs) keybindings (e.g. ctrl-a should move to beginning of PARAGRAPH, but either moves to the beginning of the visual line in the textbox, or highlights whatever you've searched for if you're that unlikely). This is far worse behavior, and it's been like this for years!

Re: Camino browser reaches its end

#25

Earlier quoted context omitted.

IE for Mac? That has to be an oxy moron of some sort.

For a surprisingly long window of time, IE Mac was the best browser around. Apparently, it did not share a code base with Windows IE, which explains why IE Mac had all the features people were drooling over in 2001 like full PNG transparency and good CSS support. PNG support even included color correction, and IE Mac did not suffer from the "box model" bug that affected IE on Windows. I think the Mac version of IE ha…

Yea, it was one of the first browsers to implement DOCTYPE switching.

Re: Camino browser reaches its end

#26
post #4

Well that marks one more end of an era. With Camino folding up and Opera going with WebKit - Camino too was on the way to this with Gecko being out of the question - the browser field is getting to be a one-horse race (since all the cool kids are going with Chrome these days).

That's news to me.

Re: Camino browser reaches its end

#27
post #4

Well that marks one more end of an era. With Camino folding up and Opera going with WebKit - Camino too was on the way to this with Gecko being out of the question - the browser field is getting to be a one-horse race (since all the cool kids are going with Chrome these days).

Arguable. Jolla uses Gecko with IPC embedding for their upcoming browser for Sailfish. Gecko is in no way out of the question. Mozilla are also working on the new Rust based browser engine (Servo).

Re: Camino browser reaches its end

#28
post #2

I find this extremely saddening because Camino offered the best native experience for OS X, with all the polish of a well-designed Cocoa app, on top of Gecko. I'll miss Camino.

I want to like Firefox, I really do, but the experience on OS X is awful. It doesn't fit well with the aesthetic of a native Mac app, and certainty doesn't' function like one. Multi-gestures in Safari are so much smoother. About a month or so back when the Firefox team was soliciting feedback for something here on HN, one of the designers or developers at Mozilla had screenshots of a version of Firefox that looked re…

I would have to agree with most of what is said here. I prefer Chrome (or even Safari) over Firefox on OS X. Chrome is faster (I need to work on a slow Internet connection many times) while Safari being the bundled browser has few features like Reader etc. which I don't want to use. I still have FF installed for back up purposes but I don't use it unless something is broken on Chrome or Safari (which doesn't happen a lot).

I find it extremely surprising that some sites (ex:Facebook) are (or were a few months back) displayed differently on Windows FF vs OS X FF.

Re: Camino browser reaches its end

#29
post #19

Earlier quoted context omitted.

My opinion is that Google/Mozila is pushing HTML5 instead of plugins not because that's what's best for the web, but because exactly this-- it decreases the potential for competition.

They must be quite bad at it, because both their browsers are split into components that can easily be reused in competing products.

The whole reason Camino has been discontinued is that the components that make it easy to reuse Gecko in their competing product were removed from Gecko.
Post reply on HN