Hacker News new | comments | show | ask | jobs | submit login

At this stage I think a fork is needed, the work needed to change the core, the people behind WordPress just won't get behind.

Unrealistic for software that powers over 20% of all new websites. Also, a bit presumptuous of the core team. I think there is a lot of support for a simplified UI (see Matt's post above). Just because there is a barrier before you get patches submitted doesn't make the core team unwilling. Each decision needs fleshing out before getting put into a new version of WP. If it wasn't that way, the project would be a (total) mess.

Its WordPress' support for older versions and depreciated plugins which is of the bigger issues.

Our commitment to backwards compatibility simply forces us to make smarter, more deliberate decisions.

Because we talk so much about our back compat efforts, it is certainly understandable that people might think that is where almost all of our development effort goes. But that isn't actually the case.

We heavily emphasize our philosophies because it makes adopting and updating WordPress easier, and we want users to know that. But in practice, the way we build software doesn't hamstring us. We've introduced new features and rewritten entire APIs without needlessly breaking plugins or sites. And we do sometimes drop stuff -- we are just careful about it. We do whatever is necessary to make WordPress evolve. In the end, we've simply become really good at following through.

Any thoughts on frameworks like roots which modify the normal core theme structure?

Stop calling it a fork—it needs a radically different core. So start over from the ground up! It needs to be a new project, not a fork.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact