Water Conservation at The Oasis: https://www.oasisatdeathvalley.com/who-we-are/sustainability...
Hydrogeology of Lower Amargosa Valley (see Fig. 1 in report): https://pubs.er.usgs.gov/publication/sir20185151
3,796 karma · joined April 21, 2011
Water Conservation at The Oasis: https://www.oasisatdeathvalley.com/who-we-are/sustainability...
Hydrogeology of Lower Amargosa Valley (see Fig. 1 in report): https://pubs.er.usgs.gov/publication/sir20185151
> “It is possible that this was partially due to reduced emissions, but meteorology likely played a much larger role.”
Here in OC over the past couple weeks the haze has returned, while traffic is only slightly up.
for a in $(git var -l | sed -nE 's/^alias\.([^=]*)=.*/\1/p') ; do
if ! command -v g$a >/dev/null 2>&1 ; then
alias g$a="git $a"
fi
done
Which creates a shell alias prefixed with `g` for each of my configured git aliases if there is no conflict. So I get not only the `gst` command you mentioned and ones like `gco` (because I have Subversion-equivalent aliases for common commands), but more complex ones like `gstpup` (stash, pull upstream, stash pop). Combined with `alias g=git`, I seldom type "git" and the setup is pretty convenient. I've thought of making the above alias unconditionally, or report conflicts, as it can be jarring when an alias is missing. I've also considered expanding it to all git commands because sometimes my custom ones live as `git-$command` scripts and not aliases. nnoremap <buffer> <C-P> :write !cat - <(echo ")OFF") \| apl --script<CR>
It took some time to figure that out, but combined with https://github.com/ngn/vim-apl, it is not too bad of an editing experience.The best source I could find is http://www.ijhssnet.com/journals/Vol_3_No_21_[Special_Issue_... which describes the condemnation of khat:
> Khat was cursed by God forever to be chewed by humans because of causing a divine displeasure when God came to Earth and all the plants bowed before him showing ultimate respect with the exception of Khat.
That's what's so exciting about new work on MLton like this: A JIT-ing MLton, for instance, could be an amazing thing. It seems like the community has been coalescing around MLton against all odds, and any improvements to it are a big deal.
SML is nicer syntactically than OCaml, but OCaml brings so much to the table that it's hard to ignore (a simpler compilation model, niceties like named arguments, single development target, good community). Also Paulson's ML For the Working Programmer explains SML's warts well, in a historical context. It goes into great detail of some of the limitations of SML's module type safety and some of the nasty things you need to do to make functors generic and reusable, which really turned me off of the language and explained why Caml and OCaml exist. I still love SML but must concede that it's mostly a teaching language. The Little MLer is wonderful.
Hadoop is one of the better known computation systems, though it does other things too (e.g. persistence with HDFS). Apache Storm is another popular computation system, particularly in the Clojure world. Onyx was created a few years ago, is implemented in Clojure, and competes with Storm (it's the first such system mentioned in the "What is it?" section of https://github.com/onyx-platform/onyx).
Onyx is distributed (meaning there are multiple nodes cooperating, typically over a network), and Jepsen is a rigorous tool for testing fault-tolerance in such systems. Being masterless (no node has central authority) is valuable for fault-tolerance. It means that in the event of a network partition, either side of the partition can continue processing as normal and recover when the partition is resolved. Jepsen simulates these and other fault conditions.
Presumably a codebase in an array-oriented language would have miniscule PRs, which is irrelevant (discussion of PL merits aside).
He loaded up AltaVista and explained what a search engine was, in terms that I could understand, by relating it to a library catalog. I'd only used those DOS catalogs to that point, and they were picky. I carefully typed on the Power Mac's keyboard, "Davis, Jim".
As the results crawled down the screen, I knew immediately that this was a world apart from reading old Garfield books at the library, that it was something totally new (and daunting). I really didn't know what to make of it.
A few days later I snuck into the office and printed out the career statistics of "Moon, Warren".
- George Orwell's 1984, a "Bloom's Guides" edition (Cliff's Notes-looking thing)
- Benjamin Franklin, a graphic-novel format biography of the statesman and scientist
- Gran Pionero de Beísbol, a graphic-novel format biography of Jackie Robison
- Wilma Rudolph, a graphic-novel format biography of the Olympian runner
- Martin and John, "with a frankness about sexuality rarely seen in contemporary fiction ... a haunting, daring, and heartrending debut novel that speaks of gay life"
Those results don't seem to reflect the stated methodology in the "About" section... the only commonality is that three of the five are biographies. I expected more things to do with Russian literature, or literary biographies contemporary with Troyat's.
I'm interested in the project's implementation, it's too bad it isn't open source.
The Elixir pipe syntax is reminiscent of Clojure's ->/->>:
(->> (range 1 10)
(map #(* % %))
(filter (partial > 40)))
It's nice that in languages like Haskell or ML this is trivial: infix |>
fun (a |> b) = a b
You could modify this to let NONE fall through, etc.