One of the interesting aspects in Typescript is that it is easy to extract out individual types from composite types.
This post is intended to primarily benefit people coming from other, so called “modern” editors to Emacs. Emacs veterans are likely to find most of the tips here very elementary.
I have observed that many programmers habituated to newer editors have many implicit assumptions about editing workflows which simply don’t hold true within Emacs environment and this prevents them from being productive to the fullest extent.
This post primarily focusses on how getting familiar with the concept of
regions in Emacs can result in productive workflows. These concepts, coupled with a few extensions can enable much more pleasurable code-editing workflows not easily achievable in more prevalent “modern” editors.
Usage of C# inspired
Most of the times we
await on promises (typically returned from async functions), however, it is relatively less well known that
await works on arbitrary thenables. By thenables we mean any object with a
then function member.
This post covers this usage, and explores some scenarios where it can be interesting.
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.
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.
While this post primarily compares Reason and TypeScript, much of what is outlined about TypeScript equally applies to flow as well.
Typescript team has explicitly stated that they don’t intend to extend typescript’s static type checking to the runtime.
Typescript Design Goals lists the following in the section on Non-goals:
Add or rely on run-time type information in programs, or emit different code based on the results of the type system. Instead, encourage programming patterns that do not require run-time metadata.
However, this also implies that for cases when static typing cannot help us we need to separately write validators using a validation library (eg. Joi) which has to be kept in sync with the typescript types.
This post outlines a container based development workflow using Vagrant and Docker.
Many common docker tutorials (eg. the official node tutorial) suggest a workflow where projects source is copied onto the image, which is then built and run through docker. This approach is not really practical for clojure development as normal clojure programming leans heavily on rapid prototyping and REPL driven development.
The setup below utilizes Vagrant and docker volumes to setup a development environment which ensures reproducibility and container isolation while retaining the short feedback cycle which clojure developers take pride in.
The lack of support for asynchronous operations in redux core has spawned a whole ecosystems for managing side-effects  in Redux.
This post argues that the redux-loop library (1.5 k ★ as of this writing) is a much better solution for this job than other more popular alternatives like redux-sagas (11.8 k ★) and redux-thunk (7.8 k ★).
As has always been prevalent in frontend ecosystem, popularity does not necessarily translate to better suitability.
However, this is jarring when the rest of your emacs environment is configured to use helm as the completion engine.
Fortunately, this is easy to fix by overriding the
tide-popup-select-item implementation to use a custom helm source derived from the completion list.