kriskowal

Modules Harmony Simplification Effort

Disclaimer: This text is exclusively focused on the existing capabilities of the language, and does not weight into additional capabilities like wasm, or virtual modules, or compartments. Those can be discussed later on.

MVP to create a module graph

The bare minimum mechanism to create a module graph that matches ESM requires few main pieces:

1. A portable (serializable) structure that represents the source text of the module. ModuleSource must be portable across processes and across realms.
2. A realm based Module that closes over a ModuleSource.

kriskowal

Starting with @snowyu’s proposal I infer some design principles:

1. This language is designed to be easy to render using existing Markdown, YAML, and syntax highlighters.
2. The language should break out to TypeScript that is evaluated in the scope of a global object that represents all of the play state.
3. The Markdown script is a Markdown subset that uses inline backtick expressions to break out to an annotation language that carry semantics.
4. The annotation language embeds the TypeScript grammar for evaluating expressions.

My iteration on this design adds some detail:

1. We use a Markdown variant that forbids arbitrary HTML, adds semantics to list item notation, and uses backticks for annotations.

kriskowal

Authors of GG Individual Contributor License Agreement

Thank you for your interest in contributing to open source software projects (“Projects”) made available by Authors of GG (“Authors”). This Individual Contributor License Agreement (“Agreement”) sets out the terms governing any source code, object code, bug fixes, configuration changes, tools, specifications, documentation, data, materials, feedback, information or other works of authorship that you submit or have submitted, in any form and in any manner, to Authors in respect of any of the Projects (collectively “Contributions”). If you have any questions respecting this Agreement, please

kriskowal

const fs = require('fs')

function readPackage(callback) {
  return fs.readFile('./package.json').nodeify(callback);
}

module.exports.readPackage = readPackage

kriskowal

var DIR = '/tmp/test',
    FILE_PATTERN = /test/,
    fs = require('q-io/fs');

fs.list(DIR)
.then(function (files) {
    var matched = files.filter(function (item) {
        return item.match(FILE_PATTERN);
    });
    if (matched.length !== 1) {

kriskowal

HORSES AND PONIES and WAGONS n CARTS:

By Deb White, Seattle, [NWRinger]

Can horses swim the Brandywine?

The Fellowship of the Ring, 112 the question of whether or not horses can cross the Brandywine River comes up at Buckleberry Ferry. We know that at least 1 hobbit pony can ride the ferry, as Merry takes his across on it when he searches for Frodo who is late to arrive; but there doesn’t seem to be an ability for them, either ponies or horses, to swim it at this point, they must go up to the Bridge or down to Sarn Ford, as Merry’s response to Frodo is: “Can horses cross the river?”

“They can go twenty miles north to Brandywine Bridge - or they might swim,” answered Merry, “Though I never heard of any horse swimming the Brandywine.”

kriskowal

We couldn’t find that file to show.

kriskowal

__all__ = (
    'build',
    'endode',
    'decode',
)

phrase = 'A man a plan a canal Panama'.lower()

def build(phrase):
    """

kriskowal

var IO = require("q-io");

function exists(id) {
    var deferred = Q.defer();
    var request = knoxClient.get(id);
    request.on("error", deferred.reject);
    request.on("response", function (response) {
        if (response.statusCode === 200)
            deferred.resolve(IO.Reader(response));
        } else {

kriskowal

function promiseResponse(request) {
    var deferred = Q.defer();
    request.on("error", deferred.reject);
    request.on("response", deferred.resolve);
    return deferred.promise
    // if you must:
    .fin(function () {
        request.removeListener("error", deferred.reject);
        request.removeListener("response", deferred.resolve);
    });