Let’s look back a few years…
Assembly code without much optimisation…
MSBASIC was fine on 8-bitters, running at 4MHz or less - through the late 70s and 80s for many of us, until CBASIC and PASCAL rolled along, and we could do 80% more with 20% extra coding effort, then Java and some others stumbled into the shot.
Easy to write, but inefficient.
C already had an audience, then C++, and C# arrived.
They all matured, and diverged as ‘web applications’, and ‘the cloud’ started to show up.
(Client-Server anyone)
HTML and then Python arrived to make GUIs and single-user applications a bit easier to write, but luckily, computers had increased their hardware performance by more than 100x - sadly the code ran at effectively the same speed, you could write code that appeared the same speed to the single user, but occupied 80% of the system resources to do it!
Luckily disk and I/O evolved in parallel, along with coprocessors - to pick up the data flow bottlenecks
About now, we should consider that here we are in 2021, with 8-bit 16MHz embedded processors that are quite capable of keeping up with 3GHz, 64-bit processors on simple control projects. Other hardware in the mid point can do the same, better.
Sure there are other benefits, but when they’re programmed with Oranges to Oranges, it becomes abundantly clear why ‘system’ programmers use the ‘harder’ languages than the easy to teach ‘application’ tools.