5 ms·
Man... when it's laid out like that, it does seem a bit insane. By comparison Python's primary web framework in 2012 was Django, and today it remains Django. D
by rectangletangle 9y ago
Man... when it's laid out like that, it does seem a bit insane.
By comparison Python's primary web framework in 2012 was Django, and today it remains Django. Despite this relatively glacial pace, there's been a ton of improvement to Django, and the surrounding Python ecosystem. A more conservative development culture can pay off sometimes, since it allows the community as a whole to focus on polishing the existing ecosystem. As opposed to dropping Django when "real time" Websockets were all the rage, there was a concerted effort to include it in the framework with the Django Channels project.
- polskibus 9y agoDon't forget that move towards microservices and Go caused many Django devs to move away from it.
- rectangletangle 9y agoThat's certainly true for that particular niche. However Python has certainly come into it's own over that timespan, with the rise of various machine learning approaches. This reinvigoration, seems to have manifested in the web side of the language too, seeing as many models eventually need some form of HTTP server. Admittedly though the community isn't perfect. There was quite a schism over Python 2 vs 3 for a while. Thankfully it's looking like that may be past us. Anecdotally the Python community seems more active than ever.