K-Meleon :: Extensions

Extensions : K-Meleon Forum

All about K-Meleon extensions.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=disrupted]
actually neither.. qtweb now is the better webkit browser for windows, arora used to be my favourite but it's quite behind.

from a non-bias view, kmeleon comes first because gecko is a better engine than presto.. opera comes second mainly because it still supports win9x and more feature-rich than the webkit browsers.

chromium clones are inferior to google's chrome.. i know they are better when it comes to privacy but from technical point-of-view, chrome is better built and more stable than the derivatives.

programming-wise, ie8 is way ahead than chrome and webkit browsers but it has the disadvantage of the trident engine. trident 4.0 isn't too bad as a rendering engine, it's much more standard-compliant than previous tridents and remember it has many parts from the tasman engine, the original engine for ie5 for mac systems.. nack then it was considered the best in standard compliance and was the only serious offering for mac  but the problem with trident is not rendering but the vulnerabilities which makes it a headache and a big no-no.

the only thing going for chrome & its cronies, is the v8 js engine because it's quite fast and that appears to be the current craze in the browser wars/fanboy cults..it's not stability or features or responsiveness or resources, it's all about the js speed and how browser x scores in benchmarks compared to browser y.. suddenly browsers are nothing more than graphic cards
 
iron se, chromeplus etc have worse redraw problems than google's, more prone to crashes..if you know how, you can crash them in 1  second, maybe a regular user won't crash it so easily but if you can crash a browser due to something completely unrelated to the website or a plugin..just because you exposed its guts, that shows how poorly coded it is. chromium clones are like a battered old car; one speed bump and it breaks apart

the problem with skinning api is you either do it perfectly and without a flaw or you don't. skinning has been around since windows 95, it's nothing new  but there's a big difference between skinning a notepad application or an mp3 player with a static window content  and a browser which has to handle a lot in its constantly changing window..it's just stupid

here are some nice snapshots of iron and chromeplus

the browser separates in 3 pieces after a quick restore/maximise: statusbar gets stuck at the bottom, the main window breaks off from the titlebar which insists to stay maximised
[img]http://kmeleon.holaservers.com/disrupted/iron1.jpg[/img]

oops, my boobs are showing:
[img]http://kmeleon.holaservers.com/disrupted/iron2.jpg[/img]

titlebar breaks off the main window frame after dragging it across the screen-too fast for the skin..still can't decide where the window went and ofcourse the boobs  spill out from the skin
[img]http://kmeleon.holaservers.com/disrupted/iron3.jpg[/img]

naturally all this rubbish will lead to this:
[img]http://kmeleon.holaservers.com/disrupted/chromiumcrash.jpg[/img][/quote]

K-Meleon forum is powered by Phorum.