Clojurians Log v2

I'm not sure I could have a decent stab at those right now. But I would be interested in being in the passenger seat. Be that we do some live collaboration on it together or I'll just look at the changes when the commit is made :)

@grounded_sage I’m not interested in e.g. livestreaming fixing a bug in Lumo or something like that

I’m available however to provide any necessary guidance someone might need in working in an issue

could also set up a Lumo hacking session in person at the Conj if people are interested

I'm location restricted. Otherwise I would love to do a hacking session. I'm exploring setting up mob programming groups to work on open source Clojure work as I am looking for something to get experience. I'll take a proper look at Lumo when I have some time in the next week or so and see if there is anything I think I can tackle.

@richiardiandrea hmm I haven't though about that, huckleberry is 100% cljs + node, you don't need the JVM to use it

you do need the jvm to modify it though

@stbgz and you need the JVM to import it in lumo as well 😄 Like other libraries to be fair, but we should change that 😉

to import it? you mean to add it to the classpath?

you don't actually, that's what calvin is for

I mean, say I want to use only huckleberry as a lib, it is deployed as maven dep now, what if we start deploying lumo compatible things on npm instead?

where is deployed does not matter much, npm clojars, it should be transparent to you as a dev where they are, you should just be able to say: I need this. And the tool should figure out the rest

that poses other questions of course for lumo itself (for example macro files need to be read from node_modules)

yes except that no tool is the best tool 😄

ok better to say, let's use npm/`yarn` for everything 😄

I'll just quote you back "no tool is the best tool" 😄

yeah well, still you have to resolve the deps somehow

if huckleberry, or others for that matter, could be deployed on npm, one could use only yarn...

ah I see

you want to use yarn to build

the process should be pretty straight forward, use cljs-jvm to create the js file, create a package file for it and publish that to npm

I would like to avoid resolving Maven dependencies...especially if I work with lumo only, both repl and compilation, that is my current dream 😄

if you go down that path, you'll miss out on basically all clojars deps

I don't need them, I can install them directly from npm

sorry

after conversion of course

ah I see, sure

so not really many cljs libs I miss from clojars

one is andare, which can be converted deployed to npm

reagent comes to mind

I mean maybe for a particular is fine, but I think it is not a great answer for the comunity as a whole

in this you are definitely right

unless someone republishes all clojars in npm

but sometimes things start and people see "that it is better", and keep doing it

wouldn't it be better to not care where the dependency is published?

yeah, that won't work, I don't thing bootstrap will ever be able to compile the same things as cljs-jvm

Another problem is that at the moment (big) companies need to have two mirrors, one is a Nexus mirror to Clojars/Central, the other is to npmjs. That is of course a lot to ask.

Because they don't like to consume things directly from the net

it would be awesome to get feedback on this, maybe I will set up some survey

You don’t lose access to the Clojars ecosystem

if I understand correctly, if you had huckleberry deployed to NPM we could use that to resolve Clojars deps

yep