| We're talking about Python frameworks, so "all of them". It's not like they're optimized to win req/s competitions or run on embedded nanocontrollers. "Developer productivity" is so vague, I'd regard it as weasely if it would be in a framework's description. What's the developers aim and workflow? Depending on that, you can probably make an argument for most frameworks on the list. - Django is your all-batteries included framework for standard CRUD with an integrated admin interface. For "average" jobs that feeds the productivity. - But then you can make the argument that this approach gets in the way if you deviate from the norm, and Flask is the new productive toy. - And isn't all the hubbub about a "pythonic" style getting in the way? Web2Py has some magic that might not be mainstream, but is just bound to ramp up productivity! (No experience myself, just using this for the argument and for nostalgia when every mention of it brought the main developer in the thread, arguing about this, just like redux today) - But hey, man, we're all doing JS frontends and just need a web scale API. Erm, okay, then Django Rest Framework? The various Flask addons? FastAPI? - I'm an ex-00s-Java developer who misses writing XML by hand. What's best for my productivity? Well, what about the endless joys of writing YAML by hand! Use connexion... Salt this discussion with complaints about speed (charge of the Rust brigade), deployment hassles (Gophers emerge from the ground) and the collective "this isn't static and thus we're doooomed!" outcries (erm, Haskell?). (And from the Waldorf & Statler balcony, enterprise programmers who get paid by the hour, laughing about "productivity") |