Quote from Bjornke
This is unacceptable business practices. What on earth could you do to have some people decrease from rate by over 80% and THEN on the release notes claim "performance increases" That my friends is the worst business practice ever. Things like this actually cause lawsuits in the US when a business claims one thing and the end result is another. How I wish Mojang was in the U.S. they would have so many different business ethics laws they would HAVE to follow which sweden doesn't have.
Let me get this staright also: why is a update that adds just a handful of new features so detrimental to performance anyways? Why does their release software (they're NOT in Beta anymore folks) have soooo many bugs? The answer - Mojang has probably the worst suit of coders for java ever. I've never come in contact with an idie game or any game for that fact made in any language with soooo many bugs. There quality control is terrible. Mojang needs to get their **** together people. The honest truth is they are a terrible company with a good idea. What we need is a good company with a good idea.
And this is where the conflict of sanity came into play. The Dev team wanted to hold off until everything, including the mod API, was finished and stable. But with the length of the update being the longest in MC history, the player base started getting impatient and clamoring for a content release to keep them busy. So they pushed back several features they had planned, focused on phase 1 with the code base merger and added some content to help satisfy the masses.
Everyone who was involved with testing the snapshot knew it was buggy, and the release would had benefited from being delayed another 2 months or more to work out the odd bugs. But apparently that wasn't enough to stop a lot of players from getting the snapshot, despite the risk, just to mess around with the new content.... and then come here in a panic when something breaks.
I've been in a lot betas in my days, but this is one of the few instance where the community demands got everyone in over their heads. Then came the delicious tears of butthurt once people realized they were getting what they asked for, but not what they expected.... followed by the "the merger is the worst thing ever" threads, a couple months of rampant misinformation, and now an outcry for a roll back to a divergent code base because it worked better.