On Fri, Aug 30, 2013 at 03:41:18PM +0100, Simon Slavin scratched on the wall:
> The arguments against DLLs are not the normal arguments you see, > they're governed by an unusual combination of four characteristics of SQLite: > > A) SQLite is very much liked, and a huge number of programs use it. > B) SQLite is tiny. You don't waste much disk space by having lots of copies. > C) There are frequent version updates to SQLite which introduce new > facilities. > D) SQLite is detailed and complicated, so updates sometimes break > assumptions made by programmers. I'm not sure that last one is fair. Generally, the SQLite team makes a huge effort to avoid breaking backwards compatibility, both documented and assumed. There are a whole list of known bugs that will never get fixed because they might break existing applications. While there are some changes to the query optimizer that sometimes do odd things, overall this is a pretty poor reason. For me, the biggest issue is A and B, combined with the fact that many applications that very heavily use and integrate SQLite often have a custom compile with specific extensions, default values, and features turned on or off. An application that uses SQLite for its document format, for example, is going to be very intimately tied to their particular configuration of SQLite. It is much easier to just integrate that fine-tuned build directly into the application. The amalgamation encourages this. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
