At Fog Creek Software, we're very careful about saying publicly what we're planning for the future. Is this because we are delicate geniuses who must not be held accountable to our fans and users?
We hate to be in the position of making promises that we find out later on we can't keep. Breaking promises is a recipe for eroding trust.
Software is a tricky business. Too often, after having embarked upon solving a problem, we later find out that two things we'd like to do are in direct conflict. We might also find that the challenges involved in implementing a given feature are too great given the possible benefit; our time might be better-used elsewhere. And all that assumes that our product operates in some sort of vacuum. While we were busy implementing one feature, a shift might have happened to make a different feature the right one to do next.
Without public promises, we get through these adjustments and difficult decisions as best we can. It's the nature of the business. When we make public promises, though, we have to decide which segment of our users we have to disappoint. We have to explain our decision, and end up alienating our user base.
We'd rather ask our users to live with same uncertainties that we operate under than give them a false sense of certainty that we might later have to destroy.