---------- Forwarded message ----------
From: Mark S. Miller <[email protected]>
Date: Tue, Nov 16, 2010 at 3:44 PM
Subject: "Future of Javascript" doc from our internal "JavaScript Summit"
last week
To: [email protected]
---------- Forwarded message ----------
From: Mark S. Miller <[email protected]>
Date: Tue, Nov 16, 2010 at 3:44 PM
Subject: "Future of Javascript" doc from our internal "JavaScript Summit"
last week
To: [email protected]
| function stupid_tricks | |
| % I made some functional tools for MATLAB. | |
| assert(reduce_(@(x, y) x + y, [1, 2, 3, 4]) == 10) | |
| % They got a little out of hand. | |
| join = @(sep, args) ... | |
| if_(ischar(sep), @() ... % Input check | |
| reduce_(@(x, y) [x sep y], ... % Reduce to string | |
| map_(@num2str, args))); % Convert args to string. |
| @mixin flexbox( $display: flex, $direction: row, $wrap: wrap, $justify: start, $items: start, $content: start ) { | |
| // <display> - flex | inline-flex | |
| // <direction> - row | row-reverse | column | column-reverse | |
| // <wrap> - wrap | nowrap | wrap-reverse | |
| // <justify> - start | end | center | space-between | space-around | |
| // <items> - start | end | center | baseline | stretch | |
| // <content> - start | end | center | space-between | space-around | stretch | |
| // @include flexbox( flex, row, wrap, start, start, start ); | |
| // @include flexbox( inline-flex, column, nowrap, center, start, stretch ); |
Unionize lets you connect together docker containers in arbitrarily complex scenarios.
Note: I recommend to use https://github.com/jpetazzo/pipework instead.
Now if you want Unionize, it's still here. Just check those examples.
| (ns default-maps | |
| "Maps with default values, similar to how you can specify default values and blocks to Ruby's Hash. | |
| Examples: | |
| user> (def b (assoc-default {:foo 34 :bar 34} (fn [_ k] (str k)))) | |
| #'user/b | |
| user> (get b :foo-bar) | |
| \":foo-bar\" | |
| user> (def m (assoc-default {:foo 34 :bar 34} 343)) |
W3C Introduction to Web Components - explainer/overview of the technologies
| +user=> (def c (ProcessBuilder. (into-array ["cat"]))) | |
| #'user/c | |
| +user=> (def p (.start c)) | |
| #'user/p | |
| +user=> (def o (.getOutputStream p)) | |
| #'user/o | |
| +user=> (.write o (.getBytes "hello\n\n")) | |
| nil | |
| +user=> (.flush o) | |
| nil |
| use std::marker::Sized; | |
| macro_rules! component { | |
| ($i:expr, $name:ident { $( $dn:ident: $def:ty ),* } ) => ( | |
| #[derive(Debug)] | |
| struct $name { | |
| $($dn: $def),* | |
| } |
Helm 3 is storing description of it's releases in secrets. You can simply find them via
$ kubectl get secrets
NAME TYPE DATA AGE
sh.helm.release.v1.wordpress.v1 helm.sh/release.v1 1 1h
If you want to get more info about the secret, you can try to describe the secret
$ kubectl describe secret sh.helm.release.v1.wordpress.v1