286 karma · joined November 1, 2017
My guess: - The Django codesource is easier to read - Maybe error messages are cleaner? (just a supposition.. I don't know)
Garanty of compatibility between Django and ALL my external packages is a lot more valuable that a responsive admin panel and a new syntax for urls.
I would love "important" (yeah it's opiniated) packages move to the official Django repo (like Channels), to help reduce this risk when migrating. It's actually surprising how often I can't find the compatibility information of a Django package.
Either I find some ES5 resources, and I have the feeling to spend my time learning stuff I'll never use by myself. Either I find some ES6 resources that need ES5 knowledge as prior requirements.
For example, even some may say I should, I don't wan't to be teached that before, we used "var", and now we use "let". I just want to learn the "let" version.
Google Photos is shitty and Google already got too much information about me.