Fork me on GitHub
#lumo
<
2020-02-21
>
kipz16:02:00

I ❤️ lumo, and really believe in the approach, especially the bit about embracing the host platform and tools. I've recently been trying to get an nrepl integration working - looks promising based on https://github.com/djblue/nrepl-cljs. I'm also interested in the idea of a solid browser development flow. Surely others are too? It would make me very sad if this project were to die.

hlolli18:02:43

I don't think Lumo is "dying" anytime soon. I don't expect new features, but that also depends on you and anyone willing to make a contribution. I expect Antonio or Andrea to keep lumo in sync with latest clojure/script and node releases. There's still great untapped potential with expanding lumo, but competing with jvm based dev tools is a lost battle in terms of speed, not an excuse not to push for self-hosted clojurescript compiler research and experimentations.

kipz19:02:12

Do mean specifically competing with the likes of figwheel and shadow, lein, deps? Why do you think that is?

hlolli20:02:42

many reasons for it, but I'm not a compiler researcher, but the jvm runtime is just lightyears ahead in almost every regard, cpu, multithreading and memory. But the libraries and their stability in java is enough for library maintainers to build powerful tools on solid foundation than the wilderness of npm packages. But node or any native js based environment will probably catch up big part of this difference in next decade.

kipz20:02:31

Agreed re: jvm vs node (at least for now), but I guess I always envisaged something like lumo also providing a killer cljs web-browser experience (like shadow-cljs, but without deps.edn, JVM and so on).

hlolli20:02:30

sooner or later, it will arrive

kipz20:02:09

It does seem rather obvious that it will, but given what's going on in the rest of the cljs community around shadow, figwheel, etc, and the trouble lumo is in, I'm questioning my logic here. Lumo seems like a good basis for building such a stack. I'm no compiler researcher either, but my smell-ometer goes crazy when my projects have two dependency descriptors (in fact, with shadow-cljs and cursive, I have three!).

kipz20:02:07

I wonder what the Clojure(script) leads think about all this? It's hard to imagine that they think ultimately the JVM has a roll in the cljs landscape (beyond tactical tooling solutions in the short term).

anmonteiro18:02:55

> I expect Antonio or Andrea to keep lumo in sync with latest clojure/script and node releases. Don’t.

👍 1
hlolli18:02:38

expect was a wrong word here, but I haven't followed up on recent events. Tough still maintaining and fixing it on nixpkgs. And using lumo ofc.

anmonteiro18:02:23

To be clear: Lumo is not going to get any updates. I’m not interested in spending any more time working on it or reviewing PRs

hlolli18:02:39

Ok, that's clear enough, so I'll fork it.

anmonteiro18:02:53

Happy to add you as a collaborator

borkdude21:02:58

"Donating" the project to clj-commons could also work, but that still has the problem of finding someone who wants and is able to maintain it

👀 1