3 ms·

The lack of typing was a huge pain. It sucks to not be able to navigate to the underlying library in your IDE, or navigate upwards in the calling stack etc beca

The lack of typing was a huge pain. It sucks to not be able to navigate to the underlying library in your IDE, or navigate upwards in the calling stack etc because it is (afaik) hard for the IDE to help you navigate through this without typing. The larger the project, the slower it makes you since reading is 99% of your work. Django, Flask etc have a lot of magic annotation business which became untenable after 2-3 years. It is really hard to reason about what they do and in what order. Much easier to reason about it with Java and Golang.

Jugurtha 5y ago
>It sucks to not be able to navigate to the underlying library in your IDE Which IDE is that? Those I've seen you hit a key, say F12, when your cursor is on a function or a class and it takes you right to where it's defined in whatever module, or shows you a list of objects with the same name in the project and you pick the one you're interested in. >Django, Flask etc have a lot of magic annotation business which became untenable after 2-3 years. Which ones? There is some kind of magic in g, and the application context. Are you talking about those? What did it prevent you from doing, and how did you get around these issues?
- silentsea90 5y ago
  It has been over 1.5 years, but it was Pycharm. I am not sure if my IDE was borked, but I remember struggling with both finding the library and the list of usages. I am happy to concede it may be my poor IDE setup. We used Django at a startup I was at in 2018, so my memory fails me on the exact issues since it has been so long. I will have to revisit Django and try to find what it was.