excoptional
scalajs-react
excoptional | scalajs-react | |
---|---|---|
5 | 13 | |
11 | 1,635 | |
- | - | |
0.0 | 4.3 | |
over 2 years ago | 2 months ago | |
HTML | Scala | |
GNU General Public License v3.0 only | Apache License 2.0 |
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
scalajs-react
- Scala DevInTraining looking to contribute to projects
-
Monorepo: seeking for an advice for bi-lang project
Then there's scalajs-react, which can be integrated with existing React ecosystem, but it's just sooo compex: macros, 5-6 type parameters, hundreds and hundreds of cryptic types. We decided to stick with TypeScript instead.
-
Show HN: Simple games ported to Scala 3 – Try them in the browser
Or the OG React Scala.js library: https://github.com/japgolly/scalajs-react
- What are Diode alternatives?
-
From ES6 to Scala: Basics
Japgolly has put a ton of time and care into https://github.com/japgolly/scalajs-react which is a complete React binding in scalajs. This paired with something like Diode (https://github.com/suzaku-io/diode) and you get a full frontend solution in scalajs.
- scalajs-react 2.0.0 final is finally out of the oven! A lot of work and love has gone into this release. Check out what's new here.
-
What's the maturity level of ScalaJS?
We've got server-side rendering with scalajs-react and scala-graal. Here's a tutorial if anyone's interested. What's really cool about scala-graal is that it has some pretty cool caching so that even with dynamic inputs, you can render pages in nanoseconds (as opposed to 10+ or even 100+ ms).
-
I know the basics, what’s next?
You can use React with Scala.js, and also most other common JS libraries. Or you can use a Scala.js specific library like Laminar, which I haven't tried myself but it looks nice.
-
What language(s) pair well with Rust (learning, using, etc.)? Also, what other languages did you learn before learning Rust?
I don't have a lot of experience with it, but many seem to be very pleased with it. Interop with JS is good and you can use React and other common JS libraries, but there is also Scala.js specific frameworks like Laminar.
-
Does it make sense to use Scala.js/Laminar in the context of a startup?
https://github.com/japgolly/scalajs-react is pretty heavily used as well, and fairly active as a project. In short, building it off of that wouldn't be a huge risk over typescript, and might even be a net win in the long run, as you could re-use some stuff from the backend in the front-end.
What are some alternatives?
sicp - HTML5/EPUB3 version of SICP
slinky - Write Scala.js React apps just like you would in ES6
Chimney - Scala library for boilerplate-free, type-safe data transformations
Laminar - Simple, expressive, and safe UI library for Scala.js
diode - Scala library for managing immutable application model
Scala.js - Scala.js, the Scala to JavaScript compiler
whirlisp - A whirlwind Lisp adventure
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
mostly-adequate-guide - Mostly adequate guide to FP (in javascript)
React4s - Production ready React wrapper for Scala.js - composable lifecycle - no memoization, no macros, no implicits.
tyrian - Elm-inspired Scala UI library.
sri