Well, I am among those of you who've used LJ for years. :) I migrated off a very homebrew blogging solution in 2002, and I'm actually an LJ permanent account holder, which is in no small part one of the reasons I'm not rushing to move.
I don't have derision for the code base, per se, but it is what it is -- "familiar" and "extensible and maintainable" aren't always congruent. It was my feeling when I wrote that post that it would be easier to do something like what Six Apart did with Vox than it would be to bring the old LJ codebase up to where I suspected it needed to be. (Vox seems to have been a failure, but I think that's been a matter of 6A really not figuring out how to reach the market they were trying for -- or possibly that market just not having actually existed.) The Dreamwidth developers took the tack of starting with the old LJ base, though, and they've done really well at proving me wrong. And to give credit where it's due, SUP hasn't been standing still, either; LJ does more now than it did in 2008, and DW benefited from that, too.
no subject
I don't have derision for the code base, per se, but it is what it is -- "familiar" and "extensible and maintainable" aren't always congruent. It was my feeling when I wrote that post that it would be easier to do something like what Six Apart did with Vox than it would be to bring the old LJ codebase up to where I suspected it needed to be. (Vox seems to have been a failure, but I think that's been a matter of 6A really not figuring out how to reach the market they were trying for -- or possibly that market just not having actually existed.) The Dreamwidth developers took the tack of starting with the old LJ base, though, and they've done really well at proving me wrong. And to give credit where it's due, SUP hasn't been standing still, either; LJ does more now than it did in 2008, and DW benefited from that, too.