←back to thread

310 points brylie | 1 comments | | HN request time: 0.253s | source
Show context
danpalmer ◴[] No.43512772[source]
> 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.

replies(12): >>43512813 #>>43512854 #>>43512920 #>>43513037 #>>43513063 #>>43513104 #>>43513224 #>>43513342 #>>43513446 #>>43514468 #>>43516716 #>>43516766 #
earnesti ◴[] No.43512813[source]
I don't get it, if you don't like it, don't use it, but why feel sad about it? Someone is developing something new and giving it out for free.
replies(1): >>43512833 #
antoniojtorres ◴[] No.43512833[source]
They aren’t sad about being forced to use something. They are expressing their opinion about split efforts in the Django community.
replies(2): >>43512973 #>>43513701 #
1. jiknstring ◴[] No.43513701[source]
I think it's perfectly fine to have split effort when you have differing views and goals on something. Developing two exact same things with same goal and purpose might not be fruitful, but variety and options don't usually hurt