steveruizok

import * as React from "react"
import { getRef } from "./getRef"

export default function App() {
  const rCanvas = React.useRef<HTMLCanvasElement>(null)

  React.useEffect(() => {
    const canvas = getRef(rCanvas)
    canvas.width = window.innerWidth
    canvas.width = window.innerHeight

steveruizok

import log from "ololog"

class Grid {
	rows = []
	width = 0
	height = 0

	chars = {
		active: ["┌", "─", "┒", "┃", "┛", "━", "┕", "│"],
		inactive: ["┌", "─", "┐", "│", "┘", "─", "└", "│"],

abcdw

Nix vs Guix

These are notes to the stream: https://youtu.be/S9V-pcTrdL8

Some notes

• We are not aware of a lot of GNU software available to us.
• Seems that Guix more hacker-friendly/explorable.

General comparsion

Description

Nix

Guix

Comment

rphuber

XSTATE

Courses

• Introduction to State Machines Using XState
• Construct Sturdy UIs with XState
• Learn State Machines
• State Machines in JavaScript with XState

Videos

• David Khourshid - Infinitely Better UIs with Finite Automata
• David Khourshid: Simplifying Complex UIs with Finite Automata & Statecharts | JSConf Iceland 2018

tannerlinsley

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.

Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.

So why

baumandm

⚠️ I'd recommend using this fork by @igoro00 which has better theme support.

---

Tiny wrapper component for React-Datepicker to stylistically fit with Chakra-UI 1.x.

<DatePicker selectedDate={myDate} onChange={(d) => console.log(d)} />

adapptor-kurt

#!/usr/bin/env python3

# See https://github.com/facebook/flipper/issues/262

import os
import sys
import syslog
import shlex
import time
import subprocess

AllenDang

Use pre-built gccemacs

Fortunatly we could use pre-built gccemacs right now.

Those two repos did the greate job for us.

https://github.com/twlz0ne/nix-gccemacs-darwin

https://github.com/twlz0ne/nix-gccemacs-sierra

Here is the tutorial:

mjlbach

WARNING: THIS GIST IS OUT OF DATE AND NO LONGER RELEVANT

• Native-comp was enabled by default in nixpgks
• Pgtk is not enabled by default, for that you can either override the derivation or use emacsPgtk from the nix-community emacs overlay if you don't want to build it yourself

Nix

Adding the overlay and configuring cachix

developit

export default (function create(options = {}) {
	const client = {
		headers: options.headers || {},
		create
	};
	const events = {};

	client.emit = (type, e) => {
		events[type] &&
			events[type].slice().map(fn => {