3 ms·
I understand that's why people think Express is great, but in practice you end up rebuilding a lot of the same functionality. It can work okay in a microservice
by morgante 10y ago
I understand that's why people think Express is great, but in practice you end up rebuilding a lot of the same functionality. It can work okay in a microservices architecture, but in the end you have to reinvent a lot of the wheel.
There's also a common misconception that Django is a "walled in" environment. It provides sensible default utilities for everything, but you actually don't need to use them at all. For example, you can bring anything from your own template engine to your own ORM if you want to.
- overcast 10y agoNot sure what wheels I'm reinventing, I just choose to include the libraries that are correct for the application. If I don't use half the stuff Django is offering me, only to bring in my own. Aren't we back to the same place?
- morgante 10y agoThe difference is that the Django ecosystem really focuses on developer productivity and has strong best practices. Look at 5 different Express apps and you'll find 5 different ways of structuring models, controllers, and routes. Plus the fact that Django has some suggested defaults allows you to be very productive with them. For example, I really haven't found any equivalent to DRF for Express. I want to make it clear I'm not some Node hater. Probably half my projects are still in Node, but I do know I'm much high productivity in Django.
- overcast 10y agoSo really all we're seeking here is a standard for application layout. I really really dislike being forced into some heavy handed framework, not that Django is that, but it's on the topic of discussion.