tabatkins

We've been deadlocked for a while on the pipeline operator proposal, for a few reasons. Partially it's just low implementor interest, as this is fundamentally just syntactic sugar, but also because there are three competing proposals and the proponents of each haven't been convinced by the others yet.

In this essay I hope to briefly outline the problem space, summarize the three proposals, and talk about what's gained/lost by each of them. (Spoiler: they're all nearly identical; we're arguing over very small potatoes.)

fuunnx

Mon setup

• vscode, spotify, git, slack, discord
• fira code
• sync vs code settings
• tabby
• diodon (gestionnaire de presse papier) + raccourci clavier
• gestionnaire de fichiers avec des colonnes de Miller : patheon-files
• activation smooth scroll dans vs code et dans ff

jiraguha

Deno for scripting

Foreword

It is largely inspired by kscript. The idea is to leverage the scripting abilities of javascript using Deno. I feel that scripting can be so much fun with Deno as:

• It can import modules from any location on the web,
• It is secure by default. Imported module can run in sandbox.
• It is Supports TypeScript out of the box.
• It is much more that Node

pyrocto

/* 
It is a melancholy object-oriented language to those who walk through
this great town or travel in the country, when they see the JavaScript
programs crowded with method calls begging for more succinct syntax.
I think it is agreed by all parties, that whoever could find out a
fair, cheap and easy method of making these operators sound and useful
members of the language, would deserve so well of the publick, as
to have his statue set up for a preserver of the nation. I do therefore
humbly offer to publick consideration a pure JS library I've written
for overloading operators, which permits computations like these:

mrehayden1

import { Stream } from 'most';
import * as most from 'most';

type Maybe<T> = null | T
type Position = [number, number]

export function dragPositionStream(
  touchStart$: Stream<TouchEvent>,
  touchMove$: Stream<TouchEvent>,
  touchEnd$: Stream<TouchEvent>

busypeoples

import React from "react";
import { render } from "react-dom";
import Task from "data.task";
import TaskComponent from "./TaskComponent";

const users = [
  { id: 1, name: "User A", points: 45 },
  { id: 2, name: "User B", points: 22 },
  { id: 3, name: "User C", points: 79 },
  { id: 4, name: "User D", points: 54 }

alexlafroscia

ShadyCSS Skate.js Mixin

Out of the box, Skate.js doesn't work that well with ShadyCSS. This is a mixin that helps bridge the gap.

Usage

The usage example below assumes you're using a build tool like Webpack to transform a CSS file into a string when loaded.

import Component from 'skatejs';

ericelliott

const wait = (
  time,
  cancel = Promise.reject()
) => new Promise((resolve, reject) => {
  const timer = setTimeout(resolve, time);
  const noop = () => {};

  cancel.then(() => {
    clearTimeout(timer);
    reject(new Error('Cancelled'));

oxpa

var path = require('path');
var StaticSiteGeneratorPlugin = require('static-site-generator-webpack-plugin')
var ExtractTextPlugin = require('extract-text-webpack-plugin')
var webpack = require('webpack');
var urlloader = require('url-loader');


var React = require("react");
var ReactDom = require("react-dom");
var Redux = require("redux");

staltz

// Generic helper function that takes a main() (the top-level component)
// and wraps it with Stanga logic

function wrapWithStanga(main, initialState) {
  return function (sources) {
    const modProxy$ = new Subject();
    const modelSource = Model(initialState)(modProxy$);
    sources.model = modelSource;
    const sinks = main(sources);
    sinks.model.subscribe(modProxy$);