"Unexpectedly" in this context might be referring to the actual event in which they traveled from their home to their cell, in which case the unexpected nature could easily prevent them from securing the Google account.
I hardly think it matters anyway. Take out "unexpectedly" and their complaint is exactly the same. Suggesting that someone who went to jail shoulda/coulda/woulda taken steps to avoid being locked out of their Google account is not practically different from victim-blaming.
That’s horrific, and the actual sentence was 6 months+ time served or you ended up winning at trial? Is it bec only US citizens are protected by the constitution’s promise of a speedy trial?
This is very common in the US justice system. There's a general institutional apathy or sometimes even vindictiveness that causes random delays to get to trial. If you don't have the money for bond, don't have someone to pay, or a bondsman wont cover you, you just stay in jail.
Every year multiple people die in prison from preventable causes without ever being sentenced.
This is why bail reform is important. A well-off person can pay-away the bond and prepare to defend themselves. A poor person will be stuck, lose their job, home, important documents, pets, etc all before being found guilty. If they're found not-guilty, its simply their fault for being poor or being in the wrong place at the wrong time and there's zero recourse for these people having their life basically lit ablaze. Please don't take the anti-bail reform propaganda at face value, for every terrible outlier case, there are hundreds of people who don't have their life grenaded over a small charge.
Making people desperate is an easy way to increase crime.
These days, most smaller users go with a managed DBaaS such as AWS RDS, and on RDS MySQL gets massively more usage than MariaDB.
I build schema management software for MySQL and MariaDB, https://www.skeema.io, used by several hundred companies. Among my userbase, MariaDB is a tiny minority, to such an extent that I wonder if it's worthwhile to continue keeping up with their new quarterly release schedule.
WordPress is very widely used, but it is not "60% of the internet" (or even 60% of the web) based on any statistics I see anywhere. Some sites say it's 60% of all CMS's; perhaps you may be transposing these stats?
Anyway, among WP usage, I would confidently wager that the percentage running in "cheap VPS" setups is declining fast each year. Many different reasons for this. The heyday of smalltime independent bloggers (on WP or otherwise) was a decade ago. Large SaaS hosts (including the official wordpress.com) make up a big chunk of WP hosting. Security is a huge issue with self-hosted WP. Companies using WP as a CMS aren't going to use a tiny VPS.
There are still a lot of WordPress instances on cheap VPS setups, don't get me wrong. I just don't believe it's still such a major force where it would make up a majority of new mysql/mariadb installations anymore.
To clarify, my comment was based on anecdotal discussions and interactions with users, issue reports, feature requests, user enthusiasm for new MySQL support/functionality vs relative lack of enthusiasm for new MariaDB support/functionality, etc.
The Skeema CLI is able to accurately identify your database version and flavor (which is necessary for its functionality), there is no notion of MariaDB registering itself as MySQL. But the CLI does not contain telemetry, so I don't have hard stats on MySQL vs MariaDB usage.
> These days, most smaller users go with a managed DBaaS such as AWS RDS
I think there's likely a long tail of small (non-tech) businesses that run WordPress (or Drupal/Joomla) on a traditional shared web host (the kind that only offers PHP and MySQL/MariaDB).
> Simply track your desired schema state in a repo of CREATE statements, and the tool figures out how to apply any changes to your tables and routines.
Wow, this sounds extremely useful, great job! Does anyone know anything like this for Postgres?
Thanks! I know of a couple Postgres tools that work in a declarative fashion: migra [1] and sqldef [2].
Migra is Postgres-specific. Its model is similar to Skeema's, in that the desired-state CREATEs are run in a temporary location and then introspected, to build an in-memory understanding of the desired state which can be diff'ed against the current actual state. (This approach has also been borrowed by other recent tools, including Prisma Migrate [3]). In this manner, the tool doesn't need a SQL parser, instead relying on the real DBMS to guarantee the CREATE is interpreted correctly with your exact DBMS version/flavor/settings.
In contrast, sqldef supports multiple databases, including Postgres and MySQL (among others). Unlike other tools, it uses a SQL parser-based approach to build its in-memory understanding of the desired state. As a DB professional, personally this approach scares me a bit, given the amount of nonstandard stuff in each DBMS's SQL dialect. But I'm inherently biased on this topic. And I will note sqldef's author is a core Ruby committer and JIT author, and is extremely skilled at parsers.
MariaDB is more closely aligned with Wordpress and PHP in terms of licensing. I sort of assumed that most users of (FL)OSS who had previously used MySQL would be using MariaDB by now, but based on comments in this topic I must be wrong.
Thanks, I gave those another try. They links didn't look inviting, expected just more of the same (text + images). But's actually an interactive demo from end-user perspective. that was easy to get: https://grid.is/@grid_templates/template-interactive-user-fu...
