>* is memory consumption...* ??? You're recommending a slower language, that uses more watts, on a presumably 24/7 backend... to save a few bucks on memory?

>* is memory consumption...* ??? You're recommending a slower language, that uses more watts, on a presumably 24/7 backend... to save a few bucks on memory? As I said, if you want a company to switch to c++ or rust because you want to save money on memory IN ADDITION to all the money you're saving on watts, while getting the same or better performance? That might make some sense. Switching to go makes, No, sense. You end up paying more money per user session to do the equivalent work. (Even worse, each user waits longer because the work is done slower.) And then, like typical engineers, we'd proceed to explain to our bosses that all of this is actually better... because our new program uses less memory.