←back to thread

310 points brylie | 3 comments | | HN request time: 0.616s | source
1. philips ◴[] No.43512767[source]
I feel the About page would be better for the audience who clearly already knows Django: https://plainframework.com/about/
replies(1): >>43512838 #
2. sroerick ◴[] No.43512838[source]
Thanks! This helps me understand his motivations for forking. I still don’t have a clear sense of how Plain is different or what the different approach is
replies(1): >>43512875 #
3. sroerick ◴[] No.43512875[source]
I also found this but I have to say I don’t really understand still.

I’ve used flask on projects but I’ve never started a project in flask and then migrated it to Django - I’m not really sure why you would do this. If I think a project would need admin panel or other Django features, I just make it in Django. That’s usually a pretty easy call to make when you start.

It seems like the fork is largely political? E.g. he just doesn’t like the way the mailing list is run, which is totally valid. I just don’t know what architecture he is building or what is different. I wish him well, though!

https://plainframework.com/faqs/