Switch to OS X Jaguar
- Started
- Last post
- 24 Responses
- chl0
3cY:
Gecko is slightly slower than KHTML, but not by much I don't think. However, the standards support for proper handling of XML, CSS, CSS2, etc. is vastly superior in Gecko.
I'm not trying to knock KHTML here. I think that team has done an amazing job considering the fact that it's mostly non-paid work (KHTML was developed for the KDE browser Konqueror), but the Gecko renderer is better than anything else out there. including KHTML, Opera, and IE in terms of standards support.
- unknown0
ah...
hence the screwed up form css and the likes...
and testing my XHTML/CSS2 sites brings up weird issues as well...
oh well, it is still a beta.
thanks for the explanation, Chris.
- chl0
No prob. I've heard that there's some hope for the XML issue. Specifically, I guess it works properly in KDE, but there's something that still needs to get ported to OSX for it to work on Safari. But at least code already exists somewhere that will do it.
As for the CSS... well...
And just FTR, I've always thought that for pure speed of page rendering Opera was fastest. Though I'm not sure it's available for Macs of any kind.
- monkeyshine0
Jaguar works like a dream for me on my 550mhz Tibook. I use Dreamweaver 4 still as well as Illustrator 8 and Jaguar is pretty fluid between OS9 and X. OSX1 was terrible.
Safari...sht. its hard enough to code and test for everything else out there..something new!?!?! NOOO!