4 ms·
Look at it this way: SQLite3 is (more or less) slowly becoming SQLite4, except for the parts that did not work out. It is not as shiny, but in the long run, yo
by krylon 9y ago
Look at it this way: SQLite3 is (more or less) slowly becoming SQLite4, except for the parts that did not work out.
It is not as shiny, but in the long run, you still get all the goodness. Nevermind the name / version number.
- jandrese 9y agoIt's basically the Perl 5 of the DB world.
- jzawodn 9y agoPerl 6 you mean?
- tripa 9y agoI read that as: it gives the impression it's been here forever, it's still being actively maintained, and will be for the foreseeable future. Benefiting from the “future” (sqlite4/perl6) at a slow but steady peace. So, really like Perl 5.
- mst 9y agoperl5 has been stealing a bunch of stuff from perl6 and is still actively maintained and doing a major release with new features annually - also continues to Just Work with an extreme commitment to backcompat. So I'm pretty sure he did mean perl5, and as a happy user of both perl5 and sqlite the comparison seems apt.
- rurban 9y agoNot at all. perl5 is horrible tech, with no development and being actively destroyed by its maintainers. Whilst SQLite3 is at the very top of its class, with lots of new features, and very well maintained.
- mst 9y agoFor context, rurban has had a long-ongoing feud with the perl5 maintainers that eventually resulted in his removal from the mailing list for being unwilling or unable to disagree sufficiently civilly to hold an effective discussion when people felt he was technically incorrect. He's also, OTOH, a technically brilliant developer whose positive contributions will be missed. (also if you ever run into him at a conference, I'd recommend grabbing a beer with him, I've always enjoyed doing so in spite of our spirited disagreements over various things)