!!! For M1/M2 apple silicon see this comment:
For MacOS | Mojave | High Sierra
import { useEffect, useLayoutEffect, useReducer, useRef } from 'react' | |
import shallowEqual from './shallowEqual' | |
const useIsomorphicLayoutEffect = | |
typeof window !== 'undefined' ? useLayoutEffect : useEffect | |
export type State = Record<string, any> | |
export type StateListener<T extends State, U = T> = (state: U) => void | |
export type StateSelector<T extends State, U> = (state: T) => U | |
export type PartialState<T extends State> = |
!!! For M1/M2 apple silicon see this comment:
For MacOS | Mojave | High Sierra
For an emulator that mimics a Pixel 5 Device with Google APIs and ARM architecture (for an M1/M2 Macbook):
List All System Images Available for Download: sdkmanager --list | grep system-images
Download Image: sdkmanager --install "system-images;android-30;google_atd;arm64-v8a"
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't