Happy-Ferret

/*
********************************************************************************
Golang - Asterisk and Ampersand Cheatsheet
********************************************************************************

Also available at: https://play.golang.org/p/lNpnS9j1ma

Allowed:
--------
p := Person{"Steve", 28} 	stores the value

Happy-Ferret

#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#ifdef _MSC_VER
#include <intrin.h> /* for rdtscp and clflush */
#pragma optimize("gt",on)
#else
#include <x86intrin.h> /* for rdtscp and clflush */
#endif

Happy-Ferret

Hyperlinks (a.k.a. HTML-like anchors) in terminal emulators

Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).

It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.

In spring 2017, GNOME Terminal and iTerm2 have changed this.

GNOME Terminal is based on the VTE widget, and almost all of this work went to VTE. As such, we expect other VTE-based terminal emulators to catch up and add support really soon. Other terminal emulators are also welcome and encouraged to join!

Happy-Ferret

/*

Tested against release/1.4 branch of https://github.com/Microsoft/ChakraCore
commit: 6f4c890505a58bbf198035d4b93bf8a726033af3

The below program will work on x86_64 Linux. It demonstrates how to safely call 
in to libChakraCore from Spidermonkey using js-ctypes. Because the ChakraCore 
GC scans the stack for JsValueRefs we must allocate JsValueRefs on the C stack. 
When I say C stack I mean in the memory region between the current stack 
pointer and the initial value of the stack pointer when the program started. 

Happy-Ferret

Components.utils.import("resource://gre/modules/ctypes.jsm")

var liblog = ctypes.open('liblog.so');
var android_log = liblog.declare("__android_log_write",
                             ctypes.default_abi,
                             ctypes.int32_t,
                             ctypes.int32_t,
                             ctypes.char.ptr,
                             ctypes.char.ptr);

Happy-Ferret

yarn add -D jest babel-jest babel-preset-es2015 babel-preset-react react-test-renderer
#Edit package.json adding the jest command : 
"scripts": {
  "build": "nwb build-react-component",
  "clean": "nwb clean-module && npm clean-demo",
  "start": "nwb serve-react-demo",
  "test": "nwb test",
  "test:coverage": "nwb test --coverage",
  "test:watch": "nwb test --server",
  "test:jest": "jest"

Happy-Ferret

// Simple wrapper to make PamlBus requests.
function palmRequest(url, params, callback) {
  var req = new PalmServiceBridge();
  req.onservicecallback = function (result) {
    var data;
    try {
      data = JSON.parse(result);
    } catch (err) {
      callback(err);
      return;

Happy-Ferret

A few conversations have circled around user-side structural profiling. For context, see React PR #7549: Show React events in the timeline when ReactPerf is active

One particular concern is the measurement overhead. This gist has a benchmarking script (measure.js) for evaluating overhead and initial results.

Results: performance.mark()

Runs about 0.65µs per mark() call. Naturally, that's ~= an overhead of 1ms for 1500 mark()s.

Happy-Ferret

const React = require('react');
const fs = require('fs-extra');
const path = require('path');

const readMetadata = require('../../server/readMetadata.js');
const CompLibrary = require('../../core/CompLibrary.js');
const MarkdownBlock = CompLibrary.MarkdownBlock; /* Used to read markdown */

const join = path.join;
const CWD = process.cwd();

Happy-Ferret

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Linq;
using System.Runtime.InteropServices;
using System.Text;
using System.Threading.Tasks;

namespace PhotoStreams
{