>>28
Although
replying to trolls will just
make them stronger,
doesn't render the CSS height class correctly.
I can't comment on this but I hear much worse complaints about the other browsers.
constantly makes version breaking changes to its awful rendering (see: legend tag).
What's a “version breaking change”?
has more security vulnerabilities than IE (look it up faggot).
But it attracts less attention. Good luck exploiting my minefield nightly build. Specially since it's unlikely you'll be in my NoScript whitelist. In any case, if you really care about security, it does allow you to do more stuff than the other browsers to try and protect yourself.
still memory leaks.
[citation needed] - It works great for me. Specially since some of the stuff in 3.0 hit, such as storing the images compressed on their original format, so opening a page with 10MB of JPEGs will only end up consuming 10MB of RAM, instead of the hundreds of megabytes you'd get elsewhere. I've run very long and hard sessions, with literally hundreds of tabs open, and memory management has never been an issue. I really think it does great, better than IE and Opera for sure. Chrome is interesting because it actually terminates the processes freeing everything, but that model isn't really useful with 100 tabs open since it's limited to 20 processes.
continues to poorly implement drafts specs.
Can't comment on that one, but really makes me wonder how, say, IE fares in that respect, since last time I checked it was still missing a lot of basic stuff, such as SVG (yes,
shit sucks, but people still want it so
enjoy your Flash shit).
is in perpetual beta requiring updates very few weeks
The 3.0 series hasn't seen a lot of releases, in fact, less than one very month (this is relevant because that's the rate MS packs fixes together). And installing them is pretty painless and doesn't require a
FULL SYSTEM REBOOT and assorted continuous nagging or dataloss scenarios that are typical in other
ENTERPRISE-QUALITY update solutions.
isn't above version breaking changes that make all plug-ins stop working
I think you are mistaking
extensions and
plugins. The great versioning system it has is to preemptively prevent trouble, you can disable it and 99% of the
extensions will, in fact, work perfectly. Otherwise you can have it the IE way: lots of crashes until it hits the topcrash list and MS releases an update to blacklist the older versions. In any case, due to the nature of
extensions, this is not really fixable without basically anchoring the browser forever. Also, when comparing update hassle, you should consider that IE has been basically frozen for a fuckton of years, and new versions when they do come out have similar problems.
is slow despite the "benchmarks"
When people misreport Acid3 scores because the test freezes for over a minute and therefore seems to have finished, you know you're really in trouble. In all seriousness though, I do believe in general it's faster on most stuff, and you can tweak it (mostly network settings, also rendering) for it to be as fast as you want. Some extensions also contribute to improving performance via selectively blocking crap (ads and even javascript) - this is hardly an exclusive feature though. Its single-threaded architecture is a problem though, IE and Chrome have a clear edge there.