391–400 of 457 posts
Earlier quoted context omitted.
PHP integrates with the server. It does not have the spawn a new process per request like CGI
I don't understand the distinction you're trying to make.
Earlier quoted context omitted.
What would replace it? PHP is unique in that it makes sharing a server trivial and low-resource compared to almost every other solution. A simple example might be that you can run 100s of PHP forums on a single machine low memory machine but if you want to use discourse (not written in PHP), it requires 10x 20x the resources for a single forum. This is true about almost every other solution AFAICT.
> [PHP] makes sharing a server trivial Is that still a thing? Why would an application on a server share anything other than the kernel?
Wordpress optimized hosts will have "servers" sharing the apache, the kernel, the php libs, even the DB instance. The effective burden of an additional host is tiny. Which is perfect for a local cafe's webpage which might be lucky to get a hit an hour.
Now how do you think you'll compete on price by using containers when your competitor can host a 100x the cafe web pages? The cafe owner does not care that they are sharing a php lib instance. They care that their 7 paragraphs appear when the page loads.
https://getpublii.com/ Yet, anyone?
Earlier quoted context omitted.
He's doing it in a way that feels suspiciously like a breakdown to me. The latest "we're restricting our contributions to 45 hours a week to match WPEngine" is the the reaction of a college student who is mad at their lab partner, not of an establish business that helped build the internet as we know it.
it's somewhat valid though, why continue providing free code for wp engine to resell when wp engine doesn't contribute to open source themselves? wp engine has also bought out multiple competing hosts, so they're a direct competitor with deep pockets
Earlier quoted context omitted.
No, pretty easy actually. You can sit and seek rent on something you built.
That's not what "rent seeking" means. Rent seeking is the term for manipulating institutions, customs or laws for the purpose of extracting money without creating anything.
Earlier quoted context omitted.
I don't think it's a mental breakdown, I think this is a (poorly executed) long pivot into Matt's companies having tighter control over the ecosystem and keeping more of the profits from hosting, plugin and theme sales. He's burning down "the community" on purpose. In a couple years, it'll be run more like Shopify, where the theme store and app store only list products that run their billing through Shopify and give…
One reason that Reddit's API changes killing the best clients was so poisonous is that the resulting non-exodus showed other companies that they can take user-hostile actions with impunity. A big enough mass of passive and undiscerning users will stay no matter what. Hence there being more freedom to take a strategy like this.
Earlier quoted context omitted.
>My personal take on this has to do entirely with how the decision to block WP Engine access to WordPress.org, unless they were willing to pay for it, was arrived at. Matt would be allowed to charge for access to Wordpress.org. It's his property. What you can't do is: make a service publicly available and then threaten a company that it needs exclusive terms In the lawsuit the judge asked Automattic to come up with a…
> In the lawsuit the judge asked Automattic to come up with a price for access to Wp.org and Matt did not provide an estimate. Automattic and Mullenweg argued that WP Engine should be required file a bond of $1.6 million to ensure that they are compensated for potential costs and damages if it’s later found that the preliminary injunction was granted without sufficient basis. https://www.searchenginejournal.com/judge…
>WPEngine’s arguments are persuasive. …the Court finds that any harm to Defendants resulting from the issuance of preliminary injunctive relief is unlikely, as it merely requires them to revert to business as usual as of September 20, 2024. Accordingly, the Court declines to require WPEngine to post a bond.”
Earlier quoted context omitted.
My personal take on this has to do entirely with how the decision to block WP Engine access to WordPress.org, unless they were willing to pay for it, was arrived at. And this is a critical detail that I'm fuzzy on. If anyone has context (even links with further info) I'd be very much appreciative. I have since read the WP Engine complaint. I understand what they are alleging. I'm just not 100% clear on the nitty and…
Well said. I think Matt Mullenweg has every right to take the action he's taking. It really seems like many companies are perfectly happy to exploit open source products. In this case, it seems like one company makes a lot of money using the Wordpress codebase and doesn't want to make equal contributions. Then they use the money they're making to turn around and sue Wordpress for standing up for themselves. If I were…
There's a right way and a wrong way to handle a conflict, and he's taken a direct route down the wrong way with his foot on the gas.
He would've been wise to read Sun Tzu, 48 laws, all those books on the basics of manoeuvring in a conflict, and found himself some wise and steady council to guide him through this effectively.
Instead he basically burst into a sustained petulant childish tantrum. He was doing things that basically any adult would know not to do.
He was in here, running his mouth in the comments section after legal proceedings had started. With everyone telling him to shut up. And instead he just kept going. And the comments literally then showed up in the legal proceedings against him, as everyone had warned.
Rights and obligations go hand in hand. Yes he had rights, and yes he could have exercised them to the benefit of the open source community (which was extremely important given WPs role in the internet - effectively carrying the beacon of the original internet vs its consumption by big companies).
But he also had obligations stemming from that. He should have played this diligently and carefully. But he didn't. And thus everyone expresses their disappointment in their own ways.
Earlier quoted context omitted.
>My personal take on this has to do entirely with how the decision to block WP Engine access to WordPress.org, unless they were willing to pay for it, was arrived at. Matt would be allowed to charge for access to Wordpress.org. It's his property. What you can't do is: make a service publicly available and then threaten a company that it needs exclusive terms In the lawsuit the judge asked Automattic to come up with a…
Isn't he within legal rights in fact to take away certain public services whenever he does want? Assuming that's the case (and that is an assumption), the fact that WPEngine went all in on a half billion dollar business model dependent on Matt is a big risk they took; I would think it would be absolutely top priority on their part to understand the nuts and bolts of the ecosystem they depend on.
The court filing is here if you'd like to have a look. Some california law around anticompetitive behaviour applies.
I thought of trying to summarize but don't wish to be inaccurate. Obviously this is under litigation so it remains to be seen which headings they win on if any.
But it definitely isn't as simple as being able to selectively withdraw a public service at any point for any reason. If it were the case would have been dismissed already.
https://wpengine.com/wp-content/uploads/2024/10/Complaint-WP...
I don't understand how (if?) WordPress has popularity among serious professionals. Extending it without plugins, many of which are paid, is a nightmare. Adding custom fields is laborious, configuring post type display modes is a slog as well. HN seems to grumble about Drupal but even if your only requirement is a PHP server with a MySQL database connect, Drupal (8+) is just as simple to set up as WordPress and infini…
The answers really are helpful and will tell folks a lot about the world. If you don't understand how WP and Drupal ended up where they did (and why Joomla, Cake, etc ad infi are no longer around), then I suggest that you try to answer the question your asking, or at least pay some attention to the answers you get.
WP had, for quiet a while, a much better and conceptually easier admin system. Even that system was clunky and hard to train non-tech folks to use. But it was better than Drupal and more interactive than Joomla.
You might not accept that answer, but that really was a lot of it in my experience.
I hate WP for a lot of reasons, but its not like the many "serious professionals" who have built software for it were doing so for unworkable reasons. I found it much of a pain the ass, but if you know what you're doing and develop the correct skill sets it is far from a nightmare.