2020-03-31, 07:07 PM
Quote: If people can't even install a theme where the developer hasn't changed the compatibility yet
Maybe the core should also check for full compatibility and not wildcard compatibility too. Adding a warning could also suffice.
(2020-03-31, 05:33 PM)labrocca Wrote: [ -> ]I don't either. Just need a default responsive theme and 1.8x is ready to go. Plugins would just need to adjust for template changes. That's what I was hoping 1.9x would be but it's just another attempt to add features no one cares about such as Twig and a different mailer..
_You_ don’t care about these features, but I would say that is because you aren’t a theme designer. Of course a stock modern theme is essential, I’m not minimizing that fact, but updating the template system is important for getting third parties to keep contributing.
Contribution needs to be meaningful to get motivation going. You can’t expect developers not to implement or update for new technologies, talk has been done since years ago to apply these updates and even though it had failed or we have been slow to do it doesn’t means we should just drop these changes.
1.8 works pretty nice, yes, but it is outdated and needs replacing sooner than later.
I do agree the project needs better long time planning for specific features, as it is shocking how long it has taken to get a responsive theme, but we are too close to it in 1.9 that it would be frustrating to revert that work back. 1.8 needs to leave. We can’t just dispose of 1.9 as that would remove meaning, thus motivation, off the project.