4 ms·
For such a comprehensive list, no mention of tornado?
by rglullis 7y ago
For such a comprehensive list, no mention of tornado?
- nine_k 7y agoIs Tornado still relevant if you can use async for multiplexed IO?
- csytan 7y agoI've been using Tornado for coming on 6 years. It's a great example of a solid, well maintained project. Why it's not more popular I'll never know. Yes it's still relevant because your framework needs to be able to run on the asyncio event loop (a feature which Tornado added early on).
- jbarham 7y agoThat surprised me too. IMHO Tornado should be #3 after Django and Flask since AFAIK it has the best built-in support for writing hybrid HTTP/WebSocket servers in Python. I use Tornado to serve the WebSocket backend for https://www.slickdns.com/live/ https://www.slickdns.com/live/. I've also used Django Channels to add WebSocket support to a Django app and found it very cumbersome compared to Tornado.
- no_wizard 7y ago+1 For Tornado. I'm curious if you care for their templates or not, though.
- jbarham 7y agoSorry, I haven't used Tornado's templates enough to compare them with e.g. Django's. Essentially all I use Tornado for is to publish a WebSocket endpoint, and for that specific purpose it's great. For building conventional web apps I'm very happy with Django and its templates.
- codesushi42 7y agoFun fact: Tornado was created by FriendFeed, a completely unmemorable social "aggregator" that was gobbled up by Facebook during the social media craze.
- yla92 7y agoYeah. It's odd. We use Tornado for all our API/microservices at work and it's been a pleasure. More and more libraries are getting asyncio support as well and they integrate well with Tornado.