Vinh Le vinhlh

Below is the list of modern JS frameworks and almost frameworks – React, Vue, Angular, Ember and others.

All files were downloaded from https://cdnjs.com and named accordingly. Output from ls command is stripped out (irrelevant stuff)

As-is (minified)

$ ls -lhS
566K Jan 4 22:03 angular2.min.js

Cheng Lou - On the Spectrum of Abstraction

Cheng Lou, a former member of the React team, gave an incredible talk at React Europe 2016 entitled "On the Spectrum of Abstraction". That talk is available for viewing here: https://www.youtube.com/watch?v=mVVNJKv9esE

It's only a half-hour, but it is mind-blowing. It's worth re-watching two or three times, to let the ideas sink in.

I just rewatched the talk for some research, and wrote down a summary that's semi-transcript-ish. I didn't see any other transcripts for this talk, other than the auto-generated closed captions, so I wanted to share for reference.

Summary

Problem: How can we preprocess JavaScript (at build-time or on the server-side) so engines like V8 don't have to spend as much time in Parse? This is a topic that involves generating either bytecode or a bytecode-like-abstraction that an engine would need to accept. For folks that don't know, modern web apps typically spend a lot longer in Parsing & Compiling JS than you may think.

Yoav: This can particularly be an issue on mobile. Same files getting parsed all the time for users. Theoretically if we moved the parsing work to the server-side, we would have to worry about it less.
One angle to this problem is we all ship too much JavaScript. That's one perspective. We could also look at preprocessing.
We've been talking about this topic over the last few weeks a bit with V8. There were three main options proposed.
1. Similar to what optimize-js does. Identify IIFEs and mark them as such so the browser and VMs heuristics will catch them and do a better job than today. optimize-js only tackles IIFE bu

	{
	"keys": ["tab"],
	"command": "expand_abbreviation_by_tab",

	// put comma-separated syntax selectors for which
	// you want to expandEmmet abbreviations into "operand" key
	// instead of SCOPE_SELECTOR.
	// Examples: source.js, text.html - source
	"context": [
	{

	/**
	* Using Operator Mono in Atom
	*
	* 1. Open up Atom Preferences.
	* 2. Click the “Open Config Folder” button.
	* 3. In the new window’s tree view on the left you should see a file called “styles.less”. Open that up.
	* 4. Copy and paste the CSS below into that file. As long as you have Operator Mono SSm installed you should be golden!
	* 5. Tweak away.
	*
	* Theme from the screenshot (http://cdn.typography.com/assets/images/blog/operator_ide2.png):

	CREATE EXTERNAL TABLE IF NOT EXISTS alb_logs (
	type string,
	timestamp string,
	elb string,
	client_ip string,
	client_port int,
	target_ip string,
	target_port int,
	request_processing_time double,
	target_processing_time double,

	const puppeteer = require('puppeteer');

	const escapeXpathString = str => {
	const splitedQuotes = str.replace(/'/g, `', "'", '`);
	return `concat('${splitedQuotes}', '')`;
	};

	const clickByText = async (page, text) => {
	const escapedText = escapeXpathString(text);
	const linkHandlers = await page.$x(`//a[contains(text(), ${escapedText})]`);