When comparing Luminus 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 Luminus is ranked 59th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro ClojureScript for client-side scripting
Luminus allows using ClojureScript for client-side development. This allows sharing things like validation logic between the server and the client.
Pro Luminus is flexible
Luminus is built on a stack of composable libraries that can be easily swapped to make the application fit the needs of the user. The applications are generated using Leiningen templates and can be initialized with a specific set of features, such as database connections, needed for a specific application.
Pro Good documentation
Luminus provides step-by-step documentation on how to accomplish common tasks.
Pro Simple to setup and use
Luminus is small and flexible. It's geared towards interactive development using the REPL. You can see your changes as you're working without having to restart the application.
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.