Writers/editors really, really like Wordpress for some reason, which is like 40% of the Internet, add to that all the other Php stuff. At $DAY_JOB we have a Wordpress instance behind our VPN and use the json API to send the articles to a front-end server written in something else. Forces us to duplicate some of the front-end plugin code (and we try to not use many) but we get peace of mind in exchange.
Hey, that's me! Unfortunately that's only reasonably complete through mid-February of 2025; i had some health issues and was never able to catch back up.
" WordPress powers about 41% of the internet. It took Matt Mullenweg twenty years to build that. It took him about ninety days in 2024 to lose the trust of the community he built it with — the agencies, plugin developers, hosts, and translators who bet their businesses on the update button still working next Friday. This is the full timeline: how a blog fork in 2003 became a movement, how Automattic became a company, how WP Engine became the target, and how one keynote at WordCamp US turned into cease and desists, lawsuits, forked plugins, mass resignations, and a preliminary injunction "
The community was already starting to turn on Matt well before 2024. He's appointed himself release manager for every version of WP since 5.0 in 2018, which is how Gutenberg managed to land in core in such a half-baked state.
I already knew Matt was throwing a tantrum and refusing to address conflicts of interest. However WP Engine also do not come out of it looking good. Nor do a lot of people in the WP community. Matt is a problem, but it does not look like he is the only problem.
The Wordpress community got so big, that inevitably it attracted leeches. Unfortunately, Matt chose to address a home-infestation problem with a firethrower.
Current ooxml/odt formats use a zip file with xml files inside (plus other files like images). I'd guess one way would be to store the xml itself as a blob and another to use a json field, which Sqlite stores in a more efficient format called jsonb: https://sqlite.org/json1.html#jsonb
The people making the video are already making the information public, you are just making it more convenient. This strikes me as similar to downloading public court documents from a government site to make them available outside of their for-profit service.
When was this? I've only seen this "anti-rust" vibe in the past few weeks, guess triggered by the Bun rewrite. Zig people usually will tell you to use the right tool for the job over shilling the language or that you don't need to use it yet (if you want a stable language/documentation) the language will be there if you want to check it in a few years.
The language itself will probably stabilize in maybe 3 years. The last things they'll do is work on the std lib, documentation, spec. That will take time but the language will be ready before then.
reply