justjavac

%GetOptimizationStatus return a set of bitwise flags instead of a single value, to access the value, you need to take the binary representation of the returned value. Now, for example, if 65 is returned, the binary representation is the following:

(65).toString(2).padStart(12, '0');
// 000001000001

Each binary digit acts as a boolean with the following meaning:

paulirish

// http://paulirish.com/2011/requestanimationframe-for-smart-animating/
// http://my.opera.com/emoller/blog/2011/12/20/requestanimationframe-for-smart-er-animating

// requestAnimationFrame polyfill by Erik Möller. fixes from Paul Irish and Tino Zijdel

// MIT license

(function() {
    var lastTime = 0;
    var vendors = ['ms', 'moz', 'webkit', 'o'];

justjavac

// 需要通过 node --allow-natives-syntax 参数运行
const { GCSignal, consumeSignals, trackGarbageCollection } = require("gc-signals");

function fn() {
    // 创建两个局部变量
    const a1 = new GCSignal(1);
    const a2 = new GCSignal(2);
    global.tmp = a2;  // 将 a2 变量赋值给全局变量
    const o = {};
    trackGarbageCollection(o, 3); // 跟踪局部变量 o 的 GC 状态，标识为 3

gr2m

// sign up
account.signUp('joe@example.com', 'secret');

// sign in
account.signIn('joe@example.com', 'secret');

// sign in via oauth
account.signInWith('twitter');

// sign out

acdlite

Demo: Coordinating async React with non-React views

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?

justjavac

var cv = document.getElementById('cv');
var c = cv.getContext('2d');
var txtDiv = document.getElementById('txt');
var fileBtn = document.getElementById("up-button");
var img = new Image();
img.src = 'a.jpg';
img.onload = init; // 图片加载完开始转换
fileBtn.onchange = getImg;

// 根据灰度生成相应字符

gaearon

// ------------
// counterStore.js
// ------------

import {
  INCREMENT_COUNTER,
  DECREMENT_COUNTER
} from '../constants/ActionTypes';

const initialState = { counter: 0 };

wintercn

我是JS中"就近声明"以及"允许多次var声明"的拥护者。

我持这样观点源自我对易读性的追求。

看一段代码：

function aFunc() {
    for(var i = 0; i < 100; i++) {
 doSth(i);

gr2m

// add a new object
var type = 'note';
var attributes = {color: 'red'};
store.add(type, attributes)
  .done(function (newObject) {});
  .fail(function (error) {});

// update an existing object
var type = 'note';
var id = 'abc4567';

justjavac

// JavaScript 字符串编码使用 UTF-16
"💩".length === 2;
"💩" === "\u{1F4A9}";    // es6
"💩" === "\uD83D\uDCA9"; // es5

// 同一个编码可能使用不同的码位
"ò" === "ò";       // ❎
"ò" === "\xF2";    // ✅
"ò" === "o\u0300"; // ✅
"o\u0300".normalize("NFC") === "\xF2"; // ✅ es6 提供了 normalize 函数