856 karma · joined December 6, 2009
Frequent speaker and author on tech subjects. Expert in building, scaling and maintaining complex web applications with Python, Django, React, PostgreSQL usually on Kubernetes.
Email: frank@revsys.com Twitter: @fwiles Mastodon: https://frankwiles.social/@frank Homepage: https://www.frankwiles.com/ LinkedIn: https://www.linkedin.com/in/frankwiles/ Work: https://www.revsys.com
Everyone needs to know it’s ok to not be ok.
We did 10 runs of each on a large AWS instance and averaged the results.
The build info and benchmark results are up here https://github.com/revsys/optimized-python-docker if we’re wrong about something please let us know.
However, definitely agree that any optimization like this could have negative performance consequences for certain specific bits of code. But that’s likely true of any build to the next.
If you need help please get it. Here is one resource:
http://www.headquarterscounselingcenter.org/
Disclaimer, I'm on tbe Board of Directors. But if not this resource please get help from somewhere. There are people here for you.
Sure, for that VERY specific (and not very common) use case U-Hauls beat F-150s. However, I think we can all agree that F-150s are far more versitle for most use cases, up to including something trivial like heading to Starbucks for a quick coffee.
We used Electron (well still called Atom-shell back when we started) for building Spectrum (https://www.devspectrum.com) which we charge per seat and it's been a great development experience and it's certainly performant enough to handle tons of local logging capture/filtering.
Also one thing I'd like to point out, that is a frequent source of confusion, is that Django isn't a CMS. It's a general purpose web framework, akin to Rails or Express. It just happens to have come from CMS roots and is particularly adept at "content" type systems.
Disclaimer: I'm pretty biased about Django :)