Plain – a web framework for building products with Python
plainframework.com
Plain – a web framework for building products with Python
1–10 of 168 posts
Re: Plain – a web framework for building products with Python
#2How come Plain looks so much like Django?
Re: Plain – a web framework for building products with Python
#3How come Plain looks so much like Django?
It's a fork of Django. It says clearly on the docs.
Re: Plain – a web framework for building products with Python
#4How come Plain looks so much like Django?
Third sentence on the page.
Third sentence.
Re: Plain – a web framework for building products with Python
#5How come Plain looks so much like Django?
It's a fork of Django.
Re: Plain – a web framework for building products with Python
#6How come Plain looks so much like Django?
Because it's a fork
Re: Plain – a web framework for building products with Python
#7This looks pretty cool! Would be nice to see an integration with Tetra
Re: Plain – a web framework for building products with Python
#8Tbh why should I use this over Django? Less docs and knowledge around it. Less maintainers. Idk seems like a business risk to invest real time in it for me
Re: Plain – a web framework for building products with Python
#9I feel the About page would be better for the audience who clearly already knows Django: https://plainframework.com/about/
Re: Plain – a web framework for building products with Python
#10> Plain is a fork of Django
Why. This makes me sad. Plain looks great, but Django's strength is its maturity and amazing, enduring community built on contributions from thousands. Forking it will at best split contributions and mean infrequent merges, and at worst means Plain users lose out on Django improvements and Django users lose out on Plain patches.
It seems like Plain could be just a set of Django packages known to work together, and perhaps a new wrapper script replacing `django-admin`, but instead it appears it is a true fork.
Plain basically looks great. I love Django, and this is a long list of things that I'd need on top of Django anyway. Would I use a framework on top of a framework like this? I'm not sure. I just wish it was built in a way that contributed to the Django community instead of one that divides it.