ryanflorence

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

isaacs

# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.
#
# Once you're done here, go to
# http://www.gnu.org/software/make/manual/make.html
# to learn SOOOO much more.

bcantrill

root@1eec2cd3-2cba-e416-e1b6-845b715b736c:~# uname -a
Linux 1eec2cd3-2cba-e416-e1b6-845b715b736c 3.13.0 BrandZ virtual linux x86_64 x86_64 x86_64 GNU/Linux
root@1eec2cd3-2cba-e416-e1b6-845b715b736c:~# rustc -Vv
rustc 1.0.0-nightly (44a287e6e 2015-01-08 17:03:40 -0800)
binary: rustc
commit-hash: 44a287e6eb22ec3c2a687fc156813577464017f7
commit-date: 2015-01-08 17:03:40 -0800
host: x86_64-unknown-linux-gnu
release: 1.0.0-nightly
root@1eec2cd3-2cba-e416-e1b6-845b715b736c:~# cat hello.rs

kmcallister

With Rust 1.0-alpha, the macro reform RFC is mostly implemented. This document gives a quick guide to migrating your code.

Macro syntax

#[macro_use] extern crate

A macro import such as

isaacs

// A "memory leak" means that, even after garbage collection, memory is still
// not released to the system. Note that this is different from "using a lot
// of memory".
//
// It's of course possible to do things that prevent garbage collection, which
// is a memory leak in JavaScript.  (As opposed to a memory leak in the
// JavaScript implementation.)
//
// Even if you do not leak memory, and the implementation does not leak memory,
// if you never hit V8's GC heuristic case, then you might keep *using* a lot

StephanHoyer

Attention

This post described how to create an application with mithril 0.2.x. Now that ver 1.0 is out, some things are a little differnent.

The example is updated with the current version of mithril, though.

Isomorphic applications with mithril

wycats

A small sampling of external projects initially built for Ember use but designed to be used standalone:

• Handlebars - templating engine
• simple-html-tokenizer - an HTML5 tokenizer
• HTMLBars - alternate HTML-aware Handlebars backend
• morph - text-node placeholders for data binding systems
• RSVP - fast, lightweight promise library
• route-recognizer - just the recognition part of a router
• router.js - hierarchical states and transition-based router
• dag-map - graph library

rtorr

rustc points.rs --crate-type=dylib

npm install

node test.js

terion-name

This class forces video to load on 100% and informs about it's load progress.

Important notes:

• Google Chrome requires your web server to be capable of serving the document using byte ranges (see http://stackoverflow.com/questions/4572720/html5-video-tag-in-chrome-why-is-currenttime-ignored-when-video-downloaded-fro)
• Load progress is calculated in percents rounded to int because IE and FF never give buffered / videoDuration == 100. Even rounding to precision of 2 fails in IE

dingjie

Ember.Handlebars.registerHelper('eachIndexed', function eachHelper(path, options) {
    var keywordName = 'item',
        fn;

    // Process arguments (either #earchIndexed bar, or #earchIndexed foo in bar)
    if (arguments.length === 4) {
        Ember.assert('If you pass more than one argument to the eachIndexed helper, it must be in the form #eachIndexed foo in bar', arguments[1] === 'in');
        Ember.assert(arguments[0] + ' is a reserved word in #eachIndexed', $.inArray(arguments[0], ['index', 'index+1', 'even', 'odd']));
        keywordName = arguments[0];