lucasmreis
Adopting Optimizely at Compass
Learning ReasonML, Part 3 – Implementing Side Effects
Learning ReasonML, Part 2 – Integrating ReasonML into a React Application
Learning ReasonML, Part 1 – Lucas Reis' Blog
Making Sense of Insurance Cards Using Deep Learning
Simple React Patterns – Dealing with Side-Effects in React – Lucas Reis' Blog
The Single Most Important Driver of Software Quality
Type Driven Domain Modelling, Part 3: One More Spec Change with F#
So, if we only want to call a couple of animations and submit a form, I agree that a small script with three jQuery-style functions can do the job.
But that's rarely the case nowadays, in my experience. Almost every frontend project I came across professionally became a full application at some point.
There's the need of dealing with concurrent user interactions, online data requests to the server, non-traditional form behaviors, different routes...
I can see a lot of value for that in non-tech companies that correctness is crucial, like finance, insurance, health...
And, as some commenter on Disqus said, probably the right thing to do would be returning an Qty option from the function, and treating it properly.
I have no experience with Scheme, but already worked with Clojure - it was actually my "gateway" to functional programming languages, hehe!
Type Driven Domain Modelling, Part 2: Evolving Models with F#
Type Driven Domain Modelling – Evolving Models with F# – Lucas Reis' Blog
From Elm to Fable – Trying F# in the Front End – Lucas Reis' Blog
Learning Elm Part 4 – Property Based Testing and Better Modelling
Does Elm Harmonize with F#?
Centralized State Design Patterns
I agree that Clojure and Clojurescript are superior languages than Javascript. In fact, I had my first contact with CSP through those languages.
I like the React wrappers more than React itself, but I prefer Quiescent than Reagent, because I can use the framework described in the post.