sbt-ci-release VS Laminar

I'm a bit surprised to see sbt-ci-release (https://github.com/sbt/sbt-ci-release) not even mentioned. It's widely used for this.

The sooner JARs are on Maven, the better for all of us. With https://github.com/sbt/sbt-ci-release/ publishing is sooo easy.

The first thing you must try is running sbt publishLocal then, you should be able to depend on the artifact from another project, when that works, you will likely want to publish the artifacts somewhere, maven central is the most popular way but it requires some setup, you can use https://github.com/sbt/sbt-ci-release to auto-publish on new commits (it explains how to get a sonatype account), github-packages is very handy but it requires a github access token to pull the packages (https://github.com/djspiewak/sbt-github-packages).

> Veautiful - https://www.wbillingsley.com/veautiful/

Thanks for sharing, first time I see this project mentioned.

> Any day now, I'll get a chance to improve the documentation of the framework (and give it a proper release rather than using JitPack snapshots all the time).

It is worth commenting about https://github.com/sbt/sbt-ci-release which makes it simple to auto-publish to maven central.

Use https://github.com/sbt/sbt-ci-release

sbt-ci-release is a great one-stop shop for this. It handles sbt-pgp, sbt-release and sbt-sonatype for you, so you don't have to configure them individually yourself. The readme also has an easy to follow tutorial.

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.