Re:Secure Custom Fields by WordPress.org
by ankleturtle on Saturday October 12, 2024 @05:21PM
(#41822749)
You are abusing the community for your own gain. Stop!
[ Parent
| on HN ]
Re:Secure Custom Fields by WordPress.org
by geerlingguy on Saturday October 12, 2024 @05:40PM
(#41822912)
What is he gaining at this point?
Re:Secure Custom Fields by WordPress.org
by ankleturtle on Saturday October 12, 2024 @06:53PM
(#41823426)
Harm of WP Engine.
Re:Secure Custom Fields by WordPress.org
by acherion on Saturday October 12, 2024 @08:06PM
(#41823930)
At the cost of also harming WP. Well done Matt. clap clap (these are sarcastic claps)
Re:Secure Custom Fields by WordPress.org
by minimaxir on Saturday October 12, 2024 @08:52PM
(#41824201)
There's a reason mutually-assured destruction is abbreviated MAD.
Re:Secure Custom Fields by WordPress.org
by kuschku on Saturday October 12, 2024 @09:56PM
(#41824547)
Harming WPEngine is not even beneficial to Wordpress anymore.
With the level of revenge matt is applying you'd think WPEngine murdered his dog or something.
It just makes no sense.
Avoiding the embarrassment of backing down and admitting he is wrong.
Apparently that's worth burning down his life's work and legacy for.
Re:Secure Custom Fields by WordPress.org
by throw16180339 on Sunday October 13, 2024 @05:38PM
(#41831870)
It gives him an excuse to behave the way he's always wanted to.
So far as I can tell, when Matt talks about "the WordPress Community", he means:
- Matt
- the people who didn't quit Automattic last week
- _maybe_ the WP core developers who don't work at Automattic, so long as they keep their criticisms to themselves
And the community of people who _use_ WordPress to run their websites, and the people who help them to do that, and the 3rd party plugin and theme developers who make WP work for so many different kinds of websites - can all go and get fucked.