Re: maybe it's time to re-consider server-side inefficiency
"I write C++ REST services. Not for any performance reason but because I've never got on with all the Node/Java web development frameworks"
and that's the kind of thing I'm talking about.
as an extra added bonus, I did some work for a company with a poorly designed back-end, by adding C utilities that are called from the DJango framework. Upload processes that WERE taking more than a minute (due to cpu-intensive activity) were shaved down to a few seconds.
But I didn't re-do all of the DJango stuff. That wouldn't have bought much of a performance change. What I _did_ do made a HUGE difference, mostly because I saw a lot of "the Python way" coded into the back-end. It implied, to me, that "the established way of doing things" is simply GROSSLY inefficient, and re-coding that stuff in something that _is_ efficient (CGI via C programs, or even Perl if it's simple enough) would buy you a HUGE performance boost (in many cases where CPU intensive operations were slowed down by anti-Meltdown patches).
If it's not CPU intensive, you probably wouldn't see a change (yeah). So for THAT, who cares.
also I've written simple web servers in C a few times. One fo them was an attempt to "genericize" something to fit on an Arduino - yes, a somewhat generic web server in under 30k of NVRAM, intended to let you configure an IoT device with a web page. down side, you can't really do anything with the Arduino because the web server code is still a bit too piggy, so I shelved it... [had to try it anyway in case it worked]. but I was able to change device parameters and store them in EEPROM (things like the IP address, fixed or dynamic) so there ya go.
THAT being said, to *ME*, 'C' coding is probably faster (in a significant number of cases) than doing a bunch of stuff with BLOATWARE, with 3rd party library hell, just to fit it all into "their way of doing things".
And it's that "3rd party library hell bloatware" that's slowing down the back ends WAY too much already, I bet.
(and with dis-respect to the 'random caps resolution' comment from earlier: BITE ME)