excoptional
Laminar
excoptional | Laminar | |
---|---|---|
5 | 26 | |
11 | 716 | |
- | - | |
0.0 | 8.3 | |
over 2 years ago | about 2 months ago | |
HTML | Scala | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
excoptional
-
From ES6 to Scala: Basics
> I mean Scala because I guess it actually has it, but worth pointing out it's like 30 LOC to define one for JS, depending on how many convenience methods you want.
Here's one I wrote: https://github.com/sbernheim4/excoptional
I fully believe it to be one of the best Option implementations in JS/TS
- Understanding the Power of Lisp (2020)
-
[AskJS] How often do you use the ES6+(ES7, ES8, ES9 and ES10) syntax? Do you like it? Does it help?
https://github.com/sbernheim4/excoptional is an option object for js/ts
-
Functors, Applicatives, and Monads in Pictures
One benefit to keeping your value wrapped in a Maybe is that as you transform and manipulate the value and pass it around in your system, you leave it up to the last place in your system that uses the value to define the fallback value in the case of a None rather than defining a fallback value part way through and establish a convention that the fallback value means nothing was found at some other part of your system.
Another benefit to using Maybes is that you avoid the rigamarole of null checks at every call site where you want to use the value. If you have a function that returns null or a value, whenever you call that function you'll always have to add an if guard to validate it's not null. If it is, that function itself may return null, and callers to it will again have to implement the same check.
I wrote a JS implementation of the Option object and the readme has lots of specific examples about these benefits: https://github.com/sbernheim4/excoptional
- Show HN: An Option Object for JavaScript and TypeScript
Laminar
-
Ask HN: Those making $500/month on side projects in 2024 – Show and tell
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
- The golden age of Kotlin and its uncertain future
-
Why would users avoid a library that makes heavy use of macros in Scala 3?
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.
-
Is there any book or course about Scala front-end development?
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.
-
Designing an HTML Component system
Have you looked at Laminar and Tyrian? Especially Tyrian seems to be close to what you're looking for.
-
The Quest for the Ultimate GUI Framework
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.
-
Solid like scala library that has more powerful reactive primitives and lean syntax?
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.
-
Solid JS compared to svelte?
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.
-
Ask HN: What companies are embracing “HTML over the wire”?
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/
-
10 Years of Scala.js
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.
What are some alternatives?
sicp - HTML5/EPUB3 version of SICP
OutWatch - The Functional and Reactive Web-Frontend Library for Scala.js
Chimney - Scala library for boilerplate-free, type-safe data transformations
tyrian - Elm-inspired Scala UI library.
diode - Scala library for managing immutable application model
Binding.scala - Reactive data-binding for Scala
whirlisp - A whirlwind Lisp adventure
Udash - Scala framework for building beautiful and maintainable web applications.
mostly-adequate-guide - Mostly adequate guide to FP (in javascript)
scalajs-react - Facebook's React on Scala.JS
slinky - Write Scala.js React apps just like you would in ES6