While this is a great talk, and a great web app, I think there is a bit of over compensation on their part, because of them being in the unique position of having founded and had to manage the ticket burden of a very popular (backend) framework - Django.

It's odd because in the talk he advocates patterns over frameworks. Django is an implementation of MVC, as is well known. What is the value of implementing MVC again in Python when someone really has done that job for you?

There is a bit of a slight of hand here. If someone had built a frontend framework in Javascript and was now no longer advocating them, that would be a cleaner argument. But we have a shift of abstraction here from front to back end, when the two domains need to deal with different worries.

Backend or frontend, I don't think it makes a difference for the points of this talk: build your own codebase, use what you need as you need it, consider following established patterns if you find ones that fit your problem.

Django is used as an example of the downsides of a framework, and how the complexity of frameworks explode even though any given user only needs a small percentage of the features.

Adrian here. Thanks! Yes, Soundslice doesn’t use any JS frameworks, and my thoughts on the matter still stand.