3 ms·
We've simplified the architecture, by reducing the number of concepts down to just three: components, bases, and projects. The tool is simpler, gives faster fee
by logarhythm 6y ago
We've simplified the architecture, by reducing the number of concepts down to just three: components, bases, and projects. The tool is simpler, gives faster feedback, and a better visualisation of your projects, due to (amount other design changes) switching from Leiningen to tools.deps.
The original version of the tool used:
- Leiningen to compile and build the artefacts
- symlinks to keep the code in one place (but allow for reuse in multiple artefacts)
- "workspace interfaces" (empty component interfaces) to guarantee the decoupling between components
The new version of the tool uses:
- tools.deps to build the artefacts and remove the need for symlinks
- static code analysis to remove the need for "workspace components"
- robto 6y agoNice! I went through the poly tool readme and I'm really impressed with the improvements. One thing I don't see highlighted that I'm curious about: have you used it to build cljs projects? Since shadow-cljs has deps.edn integration, I think it could theoretically work, though the repl might be a bit twitchy.