Well sure immaturity exists in every axis. I've seen "performance zealots" seriously suggesting moving a perfectly functional internal flask based API into some

Well sure immaturity exists in every axis. I've seen "performance zealots" seriously suggesting moving a perfectly functional internal flask based API into some obnoxious, bloated Java Spring something or other to squeeze performance out of it. The thing served approximately 1 (internal) user at a time at a rate of less than 1 request per minute on average and was a read-only API. Flask was just fine for the purpose. I've also been guilty of this in my younger days, where I was very much "C++ all the things because performance." But that's kind of my point: it's immaturity at work, here.