4 ms·
Of course Safari loads faster than Firefox on OS X, as IE loads faster in Windows. Their libraries are preloaded by OS ... Native apps for each platform may gi
by lamnk 17y ago
Of course Safari loads faster than Firefox on OS X, as IE loads faster in Windows. Their libraries are preloaded by OS ...
Native apps for each platform may give performance boost, but maintaining a consistent UI will be a lot harder
- blasdel 17y agoThat's the point: we don't want consistent UI If we want native UI, it's obviously going to have major inconsistencies between platforms!
- __david__ 17y agoWell that's not 100% true because the main interface for Firefox on Mac OS X looks more like Safari than it does Firefox on Linux. I think they've actually done a really good job making it look like a native app instead of just a port from some other OS.
- lallysingh 17y agoBut users still pay the runtime startup costs for not using the native libs.
- blasdel 17y agoIt's not about looks, but about behavior. Fun Fact: In Safari since version 3, the <input> elements aren't actually native widgets anymore, as NSButton et. al. couldn't support a bunch of the CSS attributes. They are now rigorous behavior-level reimplementations! A widget that looks native but behaves differently is terrible! At least when it looks alien you don't expect it to behave natively.
- andrewtj 17y agoWhilst that sounds reasonable on my VM Safari loads faster than Firefox on Windows.
- DrJokepu 17y agoYou know, I remember the times when Firefox was called Firebird and Phoenix and I adored it for loading way much faster than IE. It's surprising how much FF changed since then.
- rbanffy 17y agoIt would be unfair to say it's all due to Firefox and nothing due to improvements on IE (like pre-loading stuff on startup)
- DrJokepu 17y agoThe old Mozilla Suite had a start-up preloading tool as well if I remember correctly. Still, Google Chrome loads up way much faster than either IE or FF without preloading anything at all.
- rbanffy 17y agoI think Chrome has something that preloads stuff. Starting it right after login takes a lot more time than if you start it a couple minutes later. I don't think it's all due to the heavy activity a Windows login takes.