<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by flyboarder on Medium]]></title>
        <description><![CDATA[Stories by flyboarder on Medium]]></description>
        <link>https://medium.com/@degree9matt?source=rss-a2d5aa46d2e3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wKkUQ5z4DuysA2TK.jpg</url>
            <title>Stories by flyboarder on Medium</title>
            <link>https://medium.com/@degree9matt?source=rss-a2d5aa46d2e3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:49:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@degree9matt/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Env Vars in under 100 Lines of Code — (.env)]]></title>
            <link>https://medium.com/degree9/env-vars-in-under-100-lines-of-code-env-ecb2bb05378e?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecb2bb05378e</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[clojurescript]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[clojure]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Thu, 28 May 2020 02:09:55 GMT</pubDate>
            <atom:updated>2020-05-28T02:17:43.269Z</atom:updated>
            <content:encoded><![CDATA[<h3>Env Vars in under 100 Lines of Code — (.env)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VbHu6bpSKkcnmLIG62qS_w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@johnonolan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">John O’Nolan</a> on <a href="https://unsplash.com/s/photos/environment?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Like many projects that run on Node.js our apps use the dotenv package from npm to load environment variables from a local file which is kept out of git.</p><p>This lets our developers keep important secrets out of source control while our apps maintain a consistent way to read from the environment.</p><p>But I like to break things and decided to rewrite the dotenv entirely in ClojureScript, the result has been added to our degree9/enterprise repo.</p><p>Let’s get started!</p><p>Ok, so the Node.js environment is mutable within the running process. Which means we can override the js/process.env object with variables we load from our local file, this is basically the same process that dotenv uses.</p><p>Let’s start with some simple helper functions, these will make working with the .env file and js/process.env a bit easier.</p><p>First up is read-file we want to make sure the environment is populated prior to anything trying to read from it, so we are using the synchronous operation. By providing an encoding the function will return a string instead of a buffer.</p><pre>(defn- read-file [path]<br>  (.readFileSync fs path #js{:encoding &quot;utf8&quot;}))</pre><pre>(defn- env-file [dir]<br>  (.resolve path dir &quot;.env&quot;))</pre><p>The env-file is a simple path resolver which will allow us to provide an optional path to look for the .env file.</p><pre>(defn- split-kv [kvstr]<br>  (cstr/split kvstr #&quot;=&quot; 2))</pre><pre>(defn- split-config [config]<br>  (-&gt;&gt; (cstr/split-lines config)<br>       (map split-kv)<br>       (into {})))</pre><p>Next we have the split-kv helper, this produces a key/value pair from MY_ENV_VAR=foobar .</p><p>While split-config takes the result of our synchronous file read then splits each line and applies our previous split-kv to each.</p><pre>(defn- dot-env [path]<br>  (-&gt; (env-file path)<br>      (read-file)<br>      (split-config)))</pre><p>The result of our existing helpers is the dot-env function, a convenient way to load our .env files as a hash-map config.</p><pre>(defn- node-env [env]<br>  (-&gt;&gt; (js-keys env)<br>       (map (fn [key] [key (obj/get env key)]))<br>       (into {})))</pre><p>It has a counter part, the node-env function. This converts a js/process.env object into a clojure hash-map.</p><p>Our last helper is populate-env! which takes a clojure map and sets each key value pair to the js/process.env object.</p><pre>(defn- populate-env! [env]<br>  (doseq [[k v] env]<br>    (obj/set js/process.env k v)))</pre><p>Now that we have all our helper functions ready to go, we move on to the public API we will be using to interact with the environment variables.</p><pre>(defn init!<br>  &quot;Initialize environment with variables from .env file.&quot;<br>  ([] (init! {:path (.cwd js/process) :env js/process.env}))<br>  ([{:keys [path env]}]<br>   (populate-env!<br>     (merge (dot-env path)<br>            (node-env env)))))</pre><p>Starting up our application we want to initialize the environment, we do this by populating it with the result of merging our .env and js/process.env maps. We want to call this init! function as early as possible in our code so that the environment is ready before anything tries to read from it.</p><p>In our application we simply read from the environment using our other public function get</p><pre>(defn get<br>  &quot;Return the value for `key` in environment or `default`.&quot;<br>  ([key] (get key nil))<br>  ([key default] (get js/process.env key default))<br>  ([env key default] (obj/get env key default)))</pre><p>Put it all together!</p><pre>(require [degree9.env :as env])</pre><pre>(env/init!)</pre><pre>(env/get &quot;MY_ENV_VAR&quot;)</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecb2bb05378e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/env-vars-in-under-100-lines-of-code-env-ecb2bb05378e">Env Vars in under 100 Lines of Code — (.env)</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Idle in 50 Lines of Code — (idle?)]]></title>
            <link>https://medium.com/degree9/idle-in-50-lines-of-code-idle-40ad24fe5bd5?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/40ad24fe5bd5</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[clojurescript]]></category>
            <category><![CDATA[clojure]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Sun, 25 Aug 2019 00:51:02 GMT</pubDate>
            <atom:updated>2019-08-26T19:47:31.711Z</atom:updated>
            <content:encoded><![CDATA[<h3>Idle in 50 Lines of Code — (idle?)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*j1a8CTFmKzI8ZJzP" /><figcaption>Photo by <a href="https://unsplash.com/@danedeaner?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dane Deaner</a> on <a href="https://unsplash.com/search/photos/snowboarding-big-jump?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a>.</figcaption></figure><p>I often advocate for ClojureScript over other languages, and usually it’s really difficult to appreciate the ease and simplicity of the language without experiencing it first-hand. So today we are going to cover a simple implementation of “Detecting Inactivity” or idle status.</p><p>This implementation is inspired by <a href="https://github.com/shawnmclean/Idle.js">Idle.js</a>, it’s worth referencing if you are familiar with CoffeeScript. Written in ~150 loc, which is great for a small library.</p><p>But I think we can do even better and wrap this functionality in ~50 loc.</p><p>First we want to define what events will trigger activity within our application.</p><pre>(def *default-events*<br>  [&quot;click&quot; &quot;keydown&quot; &quot;scroll&quot; &quot;mousemove&quot; &quot;mouseenter&quot; &quot;mousewheel&quot;<br>   &quot;touchstart&quot; &quot;touchmove&quot;])</pre><p>We need to know when these events were fired. So let’s get the current date-time in milliseconds.</p><pre>(defn- time-now []<br>  (.getTime (js/Date.)))</pre><p>Once we have the current time we can compare that to our users last known activity.</p><pre>(defn- time-diff [initial timeout]<br>  (&gt; timeout (- (time-now) initial))))</pre><p>Our final helpers will be used to log last user activity and set an interval of when to check for user activity.</p><pre>(defn- activity! [timestamp activity]<br>  (fn [_]<br>    (reset! timestamp (time-now))<br>    (reset! activity true))))</pre><pre>(defn when-interval [ms func]<br>  (js/setInterval func ms))</pre><p>Now we need a place to store our idle state, these are the default cells but we make them dynamic so that the state can be rebound if needed.</p><blockquote>We use the <em>j</em> symbol in reference to <em>javelin.core</em> .</blockquote><pre>(def ^:dynamic *active* (j/cell true))</pre><pre>(def ^:dynamic *last-active* (j/cell (time-now)))</pre><p>Our idle detecting library wouldn’t be any useful without a convenient way to access our idle state.</p><pre>(def idle? (j/cell= (not *active*)))</pre><pre>(def active? (j/cell= *active*))</pre><p>Finally we initialize our idle state detection, this has the dual function of attaching our event handler to all our activity events. As well as set the interval to check for user activity based on a configurable timeout.</p><p>If the difference between the last activity timestamp and the current time is greater than our timeout, user activity is considered idle.</p><pre>(defn idle! [&amp; opts]<br>  (let [timeout   (:timeout   opts 30000)<br>        events    (:events    opts *default-events*)<br>        activity  (:activity  opts *active*)<br>        timestamp (:timestamp opts *last-activity*)]<br>    (doseq [e events]<br>      (.addEventListener js/window e <br>        #(activity! timestamp activity)))<br>    (when-interval timeout<br>      #(when (time-diff @timestamp timeout)<br>        (reset! activity false)))))</pre><p>💥This library is available as part of <a href="https://github.com/degree9/enterprise">degree9/enterprise</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40ad24fe5bd5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/idle-in-50-lines-of-code-idle-40ad24fe5bd5">Idle in 50 Lines of Code — (idle?)</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[docker run -t bootclj/boot]]></title>
            <link>https://medium.com/degree9/docker-boot-65ffb02be416?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/65ffb02be416</guid>
            <category><![CDATA[clojure]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[boot-clj]]></category>
            <category><![CDATA[graal]]></category>
            <category><![CDATA[clojurescript]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Sat, 26 Jan 2019 20:58:19 GMT</pubDate>
            <atom:updated>2019-01-30T06:49:46.744Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*VCCnb6Cvn9mqaskG1GErqQ.png" /><figcaption>boot-clj logo</figcaption></figure><blockquote>TL;DR — There are now official boot-clj docker images. The one you are probably looking for is <a href="https://hub.docker.com/r/bootclj/boot">bootclj/boot:latest</a></blockquote><p>Boot just got a whole whack of official docker images on Docker Hub. With so many images to choose from how can you know you are using the right one? Well this article should help, and also give you an idea when it’s best to use each one.</p><p>We are going to start with the image everyone is probably looking for, if you’re new to boot or a seasoned pro, this is the image for you:</p><p><a href="https://hub.docker.com/r/bootclj/boot">https://hub.docker.com/r/bootclj/boot</a></p><p>This container comes preloaded with the latest version and is <strong><em>the easiest way to run boot-clj.</em></strong></p><p>Command Line: docker run -t bootclj/boot</p><p>Dockerfile:FROM bootclj/boot AS boot</p><p>When To Use:<br>- 🖥local development<br>- ☁️ CI/CD DevOps Workflows</p><p>The next image is the one you should be most excited about, it’s also the most experimental. Future version of boot target native cross-platform support using Oracle GraalVM, this image includes an early preview of the bootstrap native-image.</p><p><a href="https://hub.docker.com/r/bootclj/boot-native">https://hub.docker.com/r/bootclj/boot-native</a></p><p>We really want you to give this version a try and report issues over on <a href="https://github.com/boot-clj/bootstrap">Github</a> — but you should probably keep it out of production 💥.</p><p>Command Line: docker run -t bootclj/boot-native</p><p>Dockerfile:FROM bootclj/boot-native AS boot</p><p>When To Use:<br>- ☕️ checking compatibility with Oracle GraalVM<br>- 🖥local development<br>- 👩‍🔬experiments (polyglot apps)<br>- 🎨 art / 💥 explosions / 🔥 fire</p><p>Both of the previous images start off as bootclj/bootstrap which is the docker image of our <a href="https://github.com/boot-clj/bootstrap">boot-clj loader</a>.</p><p><a href="https://hub.docker.com/r/bootclj/bootstrap">https://hub.docker.com/r/bootclj/bootstrap</a></p><p>Our bootclj/boot image is built with bootstrap + boot-clj library, while bootclj/boot-native is a directly compiled from bootstrap using the native-image tool from Oracle GraalVM.</p><p>Command Line: docker run -t bootclj/bootstrap</p><p>Dockerfile:FROM bootclj/bootstrap AS bootstrap</p><p>When To Use:<br>- 🖥hacking on boot<br>- 👩‍🔬custom boot versions</p><p>We put together a helper which greatly simplifies the developer experience when building java/clojure/boot projects. This is the bootclj/tooling image, which includes boot andlein on top of our official clojure image.</p><p><a href="https://hub.docker.com/r/bootclj/tooling">https://hub.docker.com/r/bootclj/tooling</a></p><p>This image contains the most stable version of boot available, which is currently 2.8.2 .</p><p>Command Line: docker run -t bootclj/tooling</p><p>Dockerfile:FROM bootclj/tooling AS build</p><p>When To Use:<br>- 🖥hacking on boot<br>- 🎛complex projects w/ multiple build tools</p><p>We have also built an official clojure image for boot which can be used for general clojure development and includes both clj and clojure tools.</p><p><a href="https://hub.docker.com/r/bootclj/clojure">https://hub.docker.com/r/bootclj/clojure</a></p><p>Most of the time you will want one of the images above, however we hope that eventually BootV4 will be able to compile itself via the clj tool. This would greatly simplify the previous images and cut down on the overall number of docker layers sent over the wire.</p><p>Command Line: docker run -t bootclj/clojure:1.10</p><p>Dockerfile:FROM bootclj/clojure:1.10 AS clojure</p><p>When To Use:<br>- 🖥development via clj / clojure tools<br>- 🎃 a no-install way to try clojure in a local sandbox<br>(except docker, but you already have that don’t you 😜)</p><p>One of the many challenges when building java/clojure containers is which base image to use, or trying to create and maintain a slim and secure image on your own — No More! We took the openjdk:8-alpine image and stuffed it with the common set of tools you will probably need as a developer.</p><p><a href="https://hub.docker.com/r/bootclj/openjdk">https://hub.docker.com/r/bootclj/openjdk</a></p><p>Command Line: docker run -t bootclj/openjdk:8-alpine</p><p>Dockerfile:FROM bootclj/openjdk:8-alpine AS openjdk</p><p>When To Use:<br>- ☕️ development of java applications</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65ffb02be416" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/docker-boot-65ffb02be416">docker run -t bootclj/boot</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Boot — (future (boot))]]></title>
            <link>https://medium.com/degree9/boot-future-boot-e1948562d8d3?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1948562d8d3</guid>
            <category><![CDATA[clojure]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[boot-clj]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Sat, 12 Jan 2019 06:34:58 GMT</pubDate>
            <atom:updated>2019-03-01T04:21:05.608Z</atom:updated>
            <content:encoded><![CDATA[<h3>Boot — (future (boot))</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*VCCnb6Cvn9mqaskG1GErqQ.png" /><figcaption>boot-clj logo</figcaption></figure><p>The future of boot-clj — we at Degree9 use boot everyday, from running local builds on our dev laptops to containers in production. Boot is an essential part of our toolkit, so you can imagine we jumped at the opportunity when an open-call was placed for maintainers.</p><blockquote>TL;DR</blockquote><blockquote>1. Boot has new maintainers — Degree9</blockquote><blockquote>2. V3 targets performance, long-term support</blockquote><blockquote>3. V4 targets cross-platform, boot as libraries</blockquote><blockquote>4. Joining Open Collective</blockquote><blockquote>5. Commercial Support</blockquote><blockquote>6. T-Shirts &amp; Stickers!</blockquote><p>Boot is a great example of clojure and open-source. We want to continue developing boot the way it always has been, driven by real-world problems by the people who use it. There are many loyal boot users within the clojure community and we want them to thrive!</p><p>So what do we have in the pipeline for boot? Well a few things!</p><p>First we want to maintain backwards compatibility with boot v2.7/2.8. If you are not already on one of these versions start updating your projects now.</p><p>There are a few common issues with boot that come up from time to time. The more noticeable problems being performance and cross-platform support. These will be the intended goals for v3/v4 respectively.</p><p>Boot V3 will focus on making performance oriented changes internally with backwards compatibility in mind. Any changes which are breaking will be delayed to v4. Our goal is to improve the experience of boot users who are familiar with the current releases, while also pinning the first LTS release.</p><p>V4 will bring boot to the masses, we have always wanted to run boot with more freedom, on more platforms. There is already a prototype replacement for boot-bin which compiles the loader shim into a native image using GraalVM. You can get a sneak peek at boot/boot-graalvm. This project will create a binary that loads almost instantly, and can be built for any Host OS. It only runs on Linux today but improvements to graal will get pulled in quickly and make native image for Windows and MacOS a possibility.</p><p>Today boot is already made up of many libraries. Moving forward these will be separated into a loose collection of tools that support one another. Making the task of improving individual features and enabling cross platform builds much easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9L3iUy8lfAbLe-MkyFZ5rw.png" /><figcaption>open collective logo</figcaption></figure><p>Open-source projects don’t happen for free, there is a considerable amount of work that goes into them. So in order to continue supporting boot we are joining the Open Collective, which will provide a channel for those who want to donate to the project directly.</p><p><a href="https://opencollective.com/boot-clj">boot-clj - Open Collective</a></p><p>We know getting from development to production can be a difficult task, that’s why we are launching professional services for Boot-clj consulting.</p><p><em>D9 Pipeline</em> will enable your team to take advantage of our DevOps tools and experience — automating even the most complex builds using Boot, without the need for your team to learn another tool. Your app is written in clojure, why not your build?</p><p>Already running boot in dev/prod — thats great! Get expert advice when things don’t go as planned.</p><p>Lastly we are opening an online merchandise shop &lt;<a href="http://openswag.co/">openswag.co</a>&gt; where you can buy products with your favourite open-source project logos.</p><blockquote>A portion of every sale goes to support the open-source community.</blockquote><p>Boot &amp; Hoplon will be among the first projects to get their logos featured.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZnRrHQiywV7B5O7hyOG7w.png" /><figcaption>openswag.co</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1948562d8d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/boot-future-boot-e1948562d8d3">Boot — (future (boot))</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crypto Kickstart — Airdrops]]></title>
            <link>https://medium.com/@degree9matt/crypto-kickstart-airdrops-b44f3dc97525?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b44f3dc97525</guid>
            <category><![CDATA[cryptocurrency-investment]]></category>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Mon, 05 Mar 2018 23:57:22 GMT</pubDate>
            <atom:updated>2018-03-05T23:57:22.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/337/1*U0mpOx-jaUgXE5sQaM5UVw.png" /><figcaption>Cryptocurrency Apps for iOS</figcaption></figure><p>Today we look at a mobile (iOS-based) Cryptocurrency setup for Airdrops.</p><blockquote>While I personally use this setup for my own investments please DO NOT consider this to be professional advice. I am not responsible for lost or stolen currency/tokens.</blockquote><blockquote>TLDR; Sign up <a href="https://www.coinbase.com/join/59640303415d060149b9cc5a">here</a>, <a href="https://trustwalletapp.com/">here</a>, <a href="http://earn.com/degree9/referral/?a=uw9n1ibznhmfh2u7">here</a> and <a href="https://telegram.org/">here</a>. (referral links)</blockquote><p>What are Airdrops? An <strong>airdrop</strong> for a <a href="https://en.wikipedia.org/wiki/Cryptocurrency">cryptocurrency</a> is a procedure of distributing tokens by awarding them to existing holders of a particular <a href="https://en.wikipedia.org/wiki/Blockchain">blockchain</a> currency, such as <a href="https://en.wikipedia.org/wiki/Bitcoin">Bitcoin</a> or <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a>. — Wikipedia</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0j9OzTIyJs_NhSgOp2mlEQ.png" /><figcaption>Coinbase</figcaption></figure><p><a href="https://www.coinbase.com/join/59640303415d060149b9cc5a">Coinbase — the world’s most popular way to buy and sell bitcoin, ethereum, and litecoin.</a></p><p>Coinbase is like a digital wallet, it stores all of our bitcoins and lets us watch the market price of different cryptocurrencies, as well as set alerts for when the market prices change.</p><p>While you can always buy Bitcoins through Coinbase, we are going to look at how to receive them for free!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oBYKBkN5imLYrgdS839MpQ.png" /><figcaption>Trust Wallet</figcaption></figure><p><a href="https://trustwalletapp.com/">Trust — Secure wallet for Ethereum, ERC20 and ERC223 tokens.</a></p><p>Trust is another kind of digital wallet, specifically for Ethereum and other digital tokens, this wallet will be used to store your <em>FREE</em> tokens… yes <em>FREE</em>!</p><p>How do you earn your <em>FREE </em>tokens? Keep reading….</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLh0yKhEzBuxj6av1IahgA.png" /><figcaption>Earn.com</figcaption></figure><p><a href="http://earn.com/degree9/referral/?a=uw9n1ibznhmfh2u7">Earn — Set up an Earn.com profile to receive paid messages from people outside your network.</a></p><p>Earn is commonly used for Airdrops, tokens distributed by the creators to gain awareness for their apps and other projects.</p><p>By using Earn, you can receive Bitcoins for completing Airdrop tasks. This is a direct way to earn both Bitcoins and Tokens on the Ethereum network.</p><p>Once you have completed a few tasks you can cashout your Bitcoins to Coinbase and watch your new Bitcoin investments grow (and shrink) with the market.</p><p>To complete these tasks make sure you are providing your Trust Wallet address to receive the <em>FREE</em> tokens from the Airdrops. You will also need to provide a Telegram username to verify yourself.</p><blockquote>DO NOT use your Coinbase address for the airdrops.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Au-ahI_mws57BOcPnRtiw.png" /><figcaption>Telegram</figcaption></figure><p><a href="https://telegram.org/">Telegram — a new era of messaging.</a></p><p>Telegram is often used by Token creators to discuss their projects and get people involved with the community. For most airdrops you will need to provide your Telegram username and be a member of the community until the airdrop is complete.</p><p>Thats all folks! With the few apps above you too can start investing in Cryptocurrencies for free, and get some tokens along the way. Who knows maybe these tokens will be worth a pretty penny in a few years.</p><blockquote>Please Note: Some of the links in this article are referral links.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b44f3dc97525" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Boot — (boot (exec))]]></title>
            <link>https://medium.com/degree9/boot-boot-exec-e1453826b732?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1453826b732</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[clojurescript]]></category>
            <category><![CDATA[boot-clj]]></category>
            <category><![CDATA[build-tool]]></category>
            <category><![CDATA[clojure]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 08:32:20 GMT</pubDate>
            <atom:updated>2018-02-28T08:33:37.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*VCCnb6Cvn9mqaskG1GErqQ.png" /><figcaption>Boot Logo</figcaption></figure><p>Recently our <a href="https://github.com/degree9/boot-exec">degree9/boot-exec</a> package hit 1800 downloads, as a build-tooling helper, we are excited to be a part of so many projects!</p><p>boot-exec has the simple job of running external processes as part of a boot build pipeline in either a blocking/non-blocking way.</p><p>This package is in use by a collection of other boot tasks:</p><ul><li><a href="https://github.com/degree9/boot-npm">degree9/boot-npm</a></li><li><a href="https://github.com/degree9/boot-bower">degree9/boot-bower</a></li><li><a href="https://github.com/degree9/boot-css">degree9/boot-css</a></li><li><a href="https://github.com/degree9/boot-semgit">degree9/boot-semgit</a></li><li>and more planned…..</li></ul><p>The primary task used within this package is exec which will provide blocking execution of an external process. It is most commonly used by another task to simplify running a specific build tool like npm or a preprocessor such aslessc.</p><p>Under the hood we are using the <em>fantastic</em> <a href="https://commons.apache.org/proper/commons-exec/index.html">Apache Commons Exec</a> library, which is written for the JVM.</p><p>At the bare minimum the exec task requires a process to be specified.</p><pre>(exec :process &quot;git&quot;)</pre><blockquote>In most cases we assume your are running on a *nix operating system, however there are some mechanisms in place for Windows support as well.</blockquote><p>The location of the process is usually determined for you, however if needed you can specify your own local or global path to the executable.</p><pre>(exec :process &quot;bower&quot; :local &quot;./&quot;)</pre><pre>(exec :process &quot;bower&quot; :global &quot;/usr/local/bin&quot;)</pre><p>This is most useful when running things from within a node_modules folder.</p><pre>(exec :process &quot;npm&quot; :local &quot;node_modules/npm/bin&quot;)</pre><p>In almost all cases you will want to pass additional parameters to your external build tools, this is supported by passing a vector of arguments as strings.</p><pre>(exec :process &quot;node&quot; :arguments [&quot;app.js&quot;])</pre><p>By default the exec task generates a temporary directory to run the external process in, this means any files the build tool generates need to be added to the boot fileset.</p><pre>(exec :process &quot;npm&quot; :arguments [&quot;install&quot;] :include true)</pre><p>The working directory can be filtered for a subset of the files using exclude .</p><pre>(exec :process &quot;npm&quot; :arguments [&quot;install&quot;] :include true :exclude #{&quot;node_modules/*.html&quot;})</pre><p>Custom directories are supported as well as cached directories, which is useful for tools which provide management features and need to operate on the project itself; a great example of this is git .</p><pre>(exec :process &quot;git&quot; :arguments [&quot;status&quot;] :directory &quot;.&quot;)</pre><p>Finally there is the option to halt the entire build if an external process returns a non-zero exit code.</p><pre>(exec :process &quot;exit&quot; :arguments [&quot;1&quot;] :fail true)</pre><p>You can look at the source over on GitHub:</p><p><a href="https://github.com/degree9/boot-exec">degree9/boot-exec</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1453826b732" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/boot-boot-exec-e1453826b732">Boot — (boot (exec))</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[meta]]]></title>
            <link>https://medium.com/degree9/meta-41aa65b8ea0e?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/41aa65b8ea0e</guid>
            <category><![CDATA[clojurescript]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[lisp]]></category>
            <category><![CDATA[clojure]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Mon, 07 Aug 2017 18:58:45 GMT</pubDate>
            <atom:updated>2017-08-07T19:00:32.685Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGTmGSAjUT_vwY89WyLrWA.png" /><figcaption>[meta]</figcaption></figure><blockquote>A stack. A framework. A conversation.</blockquote><ol><li><a href="https://medium.com/degree9/meta-declarative-applications-916a0b363512">Declarative Applications</a></li><li><a href="https://medium.com/degree9/meta-generative-applications-9ece513e212e">Generative Applications</a></li><li><a href="https://medium.com/degree9/meta-application-framework-2683aa759c6d">Application Framework</a></li><li><a href="https://medium.com/degree9/meta-data-libraries-e44ef05aada2">Data &amp; Interop Libraries</a></li><li><a href="https://medium.com/degree9/meta-host-libraries-50db6fdfd3a5">Host Libraries</a></li></ol><p><a href="https://github.com/degree9/meta">degree9/meta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41aa65b8ea0e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/meta-41aa65b8ea0e">[meta]</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[meta] — Host Libraries]]></title>
            <link>https://medium.com/degree9/meta-host-libraries-50db6fdfd3a5?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/50db6fdfd3a5</guid>
            <category><![CDATA[lisp]]></category>
            <category><![CDATA[clojurescript]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[clojure]]></category>
            <category><![CDATA[functional-programming]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Sat, 05 Aug 2017 20:36:59 GMT</pubDate>
            <atom:updated>2017-08-07T19:02:23.696Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGTmGSAjUT_vwY89WyLrWA.png" /><figcaption>[meta]</figcaption></figure><blockquote>A stack. A framework. A conversation.</blockquote><ol><li><a href="https://medium.com/degree9/meta-declarative-applications-916a0b363512">Declarative Applications</a></li><li><a href="https://medium.com/degree9/meta-generative-applications-9ece513e212e">Generative Applications</a></li><li><a href="https://medium.com/degree9/meta-application-framework-2683aa759c6d">Application Framework</a></li><li><a href="https://medium.com/degree9/meta-data-libraries-e44ef05aada2">Data &amp; Interop Libraries</a></li><li>Host Libraries (current)</li></ol><p>Lastly we come to our lowest level, the Host Libraries layer. In [meta] when referring to the Host we are talking about the Host Platform on which [meta] is implemented. For us this is <a href="https://github.com/boot-clj/boot">Boot</a> which is a Clojure application on the JVM. This is only a requirement for building and developing within [meta] and not a requirement for the final application, which is entirely JavaScript.</p><p>This layer operates on our project itself and is entirely outside of our application code. Which allows us to interact with external applications prior to any application code being compiled, it also allows compilation of different portions of application code for multiple build types.</p><p>Some examples of what [meta] does prior to the framework within Host Libraries:</p><ul><li>Project Dependencies/Environment</li><li>Generating Application Files</li><li>Executing External Applications (Node.js, NPM)</li><li>Project Versioning</li><li>Repository Sync</li><li>Multi-Build Workflows</li></ul><p>This provides a complete solution for building applications using [meta] as a single dependency.</p><p>You can try [meta] and checkout the README over at GitHub.</p><p><a href="https://github.com/degree9/meta">degree9/meta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50db6fdfd3a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/meta-host-libraries-50db6fdfd3a5">[meta] — Host Libraries</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[meta] — Data & Interop Libraries]]></title>
            <link>https://medium.com/degree9/meta-data-libraries-e44ef05aada2?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e44ef05aada2</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[clojure]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[lisp]]></category>
            <category><![CDATA[clojurescript]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Fri, 04 Aug 2017 23:19:03 GMT</pubDate>
            <atom:updated>2017-08-07T19:02:01.985Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGTmGSAjUT_vwY89WyLrWA.png" /><figcaption>[meta]</figcaption></figure><blockquote>A stack. A framework. A conversation.</blockquote><ol><li><a href="https://medium.com/degree9/meta-declarative-applications-916a0b363512">Declarative Applications</a></li><li><a href="https://medium.com/degree9/meta-generative-applications-9ece513e212e">Generative Applications</a></li><li><a href="https://medium.com/degree9/meta-application-framework-2683aa759c6d">Application Framework</a></li><li>Data &amp; Interop Libraries (current)</li><li><a href="https://medium.com/degree9/meta-host-libraries-50db6fdfd3a5">Host Libraries</a></li></ol><p>Data Libraries in [meta] are an important layer in making the whole stack unified. The goal of this layer is to make everything as functional as possible. For example <a href="https://github.com/degree9/featherscript">FeatherScript</a> is a great example of a Data Library, it takes the usual features provided by feathers.js and converts them to ClojureScript functions.</p><p>It is also responsible of sanitizing data types used in lower levels. Which means the [meta] framework only ever deals with ClojureScript data. Interacting with JavaScript objects/types breaks the abstraction between the application, it’s language and the host. Unless you are intending to interop with the Host directly, your application should constrain itself to ClojureScript data only.</p><p>Interop Libraries are used to communicate externally within the JavaScript ecosystem. Often [meta] relies on CLJSJS packages for this layer, which provides access to libraries and externs.</p><p>These layers are used together to abstract the [meta] framework from external systems and keep the application logic within ClojureScript.</p><p>You can try [meta] and checkout the README over at GitHub.</p><p><a href="https://github.com/degree9/meta">degree9/meta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e44ef05aada2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/meta-data-libraries-e44ef05aada2">[meta] — Data &amp; Interop Libraries</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[meta] — Application Framework]]></title>
            <link>https://medium.com/degree9/meta-application-framework-2683aa759c6d?source=rss-a2d5aa46d2e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2683aa759c6d</guid>
            <category><![CDATA[clojure]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[lisp]]></category>
            <category><![CDATA[clojurescript]]></category>
            <category><![CDATA[functional-programming]]></category>
            <dc:creator><![CDATA[flyboarder]]></dc:creator>
            <pubDate>Thu, 03 Aug 2017 22:50:17 GMT</pubDate>
            <atom:updated>2017-08-05T20:38:02.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGTmGSAjUT_vwY89WyLrWA.png" /><figcaption>[meta]</figcaption></figure><blockquote>[meta] A stack. A framework. A conversation.</blockquote><ol><li><a href="https://medium.com/degree9/meta-declarative-applications-916a0b363512">Declarative Applications</a></li><li><a href="https://medium.com/degree9/meta-generative-applications-9ece513e212e">Generative Applications</a></li><li>Application Framework (current)</li><li><a href="https://medium.com/degree9/meta-data-libraries-e44ef05aada2">Data &amp; Interop Libraries</a></li><li><a href="https://medium.com/degree9/meta-host-libraries-50db6fdfd3a5">Host Libraries</a></li></ol><p>Previously we looked at application templates in our Declarative Application layer as well as configurations within our Generative Application layer.</p><p>This provides a way to build dynamic configuration based applications using ClojureScript. This presents a new problem.</p><blockquote>How do we make templates and configurations reusable?</blockquote><p>Introducing the Application Framework layer, [meta] framework.</p><p>A major use case for [meta] is the ability to <em>“forget” </em>about everything except the Application Logic. This means that your project depends on [meta] as a single dependency which gets you up and running, then add additional dependencies for anything required by the Application Logic.</p><pre>[meta] Framework + Application Logic = Your Application</pre><p>To adhere to this goal, [meta] framework wraps all of the underlying libraries and abstracts the usual bits of logic which would be required by any application using these technologies. This allows us to create templates which refer to either:</p><ol><li>[meta] namespaces</li><li>underlying namespaces</li></ol><blockquote>Although, using underlying namespaces is not recommended as these may change!</blockquote><p>Currently, [meta] provides a collection of ready to use namespaces within the framework. These extend common libraries available within the JavaScript/ClojureScript ecosystem, bringing external integrations right into the framework.</p><p>The framework itself is divided into tiers:</p><ol><li>Core</li><li>Components</li><li>Integrations</li></ol><p>All <em>components and integrations </em>depend on the <em>core.</em> Core is a <em>well-known</em> list of variables which can be used by any of the Components or Integrations. Each variable in Core is dynamic which allows for different runtime bindings to be used. The value of this is apparent when you want to start swapping between integrations within different parts of your application.</p><p>This can be used to connect to multiple types of backends, change authentication providers or it can be used to swap routing components within the application.</p><p>Separating application concepts such as routing from their implementation, allows the exchange of Integrations within Components.</p><p>Components represent concepts within the [meta] framework, they generally relate to the list of variables within core.</p><pre>(binding [meta.core/*router* (meta.routing/router :history5)] ...)</pre><p>Binding components within the application allows you to make global changes at a single code site or localize changes within different portions.</p><blockquote>Components may also contain their own abstract state.</blockquote><p>Integrations are directly implemented on top of 3rd party libraries and abstract any initialization or configurations which may be required to use the libraries.</p><p>Using Closure Compiler features such as Advanced Compilation removes any unused Integrations from the final compiled JavaScript.</p><p>You can try [meta] and checkout the README over at GitHub.</p><p><a href="https://github.com/degree9/meta">degree9/meta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2683aa759c6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/degree9/meta-application-framework-2683aa759c6d">[meta] — Application Framework</a> was originally published in <a href="https://medium.com/degree9">degree9</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>