182 lines
11 KiB
HTML
182 lines
11 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<title>Alexis King's Blog</title>
|
||
<meta name="description" content="Alexis King's Blog">
|
||
<meta name="author" content="Alexis King">
|
||
<meta name="keywords" content="macros, elm, javascript, meta, typed racket, all, racket, heroku, ruby, angular, 12factor, rails, frog, envy">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<link rel="icon" href="/favicon.ico">
|
||
<link rel="canonical" href="http://lexi-lambda.github.io/index.html">
|
||
|
||
|
||
<!-- CSS -->
|
||
<link rel="stylesheet" type="text/css" href="//fonts.googleapis.com/css?family=Merriweather+Sans:400,300,300italic,400italic,700,700italic,800,800italic|Merriweather:400,300,300italic,400italic,700,700italic,900,900italic|Source+Code+Pro:200,300,400,500,600,700,900">
|
||
<link rel="stylesheet" type="text/css" href="/css/application.min.css">
|
||
<link rel="stylesheet" type="text/css" href="/css/pygments.min.css">
|
||
<!-- Feeds -->
|
||
<link rel="alternate" type="application/atom+xml"
|
||
href="/feeds/all.atom.xml" title="Atom Feed">
|
||
<link rel="alternate" type="application/rss+xml"
|
||
href="/feeds/all.rss.xml" title="RSS Feed">
|
||
<!-- JS -->
|
||
<!-- <script src="/js/application.min.js"></script> -->
|
||
<script type="text/javascript">
|
||
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
|
||
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
|
||
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
|
||
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
|
||
|
||
ga('create', 'UA-65250372-1', 'auto');
|
||
ga('send', 'pageview');
|
||
</script>
|
||
</head>
|
||
<body>
|
||
<div id="page-content">
|
||
<!-- Navigation Bar -->
|
||
<header>
|
||
<nav role="navigation" class="navigation-bar">
|
||
<ul class="navigation-items left">
|
||
<li id="blog-title-header"><a href="/"><h1>Alexis King</h1></a></li>
|
||
</ul>
|
||
<ul class="navigation-items center"></ul>
|
||
<ul class="navigation-items right">
|
||
<li><a href="/">Home</a></li>
|
||
<li><a href="/about.html">About</a></li>
|
||
</ul>
|
||
</nav>
|
||
</header>
|
||
<section role="main">
|
||
<!-- Main column -->
|
||
<div class="content" class="col-md-12">
|
||
|
||
|
||
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2016/02/18/simple-safe-multimethods-in-racket/'>Simple, safe multimethods in Racket</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2016-02-18T18:48:32">
|
||
2016-02-18
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/racket.html">racket</a>, <a href="/tags/macros.html">macros</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p>Racket ships with <code>racket/generic</code>, a system for defining <em>generic methods</em>, functions that work differently depending on what sort of value they are supplied. I have made heavy use of this feature in my collections library, and it has worked well for my needs, but that system does have a bit of a limitation: it only supports <em>single dispatch</em>. Method implementations may only be chosen based on a single argument, so multiple dispatch is impossible.</p>
|
||
<footer class="read-more"><a href="/blog/2016/02/18/simple-safe-multimethods-in-racket/">…more…</a></footer>
|
||
</article>
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2015/12/21/adts-in-typed-racket-with-macros/'>ADTs in Typed Racket with macros</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2015-12-21T17:57:07">
|
||
2015-12-21
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/racket.html">racket</a>, <a href="/tags/typed-racket.html">typed racket</a>, <a href="/tags/macros.html">macros</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p>Macros are one of Racket’s flagship features, and its macro system really is state of the art. Of course, it can sometimes be difficult to demonstrate <em>why</em> macros are so highly esteemed, in part because it can be hard to find self-contained examples of using macros in practice. Of course, one thing that macros are perfect for is filling a “hole” in the language by introducing a feature a language lacks, and one of those features in Typed Racket is <strong>ADTs</strong>.</p>
|
||
<footer class="read-more"><a href="/blog/2015/12/21/adts-in-typed-racket-with-macros/">…more…</a></footer>
|
||
</article>
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2015/11/06/functionally-updating-record-types-in-elm/'>Functionally updating record types in Elm</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2015-11-06T19:58:40">
|
||
2015-11-06
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/elm.html">elm</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p><a href="http://elm-lang.org">Elm</a> is a wonderful language for building web apps, and I love so much of its approach to language design. Elm does so many things <em>right</em> straight out of the box, and that’s a real breath of fresh air in the intersection of functional programming and web development. Still, it gets one thing wrong, and unfortunately, that one thing is incredibly important. Elm took the “functions” out of “functional record types”.</p>
|
||
<footer class="read-more"><a href="/blog/2015/11/06/functionally-updating-record-types-in-elm/">…more…</a></footer>
|
||
</article>
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2015/09/23/canonical-factories-for-testing-with-factory-girl-api/'>Canonical factories for testing with factory_girl_api</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2015-09-23T16:30:12">
|
||
2015-09-23
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/ruby.html">ruby</a>, <a href="/tags/rails.html">rails</a>, <a href="/tags/javascript.html">javascript</a>, <a href="/tags/angular.html">angular</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p>Modern web applications are often built as <em>single-page apps</em>, which are great for keeping concerns separated, but problematic when tested. Logic needs to be duplicated in front- and back-end test suites, and if the two apps diverge, the tests won’t catch the failure. I haven’t found a very good solution to this problem aside from brittle, end-to-end integration tests.</p>
|
||
|
||
<p>To attempt to address a fraction of this problem, I built <a href="https://github.com/lexi-lambda/factory_girl_api">factory_girl_api</a>, a way to share context setup between both sides of the application.</p>
|
||
<footer class="read-more"><a href="/blog/2015/09/23/canonical-factories-for-testing-with-factory-girl-api/">…more…</a></footer>
|
||
</article>
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2015/08/30/managing-application-configuration-with-envy/'>Managing application configuration with Envy</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2015-08-30T16:05:37">
|
||
2015-08-30
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/envy.html">envy</a>, <a href="/tags/racket.html">racket</a>, <a href="/tags/12factor.html">12factor</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p>Application configuration can be a pain. Modern web apps don’t live on dedicated boxes, they run on VPSes somewhere in the amorphous “cloud”, and keeping configuration out of your application’s repository can seem like more trouble than it’s worth. Fortunately, <a href="http://12factor.net">The Twelve-Factor App</a> provides a set of standards for keeping web apps sane, and <a href="http://12factor.net/config">one of those guidelines advises keeping configuration in the environment</a>.</p>
|
||
|
||
<p><a href="https://github.com/lexi-lambda/envy">Envy</a> is the declarative bridge between Racket code and the outside world of the environment.</p>
|
||
<footer class="read-more"><a href="/blog/2015/08/30/managing-application-configuration-with-envy/">…more…</a></footer>
|
||
</article>
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2015/08/22/deploying-racket-applications-on-heroku/'>Deploying Racket applications on Heroku</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2015-08-22T14:47:49">
|
||
2015-08-22
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/racket.html">racket</a>, <a href="/tags/heroku.html">heroku</a>, <a href="/tags/12factor.html">12factor</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p><a href="https://www.heroku.com">Heroku</a> is a “platform as a service” that provides an incredibly simple way to deploy simple internet applications, and I take liberal advantage of its free tier for testing out simple applications. It has support for a variety of languages built-in, but Racket is not currently among them. Fortunately, Heroku provides an interface for adding custom build processes for arbitrary types of applications, called “buildpacks”. I’ve built one for Racket apps, and with just a little bit of configuration, it’s possible to get a Racket webserver running on Heroku.</p>
|
||
<footer class="read-more"><a href="/blog/2015/08/22/deploying-racket-applications-on-heroku/">…more…</a></footer>
|
||
</article>
|
||
<article class="inline">
|
||
<header>
|
||
<h2 class="title"><a href='/blog/2015/07/18/automatically-deploying-a-frog-powered-blog-to-github-pages/'>Automatically deploying a Frog-powered blog to GitHub pages</a></h2>
|
||
<div class='date-and-tags'>
|
||
<time datetime="2015-07-18T19:09:01">
|
||
2015-07-18
|
||
</time>
|
||
<span style="margin: 0 3px">⦿</span>
|
||
<span class="tags"><a href="/tags/racket.html">racket</a>, <a href="/tags/frog.html">frog</a>, <a href="/tags/meta.html">meta</a></span>
|
||
</div>
|
||
</header>
|
||
|
||
<p>So, I have a blog now. It’s a simple static blog, but what’s unique about it is that it’s powered by Racket; specifically, it uses <a href="http://www.greghendershott.com">Greg Hendershott</a>’s fantastic <a href="https://github.com/greghendershott/frog">Frog</a> tool. I’ve taken this and moulded it to my tastes to build my blog, including configuring automatic deployment via <a href="https://travis-ci.org">Travis CI</a>, so my blog is always up-to-date.</p>
|
||
<footer class="read-more"><a href="/blog/2015/07/18/automatically-deploying-a-frog-powered-blog-to-github-pages/">…more…</a></footer>
|
||
</article>
|
||
</div>
|
||
</section>
|
||
<footer>
|
||
<div class="content">
|
||
<h2 id="copyright-notice">© 2016, Alexis King</h2>
|
||
<h3>
|
||
Built with <a href="https://github.com/greghendershott/frog">Frog</a>, the
|
||
<strong>fr</strong>ozen bl<strong>og</strong> tool.
|
||
</h3>
|
||
<h3>
|
||
Feeds are available via <a href="/feeds/all.atom.xml">Atom</a>
|
||
or <a href="/feeds/all.rss.xml">RSS</a>.
|
||
</h3>
|
||
</div>
|
||
</footer>
|
||
</div>
|
||
</body>
|
||
</html> |