React Fiber is an ongoing reimplementation of React's core algorithm. It is the culmination of over two years of research by the React team.
module Flow exposing (Flow(..), map, withDefault, mapDefault, view, update) | |
import Html | |
type Flow state | |
= NotRunning | |
| Running state | |
module Editable exposing (..) | |
type Editable ofType | |
= NotEditing { value : ofType } | |
| Editing { originalValue : ofType, buffer : ofType } | |
value : Editable ofType -> ofType | |
value editable = |
Jotting down a list of posts I'd like to write. Probably won't write them in this exact order.
- Practical Redux series
- Connected lists, basic form editing
- Form change handling, feature reducers
- "editing/draft slice" approach
- Modal management and "picker" modals
- Handling more complex nested/relational data
- Entity creation
- Treeview
Cheng Lou, a former member of the React team, gave an incredible talk at React Europe 2016 entitled "On the Spectrum of Abstraction". That talk is available for viewing here: https://www.youtube.com/watch?v=mVVNJKv9esE
It's only a half-hour, but it is mind-blowing. It's worth re-watching two or three times, to let the ideas sink in.
I just rewatched the talk for some research, and wrote down a summary that's semi-transcript-ish. I didn't see any other transcripts for this talk, other than the auto-generated closed captions, so I wanted to share for reference.
module SignupForm exposing (..) | |
-- This is where our Elm logic lives.`module SignupForm` declares that this is | |
-- the SignupForm module, which is how other modules will reference this one | |
-- if they want to import it and reuse its code. | |
-- Elm’s "import" keyword works similarly to "require" in node.js. | |
import Html exposing (..) | |
This proposal is an alternative to “Integer: Arbitrary precision integers in JavaScript” by Daniel Ehrenberg, but it also builds on his work.
Everything mentioned here is work in progress. It is not sure that these ideas will work out:
- They may break the web.
- They may turn out to be too complicated/user-unfriendly.
import { AWS } from 'infastructure-as-code' | |
import fs from 'fs' | |
AWS.region = 'us-east-1' | |
const ENV = process.env.NODE_ENV || 'development' | |
const lambdaRole = new AWS.IAM.Role({ | |
RoleName: `lambda-execution-${env}` | |
}) |
Here is a checklist of all the things I need my CSS solution to handle.
I can explain any of the points. Leave a comment on the gist or tweet @DavidWells
Challenge: Take your favorite CSS solution and see how the checklist holds up.
- Has ability Localize classes
- Has ability to use global classes
- Has ability to write raw CSS
- Syntax highlighting and auto completion
import React from 'react' | |
import { render } from 'react-dom' | |
// with fiber, we'll be able to write components that update text deep | |
// inside another string without wrapper dom, or rerendering the whole component | |
// before | |
class Lorem extends React.Component { | |
state = { | |
str: '' |