path: root/articles/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Articles on Nine Nines</title>
    <link>https://ninenines.eu/articles/</link>
    <description>Recent content in Articles on Nine Nines</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 Dec 2017 12:00:00 +0100</lastBuildDate>
    
	<atom:link href="https://ninenines.eu/articles/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Cowboy 2.2</title>
      <link>https://ninenines.eu/articles/cowboy-2.2.0/</link>
      <pubDate>Wed, 13 Dec 2017 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.2.0/</guid>
      <description>Cowboy 2.2.0 has been released!
 This release focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs.
    The cowboy_req:stream_trailers/2 function has been added. It terminates the streamed response by adding some trailer field values. This feature is required for gRPC.    The max_skip_body_length option was added. It controls how much of the request body we are willing to skip to get to the next request for HTTP/1.</description>
    </item>
    
    <item>
      <title>Cowboy 2.1</title>
      <link>https://ninenines.eu/articles/cowboy-2.1.0/</link>
      <pubDate>Thu, 09 Nov 2017 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.1.0/</guid>
      <description>Cowboy 2.1.0 has been released!
 This release focused on adding features that were temporarily removed during the 2.0 release process:
    The client TLS certificate can now be obtained.    The 100 Continue response is now sent automatically again when necessary.    NEW: It is now possible to send informational responses (1XX) directly from user code via the cowboy_req:inform/2,3 functions.    NEW: cowboy_rest handlers can now switch to any other type of handler from almost any callback.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0/</link>
      <pubDate>Wed, 04 Oct 2017 12:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0/</guid>
      <description>Cowboy 2.0.0 has been released!
 This is the new stable version of Cowboy. There are no new releases planned for the 1.x version of Cowboy.
 The highlights from the release are:
    HTTP/2 support!    Websocket compression!    Much simpler, cleaner interface. No more weird errors just because you discard the Req object.    A new low-level interface that receives all events from every set of request and response.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 release candidate 2</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0-rc.2/</link>
      <pubDate>Wed, 23 Aug 2017 18:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0-rc.2/</guid>
      <description>Cowboy 2.0.0-rc.2 has been released!
 This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
 This new version contains fixes for the following issues:
    HTTP/2 server push was using the wrong header compression context.    HTTP/2 flow control could end up queueing data in the wrong order when resuming the sending of data.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 release candidate 1</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0-rc.1/</link>
      <pubDate>Mon, 24 Jul 2017 18:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0-rc.1/</guid>
      <description>Cowboy 2.0.0-rc.1 has been released!
 This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
 The plan is to have a new RC version every couple weeks until the summer ends or later if there are still blocking issues open. Only issues that can&amp;#8217;t be fixed without making breaking changes to the interface may block the release.</description>
    </item>
    
    <item>
      <title>The elephant in the room</title>
      <link>https://ninenines.eu/articles/the-elephant-in-the-room/</link>
      <pubDate>Sun, 26 Mar 2017 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/the-elephant-in-the-room/</guid>
      <description>Have you ever tried telling someone why they should use Erlang? You boast the smaller code size, the auto healing mechanisms, the distribution and they seem really excited. They wonder why they never heard about Erlang before. And then you show them what the code looks like. All excitement goes away. The smiles disappear. Their face starts becoming really serious.
 You lost them. You know you lost them. They comment on the syntax, or perhaps you do, already admitting defeat.</description>
    </item>
    
    <item>
      <title>Don&#39;t let it crash</title>
      <link>https://ninenines.eu/articles/dont-let-it-crash/</link>
      <pubDate>Sun, 22 Jan 2017 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/dont-let-it-crash/</guid>
      <description>We have a specific mindset when writing Erlang programs. We focus on the normal execution of the program and don&amp;#8217;t handle most of the errors that may occur. We sometimes call this normal execution the happy path.
 The general pattern behind writing only for the happy path, letting the VM catch errors (writing them to a log for future consumption) and then having a supervisor restart the processes that failed from a clean state, has a name.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 pre-release 4</title>
      <link>https://ninenines.eu/articles/cowboy-2.0.0-pre.4/</link>
      <pubDate>Tue, 03 Jan 2017 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy-2.0.0-pre.4/</guid>
      <description>Cowboy 2.0.0-pre.4 has been released!
 This is the new recommended version of Cowboy. While I would not recommend putting it in production just yet, I do recommend you start writing new applications with this Cowboy version.
 The most significant changes in the pre-release are:
    A new architecture: there now is one process per connection and one process per request. This was done because HTTP/2 allows running requests concurrently.</description>
    </item>
    
    <item>
      <title>Ranch 1.3</title>
      <link>https://ninenines.eu/articles/ranch-1.3/</link>
      <pubDate>Mon, 28 Nov 2016 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-1.3/</guid>
      <description>Ranch 1.3.0 has been released!
 This release fixes a number of long standing issues and adds a small number of features:
 The ssl application has been added to the list of dependencies. If you don&amp;#8217;t need it, you can remove it automatically when fetching Ranch or when building the release. If you do need it, you will no longer have issues shutting down a node because of Ranch.</description>
    </item>
    
    <item>
      <title>Mailing list archived</title>
      <link>https://ninenines.eu/articles/ml-archives/</link>
      <pubDate>Mon, 29 Aug 2016 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ml-archives/</guid>
      <description>The old mailing list archives have been added to the site, mainly for referencing purposes.
 The mailing list has been shut down and all personal information has been deleted.
 If you need help with a project, consider either opening a ticket on that project&amp;#8217;s issues tracker or going through the community channels (erlang-questions, #ninenines or #erlang on Freenode).
 Prefer tickets; often when people have issues it highlights an underlying problem in the project or its documentation.</description>
    </item>
    
    <item>
      <title>Website update</title>
      <link>https://ninenines.eu/articles/website-update/</link>
      <pubDate>Sat, 02 Apr 2016 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/website-update/</guid>
      <description>Last week-end I updated the Nine Nines website.
 I switched to Hugo. The site is now built from Asciidoc documents. You probably saw me switch to Asciidoc for documentation this past year. This is the natural conclusion to that story. The great thing is that with a little bit of Makefile magic I can just copy the documentation files into Hugo and poof, they appear on the website.
 I am very happy with that new setup.</description>
    </item>
    
    <item>
      <title>The Erlanger Playbook September 2015 Update</title>
      <link>https://ninenines.eu/articles/erlanger-playbook-september-2015-update/</link>
      <pubDate>Wed, 02 Sep 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlanger-playbook-september-2015-update/</guid>
      <description>An update to The Erlanger Playbook is now available!
 The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
 The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
 This update fixes a number of things and adds two chapters: IOlists and Erlang building blocks.</description>
    </item>
    
    <item>
      <title>The Erlanger Playbook</title>
      <link>https://ninenines.eu/articles/erlanger-playbook/</link>
      <pubDate>Thu, 18 Jun 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlanger-playbook/</guid>
      <description>I am proud to announce the pre-release of The Erlanger Playbook.
 The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
 The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
 The following sections are currently available:</description>
    </item>
    
    <item>
      <title>Validating UTF-8 binaries with Erlang</title>
      <link>https://ninenines.eu/articles/erlang-validate-utf8/</link>
      <pubDate>Fri, 06 Mar 2015 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang-validate-utf8/</guid>
      <description>Yesterday I pushed Websocket permessage-deflate to Cowboy master. I also pushed a change in the way the code validates UTF-8 data (required for text and close frames as per the spec).
 When looking into why the permessage-deflate tests in autobahntestsuite were taking such a long time, I found that autobahn is using an adaptation of the algorithm named Flexible and Economical UTF-8 Decoder. This is the C99 implementation:
 // Copyright (c) 2008-2009 Bjoern Hoehrmann &amp;lt;bjoern@hoehrmann.</description>
    </item>
    
    <item>
      <title>On open source</title>
      <link>https://ninenines.eu/articles/on-open-source/</link>
      <pubDate>Fri, 05 Sep 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/on-open-source/</guid>
      <description>Last week I read a great article on contributing to open source by Alvaro Videla. He makes many great points and I am in agreement with most of it. This made me want to properly explain my point of view with regard to open source and contributions. Unlike most open source evangelism articles I will not talk about ideals or any of that crap, but rather my personal feelings and experience.</description>
    </item>
    
    <item>
      <title>The story so far</title>
      <link>https://ninenines.eu/articles/the-story-so-far/</link>
      <pubDate>Sat, 23 Aug 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/the-story-so-far/</guid>
      <description>As I am away from home with little to do (some call this a vacation) I wanted to reflect a little on the story so far, or how I arrived to Erlang and got to where I am now. The raw personal experience. It&amp;#8217;ll be an article that&amp;#8217;s more about social aspect, communities and marketing a project than technical considerations. As a period piece, it will also allow me to reflect on the evolution of Erlang in recent years.</description>
    </item>
    
    <item>
      <title>Cowboy 2.0 and query strings</title>
      <link>https://ninenines.eu/articles/cowboy2-qs/</link>
      <pubDate>Wed, 20 Aug 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/cowboy2-qs/</guid>
      <description>Now that Cowboy 1.0 is out, I can spend some of my time thinking about Cowboy 2.0 that will be released soon after Erlang/OTP 18.0. This entry discusses the proposed changes to query string handling in Cowboy.
 Cowboy 2.0 will respond to user wishes by simplifying the interface of the cowboy_req module. Users want two things: less juggling with the Req variable, and more maps. Maps is the only dynamic key/value data structure in Erlang that we can match directly to extract values, allowing users to greatly simplify their code as they don&amp;#8217;t need to call functions to do everything anymore.</description>
    </item>
    
    <item>
      <title>January 2014 status</title>
      <link>https://ninenines.eu/articles/january-2014-status/</link>
      <pubDate>Tue, 07 Jan 2014 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/january-2014-status/</guid>
      <description>I will now be regularly writing posts about project status, plans and hopes for the future.
 Before that though, there&amp;#8217;s one important news to share.
 Until a year ago all development was financed through consulting and development services. This worked alright but too much time was spent doing things that didn&amp;#8217;t benefit the open source projects. And that didn&amp;#8217;t make me happy at all. Because I like being happy I stopped that for the most part and spent the year figuring things out, experimenting and discussing with people about it.</description>
    </item>
    
    <item>
      <title>Farwest got funded!</title>
      <link>https://ninenines.eu/articles/farwest-funded/</link>
      <pubDate>Thu, 27 Jun 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/farwest-funded/</guid>
      <description>This was a triumph! I&amp;#8217;m making a note here: HUGE SUCCESS!!
  It&amp;#8217;s hard to overstate my satisfaction. Thanks to everyone who made this possible.
 If you have backed this fundraiser, and haven&amp;#8217;t provided your personal details yet, please do so quickly so that your rewards can be sent!
 I am hoping that we will be able to make good use of all that money. The details of the expenses will be published regularly on the 2013 Fundraiser wiki page, giving you full disclosure as to how your money is used.</description>
    </item>
    
    <item>
      <title>Build Erlang releases with Erlang.mk and Relx</title>
      <link>https://ninenines.eu/articles/erlang.mk-and-relx/</link>
      <pubDate>Tue, 28 May 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang.mk-and-relx/</guid>
      <description>Building OTP releases has always been a difficult task. Tools like Reltool or Rebar have made this simpler, but it&amp;#8217;s no panacea. This article will show you an alternative and hopefully much simpler solution.
 There is two steps to building a release. First you need to build the various OTP applications you want to include in the release. Once done, you need to create the release itself, by including the Erlang runtime system alongside the applications, a boot script to start the node and all its applications, and some configuration files.</description>
    </item>
    
    <item>
      <title>Xerl: intermediate module</title>
      <link>https://ninenines.eu/articles/xerl-0.5-intermediate-module/</link>
      <pubDate>Mon, 25 Mar 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.5-intermediate-module/</guid>
      <description>Today we will start the work on the intermediate module that will be used to run the code for the expressions found in our file&amp;#8217;s body, replacing our interpreter.
 This is what we want to have when all the work is done:
 xerl -&amp;gt; tokens -&amp;gt; AST -&amp;gt; intermediate -&amp;gt; cerl  Today we will perform this work only on the atomic integer expression however, so we will not build any module at the end.</description>
    </item>
    
    <item>
      <title>Xerl: expression separator</title>
      <link>https://ninenines.eu/articles/xerl-0.4-expression-separator/</link>
      <pubDate>Fri, 01 Mar 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.4-expression-separator/</guid>
      <description>As promised we are adding an expression separator this time. This will be short and easy.
 In the tokenizer we only need to add a line recognizing the comma as a valid token.
 , : {token, {&#39;,&#39;, TokenLine}}. Then we need to change the following lines in the parser:
 exprs -&amp;gt; expr : [&#39;$1&#39;]. exprs -&amp;gt; expr exprs : [&#39;$1&#39; | &#39;$2&#39;]. And add a comma between the expressions on the second line:</description>
    </item>
    
    <item>
      <title>Erlang Scalability</title>
      <link>https://ninenines.eu/articles/erlang-scalability/</link>
      <pubDate>Mon, 18 Feb 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/erlang-scalability/</guid>
      <description>I would like to share some experience and theories on Erlang scalability.
 This will be in the form of a series of hints, which may or may not be accompanied with explanations as to why things are this way, or how they improve or reduce the scalability of a system. I will try to do my best to avoid giving falsehoods, even if that means a few things won&amp;#8217;t be explained.</description>
    </item>
    
    <item>
      <title>Xerl: atomic expressions</title>
      <link>https://ninenines.eu/articles/xerl-0.3-atomic-expressions/</link>
      <pubDate>Mon, 18 Feb 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.3-atomic-expressions/</guid>
      <description>We will be adding atomic integer expressions to our language. These look as follow in Erlang:
 42. And the result of this expression is of course 42.
 We will be running this expression at compile time, since we don&amp;#8217;t have the means to run code at runtime yet. This will of course result in no module being compiled, but that&amp;#8217;s OK, it will allow us to discuss a few important things we&amp;#8217;ll have to plan for later on.</description>
    </item>
    
    <item>
      <title>Xerl: two modules</title>
      <link>https://ninenines.eu/articles/xerl-0.2-two-modules/</link>
      <pubDate>Sun, 03 Feb 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.2-two-modules/</guid>
      <description>Everything is an expression.
 This sentence carries profound meaning. We will invoke it many times over the course of these articles.
 If everything is an expression, then the language shouldn&amp;#8217;t have any problem with me defining two modules in the same source file.
 mod first_module begin end mod second_module begin end Likewise, it shouldn&amp;#8217;t have any problem with me defining a module inside another module.
 mod out_module begin mod in_module begin end end Of course, in the context of the Erlang VM, these two snippets are equivalent; there is nothing preventing you from calling the in_module module from any other module.</description>
    </item>
    
    <item>
      <title>Xerl: empty modules</title>
      <link>https://ninenines.eu/articles/xerl-0.1-empty-modules/</link>
      <pubDate>Wed, 30 Jan 2013 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/xerl-0.1-empty-modules/</guid>
      <description>Let&amp;#8217;s build a programming language. I call it Xerl: eXtended ERLang. It&amp;#8217;ll be an occasion for us to learn a few things, especially me.
 Unlike in Erlang, in this language, everything is an expression. This means that modules and functions are expression, and indeed that you can have more than one module per file.
 We are just starting, so let&amp;#8217;s no go ahead of ourselves here. We&amp;#8217;ll begin with writing the code allowing us to compile an empty module.</description>
    </item>
    
    <item>
      <title>Build an FTP Server with Ranch in 30 Minutes</title>
      <link>https://ninenines.eu/articles/ranch-ftp/</link>
      <pubDate>Wed, 14 Nov 2012 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/ranch-ftp/</guid>
      <description>Last week I was speaking at the London Erlang Factory Lite where I presented a live demonstration of building an FTP server using Ranch. As there was no slide, you should use this article as a reference instead.
 The goal of this article is to showcase how to use Ranch for writing a network protocol implementation, how Ranch gets out of the way to let you write the code that matters, and the common techniques used when writing servers.</description>
    </item>
    
    <item>
      <title>Erlang Tic Tac Toe</title>
      <link>https://ninenines.eu/articles/tictactoe/</link>
      <pubDate>Wed, 17 Oct 2012 00:00:00 +0100</pubDate>
      
      <guid>https://ninenines.eu/articles/tictactoe/</guid>
      <description>Everyone knows Tic Tac Toe, right?
 Players choose either to be the Xs or the Os, then place their symbol on a 3x3 board one after another, trying to create a line of 3 of them.
 Writing an algorithm to check for victory sounds easy, right? It&amp;#8217;s easily tested, considering there&amp;#8217;s only 8 possible winning rows (3 horizontal, 3 vertical and 2 diagonal).
 In Erlang though, you probably wouldn&amp;#8217;t want an algorithm.</description>
    </item>
    
  </channel>
</rss>