[shadowfyr]

Well, yes and no. The problem is, different drivers, different security models, etc. Too much of it *not* kept separate enough that user privilege escalation didn't land you in the core of the mud code, if it broke, and other similar issues. Stuff that should have been in the driver was in the library, stuff that should have been maybe, at least handled more gracefully, by the library, relied instead in the driver too much, almost nothing was standard, and anything that was often wouldn't work, for various reasons, under certain configuration or one certain OSes. And even basics where often added much later than the example code, so that even if you had discussions or tutorials, someone using Lima instead of TMI would be looking at you like you where trying to describe Lua code on Windows to them, while you where using Java on BSD. Not even enough of the function names would necessarily be recognizable to figure out what was going on (and even if it had the same name, it might not do the same thing).

I think, if you wanted to fix the issues LPC has, you would need to start from the ground up, and put things where they need to be, provide different access for different parts of the code (instead of trying to cludge some of the goofy security methods used in the past) and generally try to come up with some standard model for how the most basic features need to work, so that modifications are just addons, not complete rewrites of stuff that a 10 years later will be unrecognizable as deriving from the same library. Discussion and tutorial is useless without a common frame of reference.