How is fixing Logging out via GET doing - 10 years old bugfix request in Django?
https://code.djangoproject.com/ticket/15619
ActiveStorage is relatively new feature which also isn’t really big of a deal. Most issues mentioned in above links can indeed be solved by using the direct methods without given abstraction.
Using both Rails and Django I much prefer Rails, but I don’t see a point in bashing the other using single picked issues as a general argument for how crappy the framework/community is.
George Claghorn doesn't seem like an easy person to work with.
Re:Ask HN: Go-to web stack today?
by morpheuskafka on Sunday January 06, 2019 @12:56AM
(#18836818)
Also (IMO) python is a nice compromise between Ruby and JS and C/Java style. It's dynamically types but has classes out of the box, and it has Ruby "magic" methods but as double unders so you can actually tell that they are magic from the source.
Re:Ask HN: Go-to web stack today?
by faitswulff on Saturday January 05, 2019 @10:28AM
(#18832075)
Does it really count as Rails Core dumping on a widely requested feature when (in the second link) both rafaelfranca and dhh are in favor?
Having used both Django and Rails extensively recently, I disagree. Maybe 5 years ago, yes.
For two examples I ran into yesterday, check out https://github.com/rails/rails/issues/32790 and https://github.com/rails/rails/issues/31419
which feature Rails Core simply taking a dump on widely requested features that some people need for more modern architectures. And a popular note from the second issue:
> Django has had a mechanism like this for years, and it's a delight to work with — it feels like the right balance of indirection and simplicity.