C++20:Two complements reigns supreme

https://herbsutter.com/2018/11/13/trip-report-fall-iso-c-standards-meeting-san-diego/
C++20 and future C standards will stop supporting non 2-complement machines.
``Signed integers are two’s complement (JF Bastien) is the result of a courtroom drama in both WG21 (C++) and WG14 (C). After intense prosecutorial cross-examination, the witness finally admitted in both courts that, yes, all known modern computers are two’s complement machines, and, no, we don’t really care about using C++ (or C) on the ones that aren’t. The C standard is likely to adopt the same change.``

Also C++ is getting closer to D's CTFE with constexpr's expanding their role. Ranges and template-less constraints(dependent types require this) are also in standad.
``For the first time, besides the special case of generic lambdas, C++ will now let you write lots of generic functions without “template” or angle brackets, and that are concept-constrained and therefore much easier to use correctly than function templates have ever been before.``

Is this link from Hacker News? Go back there, please!

sepples committee keeps arguing about two's complement but still can't put good string handling utilities in stdlib. not to mention a non-atrocious syntax

>>2
All good links end up there, curb your autism.

I've never seen non two's complement machine and there is no reason to implement one. Same way, there is no reason to use non 16/32/64-bit architecture. Yes, some machines has registers with additional bits, but these are used mostly for typed pointers.

>>4
I don't see very many good links there

HackerNews is good if you like asutistic masturbation among fellow academic manchildren.

>>7
Wrong, hackernews is about hip starup founders

>>8
Startups === academia.

>>5

there is no reason to use non 16/32/64-bit architecture

There is no reason to use a 16/32/64-bit architecture either - unlike two's complement.

https://en.wikipedia.org/wiki/36-bit