jlongster

(require 'cljs.repl)
(require 'cljs.closure)
(require 'cljs.repl.browser)
(require 'cljs.repl.node)

(defonce target (first *command-line-args*))
(defonce action (second *command-line-args*))

(defonce build (if (= action "watch")
                   cljs.closure/watch

sgrove

;; NB: Missing the html controls to edit the parameters, 
;; will add them in later for a fair comparison
(ns gampg.learn-gamma.lesson-07
    (:require [clojure.string :as s]
            [gamma.api :as g]
            [gamma.program :as p]
            [gamma.tools :as gt]
            [gamma-driver.drivers.basic :as driver]
            [gamma-driver.protocols :as dp]
            [goog.webgl :as ggl]

sgrove

;; Gamma (shader-generation): https://github.com/kovasb/gamma
;; Gamma Driver (WebGL resource management, aka "Om for WebGL"): https://github.com/kovasb/gamma-driver
;; Gamma examples: https://github.com/kovasb/gamma-examples

(ns gampg.learn-gamma.lesson-01
    (:require [clojure.string :as s]
            [gamma.api :as g]
            [gamma.program :as p]
            [gamma.tools :as gt]
            [gamma-driver.drivers.basic :as driver]

jlongster

// Some of this is just preference, as you can do it in stuff like Rx
// as well but I find that this style scales better for readable code.

// Channels only provide a few operations like `take` (`<!` in CLJS)
// and don't care how your event loop is run. You manually create
// loops, as in `go-loop` in ClojureScript:

(go-loop [last-x 0]
  (let [x (<! x-chan)]
    (if (not (= x last-x))

SamPenrose

PierreKircher

[Unit]
Description=cAdvisor Service
After=docker.service
Requires=docker.service
[Service]
Restart=always
ExecStartPre=-/usr/bin/docker kill cadvisor
ExecStartPre=-/usr/bin/docker rm -f cadvisor
ExecStartPre=/usr/bin/docker pull google/cadvisor
ExecStart=/usr/bin/docker run --name cadvisor --volume=/var/run:/var/run:rw --volume=/sys:/sys:ro --volume=/var/lib/docker/:/var/lib/docker:ro --publish=4194:4194 google/cadvisor --logtostderr --port=4194

donpdonp

Web Message Bus notes (Oct 2013)

Description

a message bus for http requests and responses. hanging off the bus are webapps and http listeners. routing table is modified at runtime. the start script for apps and listeners are part of the configuration (services endure, like node's forever)

Components

• Bus = nanomsg
• Webapp: Rails, Node, etc (anything with a nanomsg lib)
• HTTP Listener: nginx module
• Distributed routing config with coreos/etcd

whilo

(import [pysistence [make_list make_dict]])


(defn atom [init-val])

(defn swap! [atom fn])

(defn massoc [as k v]
  (kwapply (as.using) {k v}))

mfikes

If you look at the 2014 State of ClojureScript survey, these are the top items for What has been most frustrating for you in your use of CLJS?, and my take on work done in these areas is below. It is nothing short of amazing, IMHO.

Therefore I urge you to do the current survey.

1. Difficulty using ClojureScript REPL: The Node.js REPL was added, as well as a Nashorn REPL, as well as a lot of new "ease-of-use" stuff baked into all base REPLs (doc, pst, etc.). Additionally, a few new ClojureScript REPLs (Ambly, Replete, Planck) rely heavily on new stuff in ClojureScript.
2. Difficulty debugging generated JavaScript: Source map capability was essentially extended to all REPLs with stack traces automatically being mapped. The

rm-hull

WebGL & Clojurescript

Ensure that you have a WebGL-capable browser to view this gist

• Sun
• Mercury
• Venus
• The Earth
• The Moon
• Mars