None of which have much to do with how the hardware handles requests.
Am an EE with a background in applied physics and well aware we could jam a kernel in the BIOS/UEFI storage and generate the runtime state around it at boot from a prompt cause I am working on just that
Which is exactly where we are headed with Jev/decision models; they can generate new config to min/maxing per process resource use; look into bpf and sched_ext and meditate on their application. It should eventually jump out at you
We have known in the abstract how to handle computing efficiently on our machines since we started building transistor based machines
It doesn't require handing a bunch of meat suits verbose languages/bloated state machines to manually tweak the parameters of and make mess of electrical state management
Writing code is not high tech. It's 1970s and 1980s tech. As this forum should be well aware tech evolves with the times.
The coder bros refusal to move on is them clinging to a sunk cost fallacy; but they already put time and $$ into their education in ugly languages and DSLs that merely initialize values in memory and ask the hardware to run it within some spacetime constraints
The syntactic gibberish is just a barnacle of a bygone era
Social web addicted Millennials need to grow up and move on