threepointone

Note: Since writing this, I've been pointed to some exciting new research/tooling called Project Cambria https://www.inkandswitch.com/cambria.html I'll likely have to rewrite this article taking that into account. Leaving this up for posterity's sake.

---

(This series isn't meant to be a primer/tutorial, though we might do something regarding it in the future. For official documentation and starters, see https://developers.cloudflare.com/workers/learning/using-durable-objects.

Further - these are my personal views; I expect to be wrong about a lot of them. Indeed, I'm not paying much attention to presenting these well at the moment, simply writing down thoughts. As such, expect these writeups to change often, particularly as the platform takes shape. I'm also mostly a front end guy, so don't get mad if I get it very wrong. Give me feedback! Always happy to learn and make changes.)

Durable Objects are a fascinating new storage primitive from cloudflare for their workers platform. There's a lot of 'cool'

josemarimanio

Installing pyenv on macOS for Zsh using Homebrew

Published May-13-2020

• Installation
• Basic Usage
• Virtualenv

garybernhardt

import React, { useEffect } from "react"

import { META_DESCRIPTION } from "../../util"

export const Page: React.FC<{
  title?: string
  metaDescription?: string
}> = props => {
  useEffect(() => {
    document.title = props.title ?? "Execute Program"

baldurh

const { writeFileSync } = require("fs");
const { resolve } = require("path");

const serialize = require("serialize-javascript");
const plural = require("make-plural");

const languages = [
  "de",
  "en",
  "es",

ryanflorence

Everything I Know About UI Routing

Definitions

1. Location - The location of the application. Usually just a URL, but the location can contain multiple pieces of information that can be used by an app
   1. pathname - The "file/directory" portion of the URL, like invoices/123
   2. search - The stuff after ? in a URL like /assignments?showGrades=1.
   3. query - A parsed version of search, usually an object but not a standard browser feature.
   4. hash - The # portion of the URL. This is not available to servers in request.url so its client only. By default it means which part of the page the user should be scrolled to, but developers use it for various things.
   5. state - Object associated with a location. Think of it like a hidden URL query. It's state you want to keep with a specific location, but you don't want it to be visible in the URL.

brieb

import PropTypes from 'prop-types';

type Omit<T, K> = Pick<T, Exclude<keyof T, K>>;

type Defined<T> = T extends undefined ? never : T;

/**
 * Get the type that represents the props with the defaultProps included.
 *
 * Alternatively, we could have done something like this:

ryanflorence

import React, {
  cloneElement,
  useState,
  useEffect,
  useRef,
  HTMLAttributes,
  ReactElement
} from "react";

////////////////////////////////////////////////////////////////////////////////

Rich-Harris

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

hellendag

// @flow

type ResolvedScalar = string | number | boolean | null;
type ResolvedValue =
  | ResolvedScalar
  | Array<ResolvedValue>
  | {[key: string]: ResolvedValue};
type ResolverFunction = (...args: Array<any>) => ResolvedValue;

export type ResolverMap = {

muan

Update: See https://github.com/muan/details-on-details instead.

---

I did a talk at Brooklyn JS called Details on <details> on 2018/07/19. I have way more details prepared than the ones that fit in the slides, so here's the real details on <details>. ❤️

– @muan

Spec