@andrewboltachev Yeah, Arachne intends to make it easy to get started on front end develoment. That said, it won’t introduce as much novelty as it does on the back end; it will help out with getting Figwheel/CLJS up and running, but then it pretty much gets out of your way. You’ll use Rum/Reagent/Om/whatever the same way you always did, Arachne doesn’t bring anything new or opinionated to the table the way it does on the backend.
That could change of course, there’s nothing preventing Arachne modules from providing front end behavior. I just haven’t focused on it, since I think there’s a decent number of front-end solutions out there already. It’s not as much of a pain point for me so far.
I am about ready to try my hand at creating a module and am curious what the plan is for organizing the Arachne module ecosystem, e.g. a Clojure-style approach with a small set of standard libraries, and most things live outside of core? Having a larger set of "blessed" contributed modules might fit better with a batteries-included approach, though.
Depends on what the module is
basically if it is one I was planning on being the core set I’d be happy to onboard it 🙂
assuming you’re ok with that of course
Cool, was thinking to wrap Carmine to create a Redis plugin, more or less, as I routinely need that functionality (and because it seems modest enough I might not get lost in the weeds while learning)
Would be totally cool with contributing module(s), and hope more folks pile on
Actually, is there a module wish list anywhere?
not a formal one
On another topic: searching through the Slack logs suggests I am not the first to wonder about the complementarity of Vase and Arachne
Vase takes on a subset of what Arachne aims to do. Vase makes it easy to declaratively specify microservices backed by Datomic, Arachne aims to declaratively specify any kind of web application backed by any database.
For the specific case of a microservice backed by Datomic, it’s likely that I’ll just wrap Vase.
@crimeminister I would love to see a Redis module. However, you should be aware that the Last Big Piece I’m working on for Arachne is a “data abstraction layer” that allows a unified way to access multiple different data stores (so that Modules can store data without a hard dependency on a particular persistence tool)
Nifty, I am just getting familiar with Vase, but being able to "plug in" another database module so that
#vase/query used another syntax for the selected database could be nifty
Unfortunately that’s not quite ready yet, but when it is it’s probably something you’ll want to be aware of.
Thanks for the heads up Luke
I will keep paying attention, perhaps bite off something a little smaller for learning purposes, and revisit
Glad to see people are interested!
Definitely let me know any way I can help
There are so many things I want to be working on right now… I’d love to be writing more tutorials and writing an admin interface/config explorer.
But I think finishing Chimera (the data abstraction layer) needs to be the priority now. As I said it’s the last big dependency, that will unlock a lot more modules
Beat that level boss, and we all level up with you ;)
Reminds me, the Django admin docs system is kind of nifty, with autogenerated doc pages
I imagine Arachne would use the config DB to great effect for documentation and swagger-like capability
Thanks for the feedback, and have a good one!
Oh yeah, that’s definitely in the roadmap
need to bootstrap though 🙂