Cool release! Thank you for this. It's always great to see production code get released as opposed to pet projects.
What's interesting to me is that even though it's a flask app, it seems to be re-implementing large chunks of Django:
- Similar directory hierarchy including folder-per-app, templates, config
- A big settings object that gets passed around to things like Celery
- SQLAlchemy for the ORM/database glue, some other components for migration management
- Re-implemented authentication that has a very similar feature set to django.contrib.auth
This convergence reinforces that I should keep using Django or Rails for new web/mobile products. I find myself doing all of the above when using Go or Haskell for the same task.
I'm a big believer in using an "everything but the kitchen sink" kind of framework like Django or Rails for MVP or very early versions of a web product.
The fact that they're typically opinionated about how basic things should be set up can save you from wasting time/analysis paralysis on inconsequential decisions and help get a prototype running, at which point you can decide whether it's a good fit or if you want to factor parts onto another platform.
I find that Django composes a lot more nicely than Rails, and of course that's not necessarily good nor bad; really depends on the use case. To me, Django feels like a Ford F-150 where everything is more or less exposed and easy to hack on. Rails is more like a tight well-oiled VW that runs very smoothly but may make you bend over backwards a bit to use an aftermarket part.
My pipedream is a framework as comprehensive and mature as either of these two, but in a language with a good static type system to save on 50-80% of tests, and enjoyment of many other benefits.
Version 1 was our primary product for 16 months. It still has customers using it at suite.staffjoy.com. We are helping some of those customers run the software on prem during the shutdown.
Wasn't trying to cast aspersions/take anything away: I think it's great that you are open sourcing anything. Kudos.
I was just pointing out that this infrastructure might have been great to start, but you guys moved to a very different, in terms of architecture , v2.
What's interesting to me is that even though it's a flask app, it seems to be re-implementing large chunks of Django:
- Similar directory hierarchy including folder-per-app, templates, config
- A big settings object that gets passed around to things like Celery
- SQLAlchemy for the ORM/database glue, some other components for migration management
- Re-implemented authentication that has a very similar feature set to django.contrib.auth
This convergence reinforces that I should keep using Django or Rails for new web/mobile products. I find myself doing all of the above when using Go or Haskell for the same task.