Live data from Hacker News

WordPress.org's latest move involves taking control of a WP Engine plugin

theverge.com

191–200 of 222 posts

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#191

Earlier quoted context omitted.

In 2024, wtf. How can anyone especially on software with this kind of reach still do such absolute amateur things?

> want free software to run website > want free plugins to add functionality to site > absolutely will not hire developers or pay for software or plugins > how dare the free plugin for my free software not be coded to the highest standards

That code is identical to the commercial version ACF Pro which currently costs $49/yr for a single website.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#192

Honestly I don't get the backlash Mullenweg is getting - a corp is trying to freeload on OSS community, GPL let's them have the code - but I'm all in favor of kicking then off of everything else.

Because I disagree with this definition of freeloading. They've offer a free, open source, very popular plugin for Wordpress, according to the Wordpress.org's plugin page, with 2+ million installs. Wordpress forking and taking over the plugin seems like they've accepted the code/contribution.

Not contributing back to the project you're basing your business (eg. the smallest example being infrastructure they are cut off from).

Honestly zero sympathy for WP engine, and I don't really see a better way to force them to pay.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#193
post #79
post #75

Earlier quoted context omitted.

If the bank starts fiddling with the numbers in your account: "I'm not being attacked, it's their database"

> bank starts fiddling with the numbers in your account If a bank messes with your money, you ask for your money when that happens. Not defame the bank based that they updated their database, business as usual, but you liked the old one. how exactly did they mess with your stuff? where's the attack you're speaking about? where's physical harm?

The database says you have zero money, in fact you are not even a customer and never were, good day sir.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#194
post #68

Earlier quoted context omitted.

WPE contributes to WordPress; Matt is just full of shit on this. It's an excuse, not a reason.

What does WPE contribute? I ask from a place of curiosity. Code, money?

They have an equivalent of 1-2 full time people working on it, they sponsor the WordPress conference, and they make a couple really important plugins almost everyone uses

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#195
post #79

Earlier quoted context omitted.

> bank starts fiddling with the numbers in your account If a bank messes with your money, you ask for your money when that happens. Not defame the bank based that they updated their database, business as usual, but you liked the old one. how exactly did they mess with your stuff? where's the attack you're speaking about? where's physical harm?

The database says you have zero money, in fact you are not even a customer and never were, good day sir.

The paid version of AFC is not affected, so I'm not sure what are you talking about?

What money? who did you pay? for what?

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#196
post #140

Earlier quoted context omitted.

I wouldn't even really call it that. I only think Wordpress is easier if one of two things is true: 1. You are actually building a dynamic site; eg WooCommerce is much easier than building your own storefront. 2. Your users refuse to use Markdown, and are paying you enough to double the overhead and put it all on you. It gives me a good chuckle when I see posts on here like "We use Wordpress and then scrape the stati…

In my experience, Markdown isn't the barrier. It's the: - Plugin ecosystem. Marketing people want to use specific plugins for SEO, automatic internal linking, etc. Those plugin only work with wordpress. - Marketing people want to deploy to production. They hate waiting for dev to do anything (which brings us back to the importance of the plugin ecosystem, to add functionality without developers). - It's a familiar sy…

Not really. Weird syntax is intimidating, GitHub for CMS is intimidating, people want nice goowies.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#197

Earlier quoted context omitted.

> want free software to run website > want free plugins to add functionality to site > absolutely will not hire developers or pay for software or plugins > how dare the free plugin for my free software not be coded to the highest standards

That code is identical to the commercial version ACF Pro which currently costs $49/yr for a single website.

[dead]

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#198
post #140

Earlier quoted context omitted.

In my experience, Markdown isn't the barrier. It's the: - Plugin ecosystem. Marketing people want to use specific plugins for SEO, automatic internal linking, etc. Those plugin only work with wordpress. - Marketing people want to deploy to production. They hate waiting for dev to do anything (which brings us back to the importance of the plugin ecosystem, to add functionality without developers). - It's a familiar sy…

Not really. Weird syntax is intimidating, GitHub for CMS is intimidating, people want nice goowies.

Asking your dev team to prioritize deploying updates to your markdown site is also intimidating. In most companies, everyone outside of engineering has a view of engineering that “Developers hate to be interrupted and need everything scheduled in a sprint 2 weeks in advance” - when marketing teams decide between Wordpress and a markdown system managed by the dev team, the choice is obvious (avoid anything that requires dev getting involved)

Easy GUI for writing and publishing to production, with no-code installable plugins that extend functionality, is exactly what Wordpress offers that markdown does not.

Webflow has a very similar value prop.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#199
post #173
post #97

Earlier quoted context omitted.

Yep. And they’ve gone 0-to-100 within days. I think he has a fair point - I’d be totally comfortable with a standing expectation in a community like Wordpress for companies to pay their way (or be looked down on & excluded from taking part in community events). But the expectations have to be a fair & transparent, and ideally communicated from the start, so people and companies can make informed choices about how the…

> ideally communicated from the start if only a minority could grow big and sufficiently high revenue generating to be capable of paying anything, then having this concept of "paying back" from the start would've been a chilling effect on the adoption in the first place. wordpress ecosystem is big, but it is the network effect, rather than the software itself. This network effect require lots of individual participan…

> If it was known at the start, that if you grew to a certain size, you'd have to start paying a royalty of some sort (which is the "community expectation of pay or contribution"), then you may not even start using the software in the first place - or at least, consider alternatives.

Maybe! But you could say the same thing about every paid service. “Oh, if Netflix charges customers money every month they won’t grow as fast and might never be financially profitable!”. The answer isn’t to remain free forever. It’s to accept the trade off.

And it’s gotta line up with the license too. I’d be happy if the policy was “look, if you’re doing >1M monthly revenue, we expect your company to fund some people full time to work on opensource contributions. (With some specified minimum revenue / developer ratio). After all, your business depends on this free software but software isn’t free to make. If you don’t want to do that, that’s fine - but you’re getting rich off our voluntary labor without giving back in turn. It’s an opensource licence. You’re legally welcome to do that. But know that so long as you do that you aren’t welcome at conferences or community events or spaces since you’ve opted yourself our community of contributors.

Re: WordPress.org's latest move involves taking control of a WP Engine plugin

#200

Honestly I don't get the backlash Mullenweg is getting - a corp is trying to freeload on OSS community, GPL let's them have the code - but I'm all in favor of kicking then off of everything else.

Are you honestly saying that when Matt just stole an OSS project's users? ACF is OSS. If that's not freeloading I don't know what is.
Post reply on HN