> We may never see a 4.0 because of the scar tissue, but the language continues to evolve.
They should do the opposite really. If it hurts, do it more often and get better at it. A perfect time would be when Python gets some nice JIT performance improvements which everyone will probably like.
I notice KDE's resource utilization more or less constantly. With KDE's bling turned all the way down, Kwin constantly uses 5-10% CPU when I am literally doing nothing (with my hands off the mouse/keyboard). This causes my laptop fans to noticeably spin up and makes them a lot more prone to spinning up more forcefully while doing a small task. With XFCE, my fan never audibly spins up unless I'm actively doing something. Even if I just do something small/quick, my fans don't spin up most of the time.
> NOAA was forcasting record flooding days before the storm.
The NWS forecast record flooding about 36 hours (!) before the storm hit. They only issued a flood watch shortly before everything became unpassable. Perhaps it was unavoidable, but the NWS has some serious explaining to do.
So many of communities in NC are completely cut off without food, water, power, and until a day or two ago cell service. The level of "disaster recovery" is shameful to nonexistent in so many places. I invite you to watch the video from this news report.
> But then: if they've been on notice for many months about Mullenweg being > upset about their use of the trademarks and lack of participation in the community (confirmed on camera, unless he forged emails), it feels to me like WPE --- a company with an 8-9 figure run rate --- should have been in a position to know what was coming with WordPress.org and how to mitigate that.
Matt's company owns and uses wordpress.com, so Matt's sudden concern about WP Engine using Wordpress' trademark does not seem very believable (or at the least massively hypocritical). The trademark issue just seems like a handy weapon to get what he wants. However, there are no good guys in this feud as you said -- only mud.
Again you're claiming it was "sudden", but it does not appear to have been sudden.
Meanwhile: nobody seems to deny that WPE could simply use WordPress's OSS software assets to stand up their own services, including Mullenweg. But that's all open source gets you. It doesn't entitle you to trademarks or online services!
> Again you're claiming it was "sudden", but it does not appear to have been sudden.
It was definitely sudden, just last week the term "WP" was explicitly allowed in Wordpress' Trademark Policy. This issue isn't really trademarks, it is just a club.
"The abbreviation “WP” is not covered by the WordPress trademarks and you are free to use it in any way you see fit."
> But that's all open source gets you. It doesn't entitle you to trademarks
Unless you're Mullenweg, who has abused the Wordpress trademark for years via wordpress.com. I greatly respect his years of work and dedication. However, the ends do not justify the means.
No, he hasn't. Automattic's contributions back to the WordPress foundation dwarf those of WPE's. He gave a whole interview spelling out what other companies do to get access to commercial use of those trademarks. He wasn't even demanding parity with Automattic.
I'd like to point out that the WordPress Foundation is merely the entity that owns the trademark, then gave ("for good and valuable consideration" [1]) an exclusive, perpetual, and irrevocable licence for commercial use of it to Automattic.
The WordPress project is not the foundation. The WordPress dot org website isn't under the foundation either (it's owned and run by Matt [2]), and should be considered separate from the project.
I think most contributors outside Automattic want to contribute to the project and its surrounding community, not WordPress dot org.
FYI, Python is named after Monty Python , who got into all kinds of trouble making fun of and saying things that upset basically everyone (religion to LGBT), which is ironic considering the circumstances.
I think the "hosted flavors of SQLite" would be doing the type of trick Litestream does: streaming the WAL to other copies of the database. The copy you interact with is still local.
They should do the opposite really. If it hurts, do it more often and get better at it. A perfect time would be when Python gets some nice JIT performance improvements which everyone will probably like.