Fatih Altinok frontsideair

Do we really need `node_modules` or `npm`?

I remember thinking that the way we're doing JavaScript is complex but we don't have any choice. What we've been doing for the last few years is that we are downloading a lot of JavaScript modules from npm to ournode_modules folder and we transform and bundle it for browsers using webpack and babel. This was necessary because browsers didn't have support for new features, most importantly module support and sending a lot of separate files to the browser was inefficient, so we transformed and bundlead ahead-of-time.

Now the times are changing. Many popular browsers support the crucial features including module support and HTTP/2 makes it more efficient to send a bunch of files. But we're stuck with the old ways now, and we're paying the price for what made sense at the time. As it turns out putting al your JavaScript in one bundle is not that efficient either, since you're sending non essential code which makes it load and parse slower thus affecting the us

Keybase proof

I hereby claim:

I am frontsideair on github.
I am frontsideair (https://keybase.io/frontsideair) on keybase.
I have a public key ASAPGnaC_3WM2q986wv9RYI23GHLA7eJVZ11fbdqFt0ylwo

To claim this, I am signing this object:

Enter the username of a Github user to get their full name. Request on keystroke with XHR cancellation instead of debounce, which results in less latency and better user experience. Very simple implementation with RxJS. The magic is the .switch operator.

See live on esnextbin, don't forget to open Network tab in DevTools to see cancellation.

Test case for gcanti/flow-static-land#56

Test case for copying test with native APIs. (Works on latest Chrome, Firefox, Safari.)

made with esnextbin

	// @flow

	import React, { Component } from "react"
	import { isIP, isURL, isEmail, isPort } from "validator"
	import { allValid, getErrors } from "./validation"
	import { makeAPICall } from "./api"

	// a flat data structure for viewing in the UI
	type Inputs = {
	hasAuth: boolean,

	const obj = { foo: 'bar', baz: 'quux' } // let's define our object
	const { foo, baz } = bar // the keys are now in the envorinment!

	const hello = 'world' // hello is defined in our environment
	const newObj = { hello } // and now it's captured in our object!

	const pop = (arr, tmp) => (tmp = arr.slice(0), tmp.pop(), tmp)
	const push = (arr, item, tmp) => (tmp = arr.slice(0), tmp.push(item), tmp)

	// Can you see why and how this works? Does it really? Can you guess if it's pure or impure?
	// Does it modify any of its arguments, or pollute global scope?

	<!doctype html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>ESNextbin Sketch</title>
	<!-- test here: https://esnextb.in/?gist=7cba0a35afc77d49ebb2bf5b99e944f1 -->
	</head>
	<body>
	<div id="app"></div>
	</body>

	const Cycle = require('@cycle/core');
	const {makeDOMDriver, div, button} = require('@cycle/dom');
	const {Observable} = require('rx');

	function intent({ DOM }) {
	const incr$ = DOM
	.select('.incr')
	.events('click')
	.map(() => prev => prev + 1);

Fatih Altinok frontsideair

Do we really need node_modules or npm?

Keybase proof

Do we really need `node_modules` or `npm`?