3 ms·
None of which has anything to do with having a double standard. If you ran your project with backwards compatibility as a core value and promise to your users t
by zaphar 8y ago
None of which has anything to do with having a double standard. If you ran your project with backwards compatibility as a core value and promise to your users then don't be surprised if they get upset when you break that promise.
It can be good to recognize that back-compat has become detrimental. When that happens, you need to communicate the reasons why you have decided to break it and communicate that the projects values have changed going forward. It doesn't sound like either of those things have happened here.
- photomatt 8y agoPlease check out my "State of the Word" presentation from 2016 and 2017, I tried to make the best case I could for why, perhaps once a decade, it is worthwhile to trade backwards compatibility for future relevancy. The reason I have personally not advocated for that trade-off before was that the reward on the other side was not worth it, but with Gutenberg we have a huge opportunity, and incredible user demand demonstrated by the adoption of the beta plugin, that I think makes it #worthit.