On Thu, Mar 05, 2015 at 06:52:20PM +0100, Marc Espie wrote: > > On Thu, Mar 05, 2015 at 06:11:31PM +0100, Ingo Schwarze wrote: > > > By the way, lynx(1) removal doesn't really hurt that much. > > > Rotten code that will hurt more when it will finally be deleted > > > includes, for example, the sqlite3(1) library and file(1). > > > > re: sqlite, the code doesn't follow our guidelines, but it's not that > > badly rotten. I've played with it a bit, and as long as you use it for > > what it's meant (sql), it's pretty sturdy.
> I concur. And the sqlite devs are also reacting quickly to bug reports. > The very few times new sqlite releases caused a regression in SVN the > problem was fixed promptly. > http://article.gmane.org/gmane.comp.db.sqlite.general/66248 > http://www.sqlite.org/src/info/4c86b126f2 Reactive is not the same as proactive. The code uses risk-prone idioms.
