MySQL - Better performance and tune-ability. Higher connection limits/lower connection costs. Better multi-master and clustered replication story. 2+ decades in extremely high data and availability environments (telecom).
Postgres - Better SQL semantics.
Having supported both in 'bet the business' scenarios, I would choose MySQL hands down. Operating state of the art HA postgres clusters today feels like running MySQL clusters in 2005.
I find this piece to be guilty of conflating big business publisher profits with those of individual authors.
> Incidentally, there are 149 people in the Toronto Public Library system alone earning six-figure salaries. I’m pretty sure there aren’t that many earning that much in all of Canadian book publishing.
Why don't you just come out and admit that publishers are reaping massive profits that do not flow to individual authors. Pardon me while I don't shed a tear for these profiteers. You did a disservice by framing this on the backs of authors.
In September of last year, the frequency of goods selection for calculating CPI changed from every 2 years to every year. The change came into effect in January 2023.
I tend to agree - Amazon was king but now I can usually find cheaper products on Ebay and faster shipping to my locale than Amazon. Unless its an industrial lego piece coming from China - but then the price is insanely better.
I can't figure out what benefit Amazon brings these days... They seem like the most expensive option for anything not mainstream.
> This removes the need for the hardware to do reordering, and shoves the responsibility for finding parallelism onto the human or compiler, both of which can, presumably, take a more global view of the problem than a piece of silicon can.
I think this was proved wrong - the opposite is true; it is incredibly difficult for software to predict the internal state of a CPU at compile time. The silicon is truly the only thing with an accurate account of its internal state ( cache, register renaming, etc ).
Why would a child watch a gang bang? I worry about vile content targeted toward children. I worry about these things showing up on his youtube feed, not a porn website.
Because they accidentally ran across a link and clicked on it. YouTube comments are filled with links to porn / non age appropriate material for example.
>I worry about vile content targeted toward children.
As do I. But I don't think targeting is necessarily the issue here.
PornHub does target to children though. Their Instagram had a post about children watching porn for example.
>I worry about these things showing up on his youtube feed, not a porn website.
It isn't hard to mistype YouTube and since many pornsites have the word "tube" in them it wouldn't be hard to imagine they could get to a porn site.
I don't think you are following my points likely due to me not explaining it well.
Kids can easily access porn on accident. That is all my point is. We should make it easy to prevent kids from seeing it.
Pornhub was on Instagram and so kids could get to PornHub's page and view content directed to kids about porn. I think banning Pornhub from Instagram was the right choice and helps prevent putting adult related content on a kid's feed.
My point about tube being in other websites is when you google YouTube you may end up with a porn site if you have a typo. Kids, in an attempt to go to child friendly content on YouTube may end up on a porn site just by accident.
Postgres - Better SQL semantics.
Having supported both in 'bet the business' scenarios, I would choose MySQL hands down. Operating state of the art HA postgres clusters today feels like running MySQL clusters in 2005.