I'm sure they're using a strict subset of C++ but it is still complex. I wonder if they'll move to Rust some day.

Most of the standard is taken by the description of the standard library ; the language specs ends at page 457 in C++20 (last draft). How long would be your language spec if every single function's documentation was part of it ?

To give a reference with other languages:

- This is a bit less than C# (whose standard language spec ends at page 462 in ECMA-364 2nd ed.).

- The python spec for 3.9.9 is 151 pages. Okay, but let's compare equivalent things in the C++ spec and Python spec: awaiting a coroutine.

* In Python (the whole "await" spec):

    Suspend the execution of coroutine on an awaitable object. Can only be used inside a coroutine function.

      await_expr ::= "await" primary 

    New in version 3.5.

* In C++ (5% of the "co_await" spec):

    The co_await expression is used to suspend evaluation of a coroutine (9.5.4) while awaiting completion of the computation represented by the operand expression.

      await-expression :
          co_await cast-expression

But, for C++ this is only the first sentence (which is not written in an abbreviated style but as a proper sentence). Then a whole page explains the semantics in detail, and gives a complete example of how to use it. The python spec is just insufficient in comparison.

You turn it on and it scales right up. Right up to space.

Would have been so more funny if you wrote "cloud scale".

It's interesting how much contempt people have around here for one of the most successful open source oriented companies in recent memory.

Most of the bad things about MongoDB are actually bad things about the NoSQL fad, and that fad was huge around here a few years ago.

That's the frontend. It's fed data by the main computer, but if it crashes nothing else is affected.