687 karma · joined October 4, 2018
From the article: "it’s time for Matt to resign from either the WordPress Foundation or Automattic."
Can I gently suggest to you that posting under a throwaway leads you to post - and downvote - in a way you wouldn't normally, that is not helpful for the discussion?
WP Engine is truly upset with the money they were able to make from WP being in good shape for free the last 15 years? According to the maintainer it's hundreds of millions of dollars. Before Mullenweg complaining about their not chipping in, they seemed very happy to go on.
It's quite crazy to say if the last 15 years of work was not done by the paid devs and the maintainer, WP would be in a "better place". It just goes to show how partisan this topic is, trying to argue this seems rational to you at the moment.
If he just gave up in 2010 so there was no "conflict of interest" to satisfy this guy, who is actually better off?
It looked pretty nice, but it had some problems.
- The only actual 8K modes reported on the HDMI were some variant of YUV, it means you could not select what your OS considered an RGB mode
- Even using it at 4K, with the 55" TV a couple of feet from the back of the desk, my eyes could not keep all of it perfectly in focus.
- The power consumption was much higher than a typical ~30" monitor, and the amount of heat created was also significant. This became hard to deal with in summer.
Eventually I gave up on it and returned to a ~30" monitor.
The plugin you previously used was always completely dependent on the work of the core volunteers; you were always consuming their work and nothing changed about that. It just also already includes the optional plugin now.
Why would anyone end up in jail when everything is GPL2+?
It's also open to the plugin people to distribute the core themselves, but since they don't have a history of working on it, why would you imagine for core maintenance, you can trust a smaller private equity-funded group that historically leeches on the core project, more than the originating project for the core?
It seems the "perceptual framing" that is being engineered about this, that Automattic and its leader should be cancelled, is not about technical issues.
If for example, Automattic instead had said they will bundle the plugin functionality with the core, there are many historical cases of that, unpleasant as it is for the third party usually... results are identical, right?
It's more like mcdonalds replacing Coke with McCola with your mcdonalds meal - you were already trusting mcdonalds for the food. But even that is a stretch since both are GPL2 and there's no current sign the plugin Automattic provide differs from the WP Engine one.
GPL is on both sides, nothing stops WP Engine doing the same and providing their own flavour of core with their plugin, if that's what people want. Of course that costs more than private equity just using Automattic's core for free.
It's not like users aren't already updating to whatever Automattic want to give them, in the core, if that's the case? Automattic producing the same plugin and delivering it the same as the core doesn't sound like much of change, since users already trusted Automattic for the core either way...
lol
This goes quite far along the path, building all the build tools and toolchain to the same version before building the packages.
Isn't it just that your personal in-head GPT has been trained on C++ and wants to see it everywhere? It's not so easy to make very small embedded implementations and there's a reason after 25+ years C++ has not made inroads there.
If you're serious about your code, you will turn on -Werror -Wall -Wextra and anything else you don't like the look of, use static analysis and so on that makes this class of complaint moot.
Like myapi(uint8_t *dest, const uint8_t *src, size_t dest_len, size_t src_len), it's very clear what will be doing what with what.
You can cast const away and do something unexpected in there, but that's on you doing the Wrong Thing.