The argument wasn't for shortening it, but for distributing it through the year. I have never in my adult life taken 10 consecutive weeks off, and 5 two-week breaks would still be very generous.
> This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
Warranty disclaimers may (or may not, depending on the law of the effected jurisdiction) limit liability for claims on an implied warranty theory, but they certainly don't apply to tortious interference or unfair competition claims.
I’m not saying the claims here are valid, but the warranty disclaimers don't seem at all relevant to the bases of liability asserted.
I haven’t bothered to look at the actual filing, but none of the causes of action mentioned in the article were about warranty, merchantability, or fitness for purpose.
yeah, this part is where I am confused - the dispute itself is about bad business to business behavior, but the class status of this lawsuit drills down to harm caused to end users. I'm trying to figure out what expectations end users are entitled to since it's obviously not the case that WP users can hold Automattic directly liable when they are hacked.
I _think_ the argument is that WPE gave them the (at the time reasonable) expectation that risk mitigation was handled by them, and Automattic made that expectation impossible to meet retroactively hence tortious interference, but is there language that passes the liability up the chain from the end users? To me it seems like WPE has a case but the end users as a class might face headwinds.
And for everybody angrily downvoting me I agree with you that Matt is an asshole but that doesn't mean I don't want to understand the nuance of a class claim in a case like this.
IANAL. The chain of argument is roughly: WP was transferred to WPorg -> WPorg promised open access to WP ecosystem (including plugins) -> Matt/Automattic retained effective control over WPorg -> Matt/Automattic abused their control over WPorg to sabotage WPE's ability to provide contractual services -> WPE's customers suffered.
EDIT: I think the part causing most confusion is relying on customer's expectation that they are NOT using WPE's product, but rather using WP plus WPE's services. I.e. If X contractor installs a thing to your house/car/whatever and then manufacturer of that thing then uses it to sabotage your business, you get a claim against manufacturer, not you against contractor.
This is not about any warranties at all. The warranty and liability disclaimer applies strictly to those parts and is used to establish
This suit is about unfair business practices: tort and ratchet. The suit raises a claim that Matt publicly boasted of harming WPE through his actions, which should establish intent. The core claim is that Matt/Automattic/WPF acting as a unit intentionally abused their collective power and relationship with WPE to cause harm on WPE and their customers, demanded payment to stop causing harm and on top of that attempted to pull said customers away to their for-profit alternatives.
Before you go and claim "but there are no warranties and SLAs on plugin repository", a supporting claim in the suit is that WPF plugin repository is hard-coded into WP software, therefore part of the overall service (volunteer effort maintaining the WP package) and selectively targeting users of WPF repository constitutes unfair business practice.
A distant analogy could be a tourist spot scam where nefarious party sees a family, offers their child a candy and then harasses parents to pay up. Or similarly with flowers for couples.
I’m not a lawyer, but why would they remove uses of WordPress from their website right before suing Automattic if their position is that they weren’t violating the trademark?
There are some things I host this way as well. On the other hand, I find that having autoscaling and automated deploys makes a big difference in speed I can iterate on some side projects.
Are there any good vertical autoscalers out there?
If we simply scaled the machine bigger and bigger (and then smaller) as needed, we'd avoid all the complexities of horizontal auto scaling. The limits of vertical scaling would be rather huge these days.
The simple edit/deploy loop of the blog post would remain 100% usable.
The bonus is that it'd work nicely with using sqlite as a datastore as well.
