←back to thread

310 points brylie | 1 comments | | HN request time: 0.249s | 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 #
pbreit ◴[] No.43513037[source]
At this point, seems like the server is mostly a data access layer spitting out JSON for JavaScript, Java and Swift clients.
replies(2): >>43514981 #>>43515627 #
1. evantbyrne ◴[] No.43514981[source]
That is the trend, but just because something is popular doesn't make it optimal. Developers are also excited about marginal gains from LLMs. The reality though is that most of those same teams could 2x their productivity by going back to a more retro stack, without losing quality, and also lowering costs in hosting and devops. The move to multi-service was for scale, but somewhere along the line people forgot to measure whether they needed that complexity at all.