Cocoa (OS X) vs Tornado: What are the differences?
Developers describe Cocoa (OS X) as "The Cocoa frameworks consist of libraries, APIs, and runtimes that form the development layer for all of OS X". Much of Cocoa is implemented in Objective-C, an object-oriented language that is compiled to run at incredible speed, yet employs a truly dynamic runtime making it uniquely flexible. Because Objective-C is a superset of C, it is easy to mix C and even C++ into your Cocoa applications. On the other hand, Tornado is detailed as "A Python web framework and asynchronous networking library, originally developed at FriendFeed". By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.
Cocoa (OS X) and Tornado can be primarily classified as "Frameworks (Full Stack)" tools.
"Great community " is the primary reason why developers consider Cocoa (OS X) over the competitors, whereas "Open source" was stated as the key factor in picking Tornado.
Tornado is an open source tool with 18K GitHub stars and 4.98K GitHub forks. Here's a link to Tornado's open source repository on GitHub.
What is Cocoa (OS X)?
What is Tornado?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Cocoa (OS X)?
Sign up to get full access to all the companiesMake informed product decisions
Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.
SpreadServe's RealTimeWebServer is built in Tornado. Spreadsheets loaded into SpreadServeEngine instances are projected into browsers using Tornado. Server side recalcs are pushed to the browser using web sockets.
setup an api for a client with tornado backend. incredibly fast and lightweight. unfortunately breaks down when using third party libraries which block internally.