I agree with both points, just thought the commentary would amuse
Speaking of unique ideas, I am particularly curious as to whether or not the config concept can be adapted for a project I am working on (to replace component/mount, perhaps?)
Looking forward to seeing how that evolves!
@crimeminister: you might look at https://bitbucket.org/pupcus/kosmos ... which takes edn config and builds up a system with component... maybe ..
where are the docs?
it sounds interesting but not sure how to even start using it
@crimeminister: If your project already uses Component, it should be very straightforward to port to Arachne (the only thing that will change is how you define your system object).
@roberto: Do you mean Arachne itself? It’s still pre-release, under development. I raised funds to enable me to work full-time to actually build it, but that hasn’t started yet (it will next week, actually).
no, I meant that library kosmos
Thanks @clojuregeek, I will take a look
@luke: that's encouraging, thanks! Is the Arachne config system likely to be reusable elsewhere?
@crimeminister: The Arachne core is nothing but the config system, really. The web stuff is just additional modules and configuration options on top of that. So yes, if you have an Arachne project that doesn’t include any other modules, you’ll be left with just the config system.
@roberto: here's an example of using Kosmos for web and repl https://bitbucket.org/pupcus/kosmos-example
cool
@luke sounds flexible to the n^th
I suspect it will be a very short time before Arache the web framework is morphed to support other use cases
really, Arachne is a Clojure style railties
(for those who don't know, it's the "glue" for all Rails gems that compose the framework)
railties
is a good analogy. Only data-oriented instead of code/hook oriented.