[RcouF1uZ4gsC]

Typically, you should not attempt multiple paradigm shifts simultaneously. In fact, I would argue, the more innovative your end user product is, the more boring your tech stack should be.

Facebook was PHP.

Google was C++.

Bitcoin was C++.

Netflix was Java.

Spend your innovation points on your product, not on programming language.

[vineyardmike]

Facebook was PHP (and then built its own). Google now has Golang (even if they probably still mostly use C++).

Most Telcos, what’s app used Erlang.

Apple used Objective C, and built its own language.

Microsoft used C++… and built a series of languages.

Most of the web programming was in flash… until suddenly JavaScript won out.

Except for Figma which uses WASM based stuff.

Spend innovation points on your product… but sometimes innovative products require innovative ways to built it.

[pjmlp]

Google is mostly Java and C++, Go has more use outside than on internal projects.

Nokia Networks customers were using a mix of C++ and Perl running on HP-UX back in 2004, and nowadays it is mostly C++ and Java running on Linux distributions. Not every telco is using Siemens Erlang based switches.

Apple created Clascal and Object Pascal, migrated to C++, got Objective C via NeXT acquisition, which previously licensed it from StepStone. They also created Mac Lisp, Hypercard, Dylan and Newtonscript.

Microsoft used BASIC for a looong time, dabbled with Pascal, had one of the best macro assemblers in the market, was the last MS-DOS vendor to actually add C++ support to their C compiler, focused on VB and C++ until .NET came to be.