1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
|
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
<meta name="author" content="Loïc Hoguin based on a design from (Soft10) Pol Cámara">
<meta name="generator" content="Hugo 0.17" />
<title>Nine Nines: Articles</title>
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,700,400italic' rel='stylesheet' type='text/css'>
<link href="/css/bootstrap.min.css" rel="stylesheet">
<link href="/css/99s.css" rel="stylesheet">
<link rel="shortcut icon" href="/img/ico/favicon.ico">
<link rel="apple-touch-icon-precomposed" sizes="114x114" href="/img/ico/apple-touch-icon-114.png">
<link rel="apple-touch-icon-precomposed" sizes="72x72" href="/img/ico/apple-touch-icon-72.png">
<link rel="apple-touch-icon-precomposed" href="/img/ico/apple-touch-icon-57.png">
<link rel="alternate" href="https://ninenines.eu/articles/index.xml" type="application/rss+xml" title="Nine Nines" />
</head>
<body class="">
<header id="page-head">
<div id="topbar" class="container">
<div class="row">
<div class="span2">
<h1 id="logo"><a href="/" title="99s">99s</a></h1>
</div>
<div class="span10">
<div id="side-header">
<nav>
<ul>
<li class="active"><a title="Hear my thoughts" href="/articles">Articles</a></li>
<li><a title="Watch my talks" href="/talks">Talks</a></li>
<li><a title="Read the docs" href="/docs">Documentation</a></li>
<li><a title="Request my services" href="/services">Consulting & Training</a></li>
</ul>
</nav>
<ul id="social">
<li>
<a href="https://github.com/ninenines" title="Check my Github repositories"><img src="/img/ico_github.png" data-hover="/img/ico_github_alt.png" alt="Github"></a>
</li>
<li>
<a title="Keep in touch!" href="http://twitter.com/lhoguin"><img src="/img/ico_microblog.png" data-hover="/img/ico_microblog_alt.png"></a>
</li>
<li>
<a title="Contact me" href="mailto:[email protected]"><img src="/img/ico_mail.png" data-hover="/img/ico_mail_alt.png"></a>
</li>
</ul>
</div>
</div>
</div>
</div>
</header>
<div id="contents" class="two_col">
<div class="container">
<div class="row">
<div class="span9 maincol">
<h1 class="lined-header"><span>Articles</span></h1>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/ranch-1.3/">Ranch 1.3</a></h2>
<p class="date">
<span class="day">28</span>
<span class="month">Nov</span>
</p>
</header>
<p>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’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/ranch-1.3/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/ml-archives/">Mailing list archived</a></h2>
<p class="date">
<span class="day">29</span>
<span class="month">Aug</span>
</p>
</header>
<p>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’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/ml-archives/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/website-update/">Website update</a></h2>
<p class="date">
<span class="day">02</span>
<span class="month">Apr</span>
</p>
</header>
<p>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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/website-update/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/erlanger-playbook-september-2015-update/">The Erlanger Playbook September 2015 Update</a></h2>
<p class="date">
<span class="day">02</span>
<span class="month">Sep</span>
</p>
</header>
<p>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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/erlanger-playbook-september-2015-update/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/erlanger-playbook/">The Erlanger Playbook</a></h2>
<p class="date">
<span class="day">18</span>
<span class="month">Jun</span>
</p>
</header>
<p>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:</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/erlanger-playbook/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/erlang-validate-utf8/">Validating UTF-8 binaries with Erlang</a></h2>
<p class="date">
<span class="day">06</span>
<span class="month">Mar</span>
</p>
</header>
<p>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 <bjoern@hoehrmann.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/erlang-validate-utf8/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/on-open-source/">On open source</a></h2>
<p class="date">
<span class="day">05</span>
<span class="month">Sep</span>
</p>
</header>
<p>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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/on-open-source/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/the-story-so-far/">The story so far</a></h2>
<p class="date">
<span class="day">23</span>
<span class="month">Aug</span>
</p>
</header>
<p>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’ll be an article that’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/the-story-so-far/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/cowboy2-qs/">Cowboy 2.0 and query strings</a></h2>
<p class="date">
<span class="day">20</span>
<span class="month">Aug</span>
</p>
</header>
<p>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’t need to call functions to do everything anymore.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/cowboy2-qs/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/january-2014-status/">January 2014 status</a></h2>
<p class="date">
<span class="day">07</span>
<span class="month">Jan</span>
</p>
</header>
<p>I will now be regularly writing posts about project status, plans
and hopes for the future.
Before that though, there’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’t benefit the open source projects.
And that didn’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/january-2014-status/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/farwest-funded/">Farwest got funded!</a></h2>
<p class="date">
<span class="day">27</span>
<span class="month">Jun</span>
</p>
</header>
<p>This was a triumph! I’m making a note here: HUGE SUCCESS!!
It’s hard to overstate my satisfaction. Thanks to everyone who
made this possible.
If you have backed this fundraiser, and haven’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/farwest-funded/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/erlang.mk-and-relx/">Build Erlang releases with Erlang.mk and Relx</a></h2>
<p class="date">
<span class="day">28</span>
<span class="month">May</span>
</p>
</header>
<p>Building OTP releases has always been a difficult task. Tools like
Reltool or Rebar have made this simpler, but
it’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/erlang.mk-and-relx/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/xerl-0.5-intermediate-module/">Xerl: intermediate module</a></h2>
<p class="date">
<span class="day">25</span>
<span class="month">Mar</span>
</p>
</header>
<p>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’s body, replacing our interpreter.
This is what we want to have when all the work is done:
xerl -> tokens -> AST -> intermediate -> cerl
Today we will perform this work only on the atomic integer
expression however, so we will not build any module at the end.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/xerl-0.5-intermediate-module/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/xerl-0.4-expression-separator/">Xerl: expression separator</a></h2>
<p class="date">
<span class="day">01</span>
<span class="month">Mar</span>
</p>
</header>
<p>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, {',', TokenLine}}.
Then we need to change the following lines in the parser:
exprs -> expr : ['$1'].
exprs -> expr exprs : ['$1' | '$2'].
And add a comma between the expressions on the second line:</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/xerl-0.4-expression-separator/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/erlang-scalability/">Erlang Scalability</a></h2>
<p class="date">
<span class="day">18</span>
<span class="month">Feb</span>
</p>
</header>
<p>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’t be explained.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/erlang-scalability/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/xerl-0.3-atomic-expressions/">Xerl: atomic expressions</a></h2>
<p class="date">
<span class="day">18</span>
<span class="month">Feb</span>
</p>
</header>
<p>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’t have the means to run code at runtime yet. This will of
course result in no module being compiled, but that’s OK, it will
allow us to discuss a few important things we’ll have to plan for
later on.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/xerl-0.3-atomic-expressions/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/xerl-0.2-two-modules/">Xerl: two modules</a></h2>
<p class="date">
<span class="day">03</span>
<span class="month">Feb</span>
</p>
</header>
<p>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’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’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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/xerl-0.2-two-modules/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/xerl-0.1-empty-modules/">Xerl: empty modules</a></h2>
<p class="date">
<span class="day">30</span>
<span class="month">Jan</span>
</p>
</header>
<p>Let’s build a programming language. I call it Xerl: eXtended ERLang.
It’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’s no go ahead of ourselves here. We’ll
begin with writing the code allowing us to compile an empty module.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/xerl-0.1-empty-modules/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/ranch-ftp/">Build an FTP Server with Ranch in 30 Minutes</a></h2>
<p class="date">
<span class="day">14</span>
<span class="month">Nov</span>
</p>
</header>
<p>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.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/ranch-ftp/">Read More</a>
</p>
</article>
<article class="blog_item">
<header>
<h2><a href="https://ninenines.eu/articles/tictactoe/">Erlang Tic Tac Toe</a></h2>
<p class="date">
<span class="day">17</span>
<span class="month">Oct</span>
</p>
</header>
<p>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’s
easily tested, considering there’s only 8 possible winning rows (3 horizontal,
3 vertical and 2 diagonal).
In Erlang though, you probably wouldn’t want an algorithm.</p>
<p style="text-align:right">
<a class="read_more" href="https://ninenines.eu/articles/tictactoe/">Read More</a>
</p>
</article>
</div>
</div>
</div>
</div>
<footer>
<div class="container">
<div class="row">
<div class="span6">
<p id="scroll-top"><a href="#">↑ Scroll to top</a></p>
<nav>
<ul>
<li><a href="mailto:[email protected]" title="Contact us">Contact us</a></li><li><a href="https://github.com/ninenines/ninenines.github.io" title="Github repository">Contribute to this site</a></li>
</ul>
</nav>
</div>
<div class="span6 credits">
<p><img src="/img/footer_logo.png"></p>
<p>Copyright © Loïc Hoguin 2012-2016</p>
</div>
</div>
</div>
</footer>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
<script src="/js/bootstrap-carousel.js"></script>
<script src="/js/bootstrap-dropdown.js"></script>
<script src="/js/custom.js"></script>
</body>
</html>
|
