Re: [Slashcode-general] Jumping in here late ... Slashcode is Dead ...

[W. S. L. I. <sc...@gu...>]

The fact that almost _no one_ uses it in production anymore is kind of a
clue... Even _Debian_ has moved totally away from 1.x for Apache. I
realize that you guys don't care so much about the rest of us, as has
been stated several times by Rob on many different occasions and posts,
but at some point you guys will likely end up having to upgrade, right?
Is there any time frame or roadmap for that for /.? I'm really leery of
advocating a fork where it's really not necessary, and where the
community would gain no benefit, but at the same time that's basically
what we'd have to do in order to get it working on Apache 2.x at this
point.

Support for databases that don't silently eat your data would be nice,
too, I.E. PostgreSQL.

On Mon, 2009-09-21 at 10:42 -0700, Chris Nandor wrote:
> There's no need for newer perl, mysql, or, IMO, Apache.

-- 
W. Scott Lockwood III <sc...@gu...>
LRSE Hosting