tomato potato - if one company has a calculator app and someone makes a different one that is exactly the same.. it sucks, it is what is is. Look at all the 'to

tomato potato - if one company has a calculator app and someone makes a different one that is exactly the same.. it sucks, it is what is is. Look at all the 'todo list' apps on HN alone. regardless, they are making other ones (see gutenberg fields blocks) - but they HAD to re-make this exact one, because so many themes and plugins already use the exact code (2 million active install depend on it working) - - they also depend on it being secure, so more reason - but whatever. Anyone can rip off any gpl plugin in the repo at anytime, it's not outrageous. Automatt does not own all the directories in the world, come on. You can flourish with a 6 figure plugin or theme business and only be listed at themeforest or envato for starters. I'm not here to defend the whole kerfuckle - I think things should of gone slower from both sides, I find it reprehensible that all sides went to level 10 so quickly - but as more details come out, it appears this issues have been brewing much longer than we initially knew and got surprised by. It is not defending the indefensible - it makes sense, and its' not worse than what apple did to fortnite and so many others, its no different that what happened with wpmudev back in the day - so many others.. Truth is the owners of acf/engine were riding high making lots of money while using WP resources, they got asked to pony up some resources, they refused. They got blocked from the free resources they depended on (and so many of their subscribers depended on) The nice thing is WP and co have made a full copy of all the things available to them to host on their own servers and the GPL allows them to fork and make their wordpress sites pull from their own directory. Wpengine has taken a very adverserial stance that may save it some money this year, but may cost them more in the years to come. Wordpress has also suffered some reputational damage, but it's more of a wakeup call that you should not live by someone else's code or directory and these issues are possible. These sorts of things have happened many times in the past in smaller ways, like wordpress changing code that breaks premium themes like Salient - well we all spend resources to adapt or we don't spend resources and keep things using the old version of WP for example. Hey if it's your plugin I agree it sucks, but hey you made (they bought) a plugin that is GPL, sharecropping on someone else's code base and directory. Live and learn but don't suddenly say someone using GPL in various ways is indefensible - it's not like they pretended to give exclusive lifetime license to use this or that thing. and it was all free - sheesh.