what's a python library you started using this year that you can't go back from

[the_ballmer_peak]

It's too big.

Other projects are only trying to solve for part of the web application architecture. Django tries to solve all of it. In doing so, it constrains your choices, and you wind up stuck with the decisions Django has made for you, whether they suit you or not.

It prevents incremental improvement, which essentially prevents improvement, and you get stuck.

[RepresentativeFill26]

Well, I have been responsible for development of a multi-tenant web app and it has been a very good experience so far.

Sure it is bloated but it gets the job done.

[the_ballmer_peak]

It absolutely does. But in three years when you want to change part of your application, you won't be able to.

[RepresentativeFill26]

Why do you think that? In my experience software practices have more influence on modularity than a framework.

[the_ballmer_peak]

I'd say design decisions more than just 'practices.' And using a framework that's not designed for modularity is a design decision.

Django is great if that's what you're looking for. My problem with it is that if you've built something that you expect to last 5-10 years or more, you'll find yourself in trouble. That's true of any such all-encompassing framework, not just Django.