#enable nginx server-wide Gzipping
First, open /etc/nginx/nginx.conf
Then add the following lines inside the http{}
gzip on;
gzip_http_version 1.1;
| // src/plugins/dctypes.js | |
| import { types as tt } from "../tokenizer/types"; | |
| import { types as ct } from "../tokenizer/context"; | |
| import Parser from "../parser"; | |
| import "./flow"; | |
| const pp = Parser.prototype; | |
| export default function (instance) { |
This is a proposal for lightning talk at Reactive Conf. Please 🌟 this gist to push the proposal!
Hi, I am Andy, creator of leakage - the node-powered memory leak testing library.
Instead of manual debugging it provides a structured approach to fix or even prevent memory leaks.
| // The Babylonian Method | |
| // http://en.wikipedia.org/wiki/Methods_of_computing_square_roots#Babylonian_method | |
| // @param n - the number to compute the square root of | |
| // @param g - the best guess so far (can omit from initial call) | |
| function squirt(n, g) { | |
| if (!g) { | |
| // Take an initial guess at the square root | |
| g = n / 2.0; | |
| } | |
| var d = n / g; // Divide our guess into the number |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>WebGL NFT</title> | |
| <meta | |
| name="viewport" | |
| content="width=device-width, user-scalable=no, minimum-scale=1.0, maximum-scale=1.0" | |
| /> | |
| <meta property="og:image" content="thumbnail.png" /> |
tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?
| /*! CSS.supports() Polyfill | |
| * https://gist.github.com/codler/03a0995195aa2859465f | |
| * Copyright (c) 2014 Han Lin Yap http://yap.nu; MIT license */ | |
| if (!('CSS' in window)) { | |
| window.CSS = {}; | |
| } | |
| if (!('supports' in window.CSS)) { | |
| window.CSS._cacheSupports = {}; | |
| window.CSS.supports = function(propertyName, value) { |
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.
States. The final frontier. These are the voyages of an enterprising developer. Her eternal mission: to explore strange new techniques, to seek out better ways to engineer for mental models and new design patterns. To boldly go where a few awesome devs have gone before.
So you’ve found our poignant guide to SCXML and surely you’re wondering “Why should I want to go out of my way to use formal state machines?” or something like that. Hopefully this introduction addresses that kind of question.
