start new:
tmux
start new with session name:
tmux new -s myname
# Matches patterns such as: | |
# https://www.facebook.com/my_page_id => my_page_id | |
# http://www.facebook.com/my_page_id => my_page_id | |
# http://www.facebook.com/#!/my_page_id => my_page_id | |
# http://www.facebook.com/pages/Paris-France/Vanity-Url/123456?v=app_555 => 123456 | |
# http://www.facebook.com/pages/Vanity-Url/45678 => 45678 | |
# http://www.facebook.com/#!/page_with_1_number => page_with_1_number | |
# http://www.facebook.com/bounce_page#!/pages/Vanity-Url/45678 => 45678 | |
# http://www.facebook.com/bounce_page#!/my_page_id?v=app_166292090072334 => my_page_id | |
# http://www.facebook.com/my.page.is.great => my.page.is.great |
# Struct utilities | |
# Author:: Matt Sullivan (mailto:matt.j.sullivan@gmail.com) | |
# Attempt to require Ruby Gems; 1.8.X gem support only | |
begin | |
require 'rubygems' | |
rescue LoadError | |
# Ruby Gems not installed | |
end |
source "https://rubygems.org" | |
gem 'sprockets' | |
gem 'sprockets-sass' | |
gem 'sass' | |
gem 'compass' | |
gem 'bootstrap-sass' | |
gem 'handlebars_assets' | |
gem 'coffee-script' |
Too much for teh twitterz :)
JVM + invokedynamic is in a completely different class than CLR + DLR, for the same reasons that JVM is in a different class than CLR to begin with.
CLR can only do its optimization up-front, before executing code. This is a large part of the reason why C# is designed the way it is: methods are non-virtual by default so they can be statically inlined, types can be specified as value-based so their allocation can be elided, and so on. But even with those language features CLR simply cannot optimize code to the level of a good, warmed-up JVM.
The JVM, on the other hand, optimizes and reoptimizes code while it runs. Regardless of whether methods are virtual/interface-dispatched, whether objects are transient, whether exception-handling is used heavily...the JVM sees through the surface and optimizes code appropriate for how it actually runs. This gives it optimization opportunities that CLR will never have without adding a comparable profiling JIT.
So how does this affect dynamic
Here are a list of headless browsers that I know about:
package controllers | |
import play.api._ | |
import play.api.mvc._ | |
object Application extends Controller { | |
def zip = Action { | |
import play.api.libs.iteratee._ | |
import java.util.zip._ |
(ns demo.client | |
(:require [enfocus.core :as ef] | |
[enfocus.events :as events] | |
[vertx.client.eventbus :as eb]) | |
(:require-macros [enfocus.macros :as em])) | |
(defn open-eventbus | |
"Opens a connection to the remote EventBus endpoint." | |
[& on-open] | |
(let [eb (eb/eventbus "http://localhost:8081/eventbus")] |
"A generic function that produces a memoized version | |
of the given [[function|fun]]. Works for any function | |
arity." | |
Callable<Return,Args> memoize<Return,Args>(Callable<Return,Args> fun) | |
given Args satisfies Anything[] { | |
value cache = HashMap<Args,Return&Object|Finished>(); | |
function callFun(Args args) { | |
//we'll use finished as a convenient | |
//unit value to represent the case | |
//that the function returned null |