msociety

/*
 * André Staltz (@andrestaltz): You will learn RxJS at ng-europe 2016
 * https://www.youtube.com/watch?v=uQ1zhJHclvs
 */

function map(transformFn) {
  const inputObservable = this;
  const outputObservable = createObservable(function subscribe(outputObserver) {
    inputObservable.subscribe({
      next: function(x) {

developit

🐻 valoo

just the bare necessities of state management.

Usage

Hotlink it from https://unpkg.com/valoo.

See Interactive Codepen Demo.

markdalgleish

import React from 'react';
import classnames from 'classnames';
import resetStyles from './reset.module.css';

export default ({ component, className, ...props }) =>
  React.createElement(component, {
    className: classnames(className, resetStyles[component]),
    ...props
  })
);

developit

suspense-loader

Installation (sorry)

npm i THIS_URL

Usage

gimenete

Tras este tweet que publiqué

He sido freelance, emprendedor y trabajo desde hace años para empresas USA de diversos tamaños en remoto como programador fullstack. Ahora en GitHub. Si puedo ayudar a alguien en orientar su carrera, mis DMs están abiertos. Ask me anything.

he recibido muchos mensajes y escribo aquí algunos de los consejos que he dado en resumen. Nota: algunas cosas son concretas de trabajar en España. Si vas a trabajar desde Sudamérica sólo una nota: tienes la ventaja de la zona horaria para trabajar con EEUU.

Inglés

Tener un buen nivel de inglés es fundamental para poder trabajar con clientes extranjeros. El conocimiento del idioma tiene que mantenerse en el tiempo. Es como mantenerse en forma física; si lo dejas, lo pierdes. Personalmente aunque trabajo 100% en inglés desde hace bastantes años, intento crearme un entorno diario con el idioma para no perderlo:

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:

brookback

/*
 * This script fetches all color styles from a Figma team/document.
 *
 * Dependencies:
 *
 *  - node-fetch
 *
 * Due to a limitation in the Figma /styles endpoint, we need to use a
 * document for actually using the colors in a color grid 🙄That's why
 * we're both fetching from /styles and /files below.

mjackson

import { useState, useEffect, useCallback } from 'react'

function usePromise(createPromise) {
  const [error, setError] = useState()
  const [value, setValue] = useState()

  useEffect(() => {
    let current = true

    createPromise().then(

sebmarkbage

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

ryanflorence

Reach UI Philosophy

Reach UI is an accessible foundation for React applications and design systems.

The three equally important goals are to be:

• Accessible
• Composable
• Stylable