When comparing Lift 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 Lift is ranked 58th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro View First architecture
Lift apparently pioneered the View First architecture, which is greatly superior to MVC for implementing DRY code. A common issue with MVC that it solves is the need to place a single component on multiple different pages, which, with MVC architecture, tends to require logic to be duplicated across multiple controllers. With View First, the code supporting the component is associated directly with the component, enabling the component to be inserted in many contexts with ease and without any additional code.
Pro Excellent security
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.