-- https://news.ycombinator.com/item?id=11396045
SELECT count(*)
FROM (SELECT id, repo_name, path
FROM [bigquery-public-data:github_repos.sample_files]
) AS F| # chat.rb | |
| require 'sinatra/base' | |
| # this also loads celluloid io, let's keep that in mind | |
| require 'celluloid/current' | |
| require 'reel' | |
| # The chat server, an IO Event Loop held by the actor | |
| # Collects connections (Reel Event Streams) | |
| # | |
| # Contrary to EventMachine, there is no event callback for |
| #!/bin/bash | |
| #no PATH, no way to accidently run any programs | |
| PATH='' | |
| #useful variables | |
| term_height=0 | |
| term_width=0 | |
| term_scroll_height=0 | |
| status_line_row=0 |
| # <type>: (If applied, this commit will...) <subject> (Max 50 char) | |
| # |<---- Using a Maximum Of 50 Characters ---->| | |
| # Explain why this change is being made | |
| # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
| # Provide links or keys to any relevant tickets, articles or other resources | |
| # Example: Github issue #23 |
=======================
*, *:before, *:after {=======================
*,BTW, this is implemented as burn-name and burn-name-writer.
BurnName is a proposal for a simple and practical decentralized name registration system. In BurnName, users burn bitcoins to bid for names. The user who bids the most for a name owns that name, after a delay. BurnName uses the existing Bitcoin blockchain and network, and it can be used by various applications.
- GitTorrent or a similar "decentralized GitHub"
- Domain name registration: your username doubles as a domain name
- Human-memorable Bitcoin addresses: map from your username to your Bitcoin address
| #!/usr/bin/env ruby | |
| # This pre-commit hook will prevent any commit to forbidden branches | |
| # (by default, "staging" and "production"). | |
| # Put this file in your local repo, in the .git/hooks folder | |
| # and make sure it is executable. | |
| # The name of the file *must* be "pre-commit" for Git to pick it up. | |
| def current_branch() | |
| branches = `git branch --no-color`.split(/\n/) |
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
gem 'browserify-rails', '1.5.0' # until fix: https://github.com/browserify-rails/browserify-rails/issues/101
gem 'react-rails'Browserify-rails allows to use browserify within assets pipeline. React-rails is here only to allow to use #react_component (and thus, prerendering).
Note that jquery-rails can be removed from Gemfile, the npm version of jquery and jquery-ujs will be used instead.

