When comparing Padrino vs N2O, the Slant community recommends N2O for most people. In the question“What are the best backend web frameworks?” N2O is ranked 29th while Padrino is ranked 43rd.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Ruby framework based on Sinatra - with extra features
Padrino is as fast as Sinatra, but extra features are added to this framework. They include namespaced route aliases, nested routes, controllers, a mailer system, unified logging and a lot more.
Pro Open source
Padrino is open-source.
Pro Fast binary data
Pro Binary encoding and protocols
Here is a list of types of endpoints which are supported by EMQ and accesible to N2O apps: WebSockets, MQTT, MQTT-SN, TCP, UDP, CoAP. Normal use of N2O as a Web Framework or a Web Application Server is through WebSockets, but for IoT and MQTT applications it could be served through UDP or SCTP protocols providing application level message delivery consistency.
Cons
Con Unfriendly developer community
Developers are often rude and unfriendly to users.
Con Bad documentation
It has bad documentation, which leaves out crucial steps, making it hard to learn.