You got the year wrong with that '0' prefix. The decade you're referring to is the 11990s.
https://longnow.org/ideas/long-now-years-five-digit-dates-an...
Good luck getting people to agree on anything.
So this is now the year 2,002,023 FE (Fire Era).
As an example, as late as '99, my first large web application was C++, and that was not an unusual choice at the time.
Most of the stuff I have exposed to the Internet written in C or C++, has done so by using a safer managed language and only accessing the native code via libraries.
Naturally there is the issue of on which language those runtimes were written on, but even so, the trusted computing base is much smaller than having the application fully written in C++, with possible C idioms while parsing data coming out of the network.
c++ projects today are very different from c++ projects in the 01990s when basically all 'serious' software was either c++ or c
a lot of c++ projects in the 01990s were what we think of now as java projects or c# projects (or django projects): line-of-business systems full of boilerplate and shitty architecture, not streamlined mega-optimized aaa game engines or web browsers
c++ projects today are the niche that was left over, which is, yeah, basically the cases where you can't afford gc
— ⁂ —
the appeal of wirth languages is that you get 90% of the value of a monstrosity like pl/i or c++ for about 5% of the complexity
language complexity hurts you three times: when you are learning the language, when you are choosing a compiler, and when you are debugging your code
so actually sometimes you get 200% of the value of a monstrosity like pl/i or c++
hopefully at some point someone will develop a wirthified version of rust, but i don't think wirth will do it this time