The difference between 10.4 and 10.8 is seven years. That doesn't seem like an outrageous amount of time to break compatibility.
Forever? At least the linux kernel has an explicit goal of never breaking userspace. That doesn't mean other parts of userspace don't break themselves, but the linux kernel has as a development goal to never break binary compatibility for userspace.
But I still admire the kernel for their stance even if it can't solve every compatibility problem.
Of the new software that still claims XP compatibility, much of it requires SP3.
So actually, XP = XP SP3.
Unless you're a large organisation paying a lot of money, you aren't likely to get 5 years of support for a particular version of most products.
http://support.microsoft.com/lifecycle/?LN=en-gb&C2=1173 http://www.microsoft.com/en-us/windows/endofsupport.aspx
I think there's some good precedence for that with Firefox who (still?) deliberately broke all their extension compatibilities on every release, and contrary to that Wordpress who've led to a fully automated exploit ecosystem.
#Supporting older versions is a pain. Supporting all features in older versions AND newer versions to work together is an even bigger pain. Example: Wordrpress.
#Compatibility for older version leads to bloated code, with too many legacy variables, too many points of failure. Example: Wordpress.
#Evolution of any software requires that it discards old ideologies and embraces the newer ones. The ones that don't do, tend to drift away from the main goals. Example: Wordpress.
Wordpress was started with the exact same intention as Ghost and yet, what you are left with now is a half-baked unstable CMS, and a half-baked blogging platform that breaks old plugins with each upgrade.
If you want to embrace progress, then you must embrace C.H.A.N.G.E. And this is not just for software.
I want a frozen codebase that only worries about critical security updates.
In the real world, you will break your site by adding new plugins every few months. The site will break. I get a stable codebase and I sit on it.
Development causes bugs! Milestone releases are what I want.
> In the real world, people need compatibility more than they need whatever cleanup you're able to do by breaking compatibility.
Here's the thing: if you're a user that needs compatibility don't upgrade! (not an option with most blogs) If you're always adding new functionality and plugins to your blog, things will break. If your business needs constant new web technology updates, use a real CMS and fix them when they break. They will break, they always break.
I have used plugins that haven't been updated for four years without any issues.
Of course, one way to achieve this is less reliance on add-ons, so you have less API surface to expose. Having a usable WordPress install relies so heavily on add-ons that it's kind of pointless to consider WordPress alone.
Time and time again, rolling software has proven to be more secure than static releases. A plugin from five years ago that hasn't been maintained in that time is probably going to hurt you a lot.
When you have constantly breaking API changes, and then someone has an essential plugin that's unmaintained, then they're a lot more likely to stay with your old, buggy, insecure base package, rather than finding someone who knows how to update their plugin (remember, most users aren't programmers, and most have installed plugins for a reason).
What you do is try to minimize the API surface that plugins have so it's easy to maintain backwards compatibility, and minimize the impact that older plugins can have by keeping them reasonably well isolated.
Hopefully a lot.
Unless it just does some simple, or basic thing. In which case, you're still hurt. But in a different way....
The other way around is different, of course, as as a huge number of new APIs have been added since then.
The Ghost admin panel doesn't allow editing themes, the post doesn't have buttons that allow you to quickly format posts, there are no SEO options/plugins, there is no theme editor that allows editing of themes, no sidebars, no multi-user creation, no e-mail to post, etc. Too many features are missing and this is very simple. WordPress is better, there just is no debate on this right now.
Also, we are talking ~37k lines of code, not exactly something you can write in a week or two for $500.
In the real world, people need compatibility more than they need whatever cleanup you're able to do by breaking compatibility. Heck, in many cases you can get both by doing your rewrite but leaving a compatibility layer on top that gives you the compatibility that you need.
I'm so sick of trendy "modern" frameworks like Rails that break compatibility every 5 minutes, and listing breaking compatibility as a major feature is a huge turnoff.
How about focusing on spending the pre-1.0 releases iterating and designing a really good API that will be amenable to backwards compatible extensions, and then sticking to that API and backwards compatible extensions to it for the forseeable future?