When comparing Luminus vs Beego, the Slant community recommends Beego for most people. In the question“What are the best backend web frameworks?” Beego is ranked 18th while Luminus is ranked 59th. The most important reason people chose Beego is:
Beego is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.
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 No need to find and install external libraries
Beego is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.
Pro Built-in tool which watches for changes
Beego has a built-in tool which watches the code for changes. This tool (called bee tool) can be configured to run any task once the code changes. It can run tests or reload and rebuild the whole project.
Pro Built in ORM
Beego's eloquent ORM is a simple and fast Object-Relational Mapping which helps with organizing the application's database. Beego examples and documentation all use the beego ORM. No need to learn to use and integrate another ORMs API.
Pro Captcha
Pro Auto testing
Cons
Con Very opinionated
Con Very opinionated
Con Non-idiomatic code
Con Builds may fail silently
Sometimes even though a build has failed, the pages will still render. Apparently it caches a previous build when the current one has a problem. This can be a frustrating though because it leaves you wondering why the page you are working on stopped working out of the blue.