In defense of Firefox

There's a lot of satisfaction to be had in reflexively ranting about things and slamming on
them.  In my experience, there is ultimately more satisfaction -- just of a slower and less
instantly-gratifying sort -- in learning and building.  Unfortunately, the two approaches are
often at odds, because one is fundamentally about protecting one's preconceptions, while the
other requires with-holding judgement and seeking out ways to challenge them.  In this case,
you're being factually wrong, utterly ignorant of the relevant technical issues, and actively
hostile to changing either -- but you do probably *seem* smart to some readers, and that's a
choice you can make.  Many technical people do.  YMMV.

@jch: Please do some research before posting. SqlLite doesn't pretend to be an RDBMS. It
doesn't support (enforce) basic datatypes. The shared library is ~1MB on my system (and can go
down to ~100K when embedded and features removed).

Yes, it supports "strong integrity guarantees". The opposite of that is called "corruption".
If you wrote a browser, would you just call "truncate(bookmarks); write(bookmarks, data);
close()"? I hope not. You would need to design a fail-safe recovery mechanism that doesn't
loose data. It might be fairly simple when updating bookmarks, but for storing browsing
history and doing indexing, you'd basically be re-writing most of SqlLite anyway.