excoptional
diode
excoptional | diode | |
---|---|---|
5 | 4 | |
11 | 640 | |
- | 0.0% | |
0.0 | 0.0 | |
over 2 years ago | 19 days 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
diode
-
What are Diode alternatives?
I've started with scalajs-react. Overall the experience was good (perhaps the overloaded API is my biggest concern, but we can live with that). Then I stumbled upon a problem where I need to propagate a state change from two leaf components and found out I need something like this Redux thing. I trtied built-in StateSnapshot, but couldn't make it working. Then I googled for Scala-land alternatives and it seems like there are few semi-abandoned Redux facades and Diode. Diode looks like what I need, but:
-
State of Scala.js frameworks
c) Diode is my favourite "wiring" library. It is similar to Redux and allows you to handle asynchronous behaviour in your frontend. It has a learning curve but it's not too bad and makes everything so much easier.
- Back-end languages are coming to the front-end
-
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.
What are some alternatives?
sicp - HTML5/EPUB3 version of SICP
tyrian - Elm-inspired Scala UI library.
Chimney - Scala library for boilerplate-free, type-safe data transformations
wasmer-python - 🐍🕸 WebAssembly runtime for Python
whirlisp - A whirlwind Lisp adventure
slinky - Write Scala.js React apps just like you would in ES6
mostly-adequate-guide - Mostly adequate guide to FP (in javascript)
Airstream - State propagation and event streams with mandatory ownership and no glitches
Converter - Typescript to Scala.js converter
scalajs-react - Facebook's React on Scala.JS