| ;;; packages.el --- elm Layer packages File for Spacemacs | |
| ;; | |
| ;; Copyright (c) 2012-2014 Sylvain Benner | |
| ;; Copyright (c) 2014-2015 Sylvain Benner & Contributors | |
| ;; | |
| ;; Author: Sylvain Benner <sylvain.benner@gmail.com> | |
| ;; URL: https://github.com/syl20bnr/spacemacs | |
| ;; | |
| ;; This file is not part of GNU Emacs. | |
| ;; |
Questions about Distributed systems by @tsantero.
| defmodule HttpRequester do | |
| use GenServer.Behaviour | |
| def start_link(_) do | |
| :gen_server.start_link(__MODULE__, nil, []) | |
| end | |
| def fetch(server, url) do | |
| :gen_server.cast(server, {:fetch, url}) | |
| end |
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
| defmodule Mix.TasksServer do | |
| @moduledoc false | |
| use GenServer.Behaviour | |
| def start_link() do | |
| :gen_server.start_link({ :local, __MODULE__ }, __MODULE__, :ok, []) | |
| end | |
| def clear_tasks() do | |
| call :clear_tasks |
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
(by @andrestaltz)
So you're curious in learning this new thing called (Functional) Reactive Programming (FRP).
Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:
Rx.Observable.prototype.flatMapLatest(selector, [thisArg])
Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.
I want to write plugins for Atom's editor in Ruby. Opal makes this possible. Atom is one of several projects in recent times to combine Chromium with Node.js for a desktop app. While it utilizes chromium for it's gui, and boasts "[e]very Atom window is essentially a locally-rendered web page", writing Atom plugins is more like writing a server-side node.js app than a typical single-page client-side app (albeit with really awesome integration with Chrome Devtools). Opal development, on the other hand, has to-date been focused primarily on the browser use-case.
Because of this, I had to make a choice between using the opal-node package from npm, using Opal via Ruby w/ a compile step, or packaging up opal-parser.js, including it with the app, and writing in compilation on the fly. Each choice came with compromises. Using opal-node would have been easiest, just create a top level index.coffee that required opal-node, and then require in your ruby