4 ms·
This blog is so disingenuous. > I feel for impacted end users. But that they were impacted at all is WP Engine’s fault and responsibility to fix. Users are im
by InsomniacL 2y ago
This blog is so disingenuous.
> I feel for impacted end users. But that they were impacted at all is WP Engine’s fault and responsibility to fix.
Users are impacted because the update mechanism was pulled out from under them with no advanced warning, that's not WP Engine's fault.
- Aurornis 2y agoI’m amazed by how many people are defaulting to Mullenweg’s side in this spat. I think a lot of people are giving Wordpress.com (the hosting business) the credibility and respect that they normally give to open source projects, but that credibility should be going to Wordpress.org. The way Mullenweg is trying to blur the lines between .org and .com as convenient for his business purposes is the most confusing thing about this argument.
- LegionMammal978 2y agoEven attributing the credit to WordPress.org seems hairy. On another thread, someone (claiming to be an Automattic employee) said that the WordPress.org website is personally owned and operated by Mullenweg, and that it has no formal affiliation with the WordPress Foundation [0]. (Even though DNS records place its IP address with the Foundation.) So really, I think the blurring here might run even deeper than it may appear at first. [0] https://news.ycombinator.com/item?id=41656670 https://news.ycombinator.com/item?id=41656670
- tpmoney 2y agoIf I sign a contract with you for 10,000 barrels of apples, and the next day your sole apple vendor decides they don't like you anymore and cut you off, that's not my problem. I might be sympathetic to you, but I didn't sign a contract with your vendor, I signed it with you. You owe me the barrels and not needing to worry about the details of how you fulfill that contract is one of the things that makes contracting stuff out useful.