clojure-cli-config VS Laminar

Programming Clojure 3rd edition does have some minimal coverage of the CLI but it just barely made it to publication and a lot has been added since. You might find the CLI guide (https://clojure.org/guides/deps_and_cli) and CLI reference (https://clojure.org/reference/deps_and_cli) to be helpful for some questions. The Practicalli guide (https://practical.li/clojure/) has a number of good pages and resources on repl, tools, and use.

Yeah this is grim.

There is https://github.com/practicalli/clojure-deps-edn which solves this but it’s not linked to from any official docs which seems a miss to me. As well as the config and full documentation, it also comes with a video walking you through a demo of all the features.

I was lost when I moved to deps from lein, but just forking and cloning https://github.com/practicalli/clojure-deps-edn as $HOME/.clojure solved the problem - this base deps.edn contained all the aliases I needed - creating a new project, searching and adding dependencies, hooking up data inspectors like portal or reveal, testing, code coverage, benchmarking, building uberjar etc. Moving to deps also introduced me to polylith [1], which has been very useful for building large multi-component projects

[1] https://polylith.gitbook.io/polylith/

When I'm looking for tooling related stuff I do always check practical.li (https://practical.li/clojure/) since it probably has a good, if terse, description and mostly has links to the good documentation (or at least the best available).

4. You need build tooling and it seemed the choices were lein (easy user experience but not “blessed” future direction? - not sure about what i’m saying here but it’s the understanding i formed). Tools.deps is the blessed approach but designed to customise the heck out of it - problematic for a beginner like me! Thankfully you can park the customisation for later and just get started with a well laid out starter https://github.com/practicalli/clojure-deps-edn - there’s even a video walks you through its features, all the inspectors and visualisers are nice to know about but not needed yet on a beginner journey

My quite niche open source project broke this threshold last year, via Github sponsorships. Of course, I put a lot of time into it, so it's not "passive income" or even "market rate income", but still, without these sponsorships I wouldn't be able to work on it so much.

The project is Laminar, a UI library for Scala.js https://laminar.dev

I've noticed that Laminar and the newly released Kyo point that they don't use a lot of macros as a feature. Laminar says "Easy to understand: no macros", while Kyo emphasizes "Note: defer is currently the only macro in Kyo. All other features use regular language constructs." It seems that using less macros is something library users will like.

https://laminar.dev/ might be what you need. Though I wish there was a more beginner friendly (I'm not from front-end world) tutorial for me to follow along.

Have you looked at Laminar and Tyrian? Especially Tyrian seems to be close to what you're looking for.

For Scala there is Laminar, which has an even flashier website with nice docs. I haven't tested it out though, as I have never used Scala.

I found this scala library called Laminar which looks super similar to solid. They use signals and has no virtual dom. State changes are represented by signals and events by event streams. Thus they seems to have feature parity with RXJS as they can model all sorts of async stuff. Best part is they get to keep writing their markup in C-style syntax than XML based JSX. It looks super elegant,minimalist and has type safety.

This is very true. I really hate svelte single file components. But then I tried JSX for breaking things down. I love solid but I don't feel really good about angle brackets within C style syntax. I saw this Scala library that stick with simple statically typed function syntax than html tags. I don't understand why people still wants to stick with xml like tags. In laminar markup is written like this scala div( h1("Hello world", color := "red"), inputCaption, input(inputMods, name := "fullName"), div( ">>", button("Submit"), "<<" ) ) I wish solid team makes their HyperScript syntax as performant as JSX.

Laminar (Scala framework) hasn't been mentioned yet so dropping it here as an awesome framework that support HTML-over-the-wire. It can be used together with React, HTMX, and many other frontend frameworks -- but doesn't have to be.

https://laminar.dev/

Scala.js core itself, which I maintain, does not need much innovation. We support all of Scala, and interact with any JavaScript library. That's what the core promises.

If you want to compare to Scala 3, it's worth pointing out that you can use Scala.js with any Scala version >= 2.12.2. In particular, you can use it with Scala 3 and benefit from all its innovations. ;)

Innovation comes mainly from libraries, notably UI libraries. Laminar (https://laminar.dev/) is a great example.

In terms of roadmap, we are mostly working on "boring" stuff: improving performance (of the generated code, and of the linker), fixing bugs when they get reported, etc.

Perhaps, when Wasm gets more features for deeper interoperability with JavaScript (manipulating objects notably), we will take another look at targeting Wasm. People usually expect all languages to target Wasm now, "because it's fast". Truth is, it's fast for languages with linear memory. There is no evidence yet that it will be fast for memory-managed languages with objects and virtual dispatch.