I think you Ryzen CPU is being throttled. It is not able to sustain it's burst speed. You should keep an eye on CPU temp and clock.

My benchmarks on hardware that have less single thread power than yours:

Intel(R) Xeon(R) Gold 6240R CPU @ 2.40GHz - Linux - Java 8

0 - Passes: 3200, count: 78498, Valid: true 1 - Passes: 3197, count: 78498, Valid: true 2 - Passes: 3200, count: 78498, Valid: true 3 - Passes: 3202, count: 78498, Valid: true 4 - Passes: 3207, count: 78498, Valid: true 5 - Passes: 3207, count: 78498, Valid: true 6 - Passes: 3202, count: 78498, Valid: true 7 - Passes: 3205, count: 78498, Valid: true 8 - Passes: 3209, count: 78498, Valid: true 9 - Passes: 3178, count: 78498, Valid: true

Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz - Linux - Java 18

0 - Passes: 3445, count: 78498, Valid: true 1 - Passes: 3443, count: 78498, Valid: true 2 - Passes: 3408, count: 78498, Valid: true 3 - Passes: 3449, count: 78498, Valid: true 4 - Passes: 3439, count: 78498, Valid: true 5 - Passes: 3442, count: 78498, Valid: true 6 - Passes: 3450, count: 78498, Valid: true 7 - Passes: 3445, count: 78498, Valid: true 8 - Passes: 3438, count: 78498, Valid: true 9 - Passes: 3447, count: 78498, Valid: true

Things got cheaper because they are being made where wages are cheaper. At the end of the day, everything that is a expense to me is a source of income to somebody else. Only robots don't get paid.

Is it impossible to believe that someone harvesting corn with a combine would be able to sell it for cheaper than if they had harvested it by hand?

> Only robots don't get paid.

Their owners do, though. (And their makers.)

Software is hard, but unlike many other professions, you can do useful work at almost any level of the learning curve. Even for those of us with many years of experience, there's always something new. You can use an argument within these lines. Remember them it's a journey. One can start with bare resources. It's not capital intensive and there's no need to put themselves in debt.

And there's still people who don't believe in 10x programmers...

Tom Lane is the best example of a 10x programmer that I have met. Really humble and nice too when you meet him in real life.

That's assuming that these people only contribute to PostgreSQL. I'm betting most of the folks listed here make major contributions on other projects or at work.

Your comment feels like a bit of unfair judgement, particularly since a lot of those you are implying that are 'only 1x programmers' are effectively donating their time.

I think you almost got the answer to your own question. For me, quality software is made by very small teams of very competent people improving the software for a long time. We don't know much about the vast amount of closed software, but, for opensource, the state-of-the-art follow these rules.

Injection means you can modify an existing query. The example are not SQL injections, they are full queries.

HTTP is not just for the web. In fact, the vast majority of HTTP trafic doesn't involve the browser at all.

The examples are realistic and useful. E.g., Clickhouse uses POST methods for queries, and a ridiculous `&readonly=2` parameter to differentiate modifying queries from readonly SELECT queries.

This is only a proposal for a new HTTP verb. How you use it (and how you interpret is) is completely up to you.

I don't see any sql injection in samples

PHP's null coalescing operator:

firstWorking() ?? getItFromTheCache() ?? getItFromTheDataBase() ?? getItFromAnExternalApi() ?? computeItTheSlowWay() ?? defaultValue;

Perl OR short-circuit:

firstWorking() or getItFromTheCache() or getItFromTheDataBase() or getItFromAnExternalApi() or computeItTheSlowWay() or defaultValue;

If self moderation is not working, plain old avoidance/abstinence is the way to go.

I am not capable of moderate game playing, so I have no games installed on any device of mine.

I follow the same testing philosophy. No mocking, except for external dependencies (mainly 3rd party APIs). No cleanups, except for problematic cases. RDBMS cleanups, when needed, are done by enclosing tests with transactions and explicit rollbacks.

Power law and asymmetries