Re:Luminus – A Clojure Web Framework
by subsaharancoder on Monday April 13, 2020 @06:25PM
(#22860876)
Did you consider re-frame?
Yes, we considered both reagent and re-frame together. Around the time om.next was announced myself and a handful of others built a commercial product based on reagent, re-frame, and om.next. I only have good things to say about them, but there's a lot that they don't do and Fulcro's client-side solution is equally pleasant.
As a business building an extremely ambitious product on a tight budget, we want to be able to:
* Focus as much time and thought on building features that bring value to our customers, rather than, for example, building a bespoke protocol between the browser and back-end if a better alternative is available.
* Share early iterations of our application with everyone in our organization easily. Capture feedback and push out new iterations quickly.
* Be able to support new customers immediately. Our feature road-map will always be in constant flux, but at no point should our ability to make changes with confidence be compromised. In addition to feature development, tests and automation must be priorities. Our development and production environments must match.
* Be ready to onboard new team members. "Works on my laptop" is never acceptable. Enough of our application must be documented and automated so that anyone with a technical background "reasonably proficient" in our work can contribute without requiring hand-holding. Or course, we'd never turn down a request for help.
Our requirements are:
* Clojure, Clojurescript, and Datomic are immutable choices. We love these solutions for their simplicity and expressiveness. We believe these are the best choices available for achieving our long-term business goals.
* Be measurable. Our work should be guided by data not guesswork.
* Be testable. The entire application should have 100% test coverage as measured by its acceptance or integration tests (not unit tests). Changes should be made with confidence.
* Be performant. As builders of both the front-end and back-end components, we should encourage cooperation between them, not purposefully isolate them. Our customers and the end-user experience should be our priorities, not artificial divisions between software components or technical teams. Each component of the application should cooperate to support progressive enhancement where every URL is a real URL that, when requested, returns a server-side rendered page view. Further actions by the user result in browser-side changes through API calls and minimal component updates.
* Be pragmatic. We should be eager to innovate when the need arises. However, we should be humble enough to understand that sometimes, as software developers, we can become enamored with new toys that are entertaining, and possibly educational, but offer little business value. We should choose existing solutions to our problems that are acceptable enough over building our own solutions simply because we want to. For example, a standards-based protocol, like https://github.com/edn-query-language/eql, that allows clients to craft their own queries with little to no server-side updates is preferable to our current bespoke solution.
* Be documented and supported. Our choices should have active, helpful, and inclusive development communities built around them.
Our choices are:
* Rum, https://github.com/tonsky/rum
* Reagent, https://github.com/reagent-project/reagent * Hoplon, http://hoplon.io * Luminus, https://luminusweb.com * Pedestal, http://pedestal.io * Fulcro, https://fulcro.fulcrologic.com/ * Datomic Cloud, https://www.datomic.com