Discussion with Bukkit Devs

<CaptainLepidus> Amaranth, having a discussion with someone about replacing the vanilla server with Bukkit. What would your view point be on this? (it probably won't happen, but I'm interested anyway)
<Amaranth> CaptainLepidus: You mean having Mojang pull in CraftBukkit/Bukkit and call it the official plugin API?
<CaptainLepidus> Indeed.
<Wolvereness> No...Pulling Bukkit/CraftBukkit.... no...
<Amaranth> CaptainLepidus: Excuse me while I roll on the floor laughing
<CaptainLepidus> I'm intrigued. Why are you opposed to the idea? (Not that I'm not...just interested in your ideas.)
<Amaranth> Our API sucks in a lot of ways and in a lot of places our implementation isn't much better
<Wolvereness> Craftbukkit / Bukkit was rushed, and many features were written in terrible ways...The methods in the scheduler make me want to cry...
<CaptainLepidus> But is it not superior to having zero plugin support?
<Wolvereness> CaptainLepidus: you don't quite understand the implications of grabbing Bukkit and calling it a day
<Amaranth> CaptainLepidus: I'd rather vanilla have nothing To start with a vanilla plugin loader should completely isolate plugins (and their dependencies) from each other and use the security system to lock down what they can do, including poking in to minecraft internals
<CaptainLepidus> So you see Bukkit as a freer alternative to vanilla, then? With less security, but perhaps more capability?
<DarthAndroid> the fact that you *have* to poke into the internals to do so much stuff is a sign of design flaws and one of the reasons why it's not an answer to "Minecraft Mod API" but that's the problem with anythign built off of vanilla (as CB is) - there's just not a whole lot of other options
<Amaranth> CaptainLepidus: No, I see that as a failure of our plugin loader