React refs are generally considered an anti-pattern as their usage typically encourages patterns which go against declarative compositon and top down flow of data.
This post explores a somewhat uncommon use case where refs can be used to expose layout slots in parent components to nested components.
Continue reading Exposing slots in layout containers through shared refs in React
I like F# and believe the author has done an amazing job evolving a functional language on the dot net platform but there are simply too many design choices in F# geared around C# compatibility and limitations of CLR being an object oriented language that when you switch to a different compilation target, these language aspects begin to look like bizarre warts.
Continue reading Fable+F# vs ReasonML | Hacker News
While this post primarily compares Reason and TypeScript, much of what is outlined about TypeScript equally applies to flow as well.
Continue reading ReasonML vs TypeScript – First impressions
A hack which makes the HAML parser BEM aware and helps reduce some of the repetitive boilerplate associated with specifying BEM compliant class names in templates.
Predictability and Side-effects
Redux advertises itself as a predictable state container.
This predictability comes at a cost: Your actions that are supposed to manipulate the state of your application are processed synchronously through pure functions called reducers. You should not have side-effects in your reducers.
Eliminate full page refreshes and reduce page transition latency, in your your Rails sites, using SPF.js – a library for dynamic page updates from Youtube.
While it is disheartening to see technologically superior software be ignored by industry in favor of lacklustre ones, is the same true for React as well ?
In past developers have often relied on backend-specific toolchains for web application frontends. Some examples would be Rails asset pipeline or the legacy ant based toolchain for YUI. However recently node.js based tooling support for frontend technologies has significantly evolved and it is quite viable to use a node.js based toolchain for managing your frontend projects, even if the backend is not node.js, thus keeping the workflow decoupled from the backend.
One of the biggest promises of Node.js is code re-use across client and server – this post focusses on reusing server side templates on client as well for dynamic rendering.