diff options
38 files changed, 2015 insertions, 397 deletions
diff --git a/_build/content/articles/the-elephant-in-the-room.asciidoc b/_build/content/articles/the-elephant-in-the-room.asciidoc new file mode 100644 index 00000000..24aa0006 --- /dev/null +++ b/_build/content/articles/the-elephant-in-the-room.asciidoc @@ -0,0 +1,148 @@ ++++ +date = "2017-03-26T00:00:00+01:00" +title = "The elephant in the room" + ++++ + +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. It's +unlike anything they have ever used before. And they will +most likely end up not using it. + +What about people who already know what the syntax looks +like? As soon as you mention Erlang, the topic of the syntax +comes in. It's like nothing else matters. + +Perhaps the topic of syntax didn't come up. But they're +still not going to try Erlang because of it. + +You're probably not having these kinds of interactions at +Erlang conferences. This doesn't happen with people who are +already somewhat interested in, or need, the features that +Erlang provides. With them the syntax is at worst a minor +inconvenience. + +This happens because most developers are familiar with +syntaxes that look nothing like Erlang. To be clear, I +include language features and other concepts like objects +as part of "syntax" here. Familiarity is a very important +factor to drive adoption. + +You can see an example of that in the Elixir world, where +the majority of people come from Ruby or already knew and +liked Ruby. The 2016 survey tells us that 59% of Elixir +developers were using Ruby primarily before. That's in +large part because of the syntax. They will deny it of +course and find other reasons. And yet, we don't see such +a strong adoption of Erlang from Ruby developers, before +or after Elixir appeared. + +Side note: have you ever wondered why the Elixir community +is, I quote, much friendlier than the Ruby community? +Despite having much of the same people? + +Before we continue, let me be clear. I love the Erlang +syntax. It is simple and explicit. It is powerful, especially +when dealing with binary data. It has very few quirks. +It has little to no ambiguity. It's great. Except for +persuading people to use it. + +Over the years I have been writing Erlang, I have seen +very few people point out that the syntax slows down +adoption. We have no problem with it, so why would others? +At the same time, people coming to Erlang come to solve +a real problem they're having, so the syntax is fairly +secondary. Even if they hate it at first, they know they +can solve their problems despite the syntax. + +You don't build a popular product or language by solving +people's problems though. In general you end up solving +some problems and creating new problems. No, you build +a popular product by *convincing people to use it*. And +you make them stay with your product by making them +*commit* to using it. + +Take MongoDB for example. It didn't become popular by +working, or even by being practical. It wasn't performing +its primary function and was losing people's data. That +didn't stop it from becoming popular. Smart people would +knowingly use a database that was losing data. Think about +that for a minute. + +MongoDB of course had a huge marketing machine, and they +focused on that. They helped organize many meetups all +over the world, complete with various swag items given +for free, including a small handbook about MongoDB. All +people had to do was show up. + +They didn't go tell people to look at all the weaknesses +their product had. They focused on the strengths. On +what would convince people to try it. People would go +to meetups, discuss with people, commit to try it (or +try it at meetups directly), and by doing so sell MongoDB +to themselves. + +How do we get people to meetups though? That'd be the +first step: you need to *catch people's attention*. +I believe MongoDB did this using benchmark results. +Ironic isn't it? MongoDB gets fast benchmark results +because they lose data, and this gets everyone to buy +into the product. + +The key points to remember about this are: + +* catch people's attention +* show your product's strengths +* make people take a commitment + +Once they commit to something, you win. Everyone will not +end up ultimately using your product of course, but it's +at the very least become a consideration. It's on their +mind. Their resolve will be stronger when they ultimately +try it and inevitably run into issues. + +Erlang's syntax is a weakness. Almost nobody looks at the +Erlang syntax and falls in love with it at first sight. +No, it takes time to learn it and understand how good it +is. You need to sell Erlang to people without showing +the Erlang syntax. If you do show it, then you need to +hide the parts that feel alien. Function calls are OK. +Recursion, not so much. Maps are OK. Records, not. + +Avoiding code is not always possible when you try +to sell it, especially to developers. You can however +prepare them to accept the alien syntax by admitting +that the syntax is not perfect before you show it. +You can do this while praising it at the same time. +For example, "the syntax is a little out there, but +it matches the concepts perfectly, it will all make +sense when you start learning". + +This might not be the best introduction. Someone will +need to A/B test it to find the one that gives the +best results. But that should give you ideas. + +When something terrible happens, mentioning that this +isn't the end of the world *before* you tell others what +happened will soften their reaction. When someone +breaks your favorite item and cries over it calling +themselves stupid, it's harder to get mad at them, +compared to the same event with no emotional reaction. + +Our behavior is largely dependent on what's at the +top of our mind, so it's up to you to take advantage +of this to make your case in the best conditions. + +Next time you try to make someone use Erlang, remember +that you should aim for getting a spoken commitment +out of them, if possible before you show the syntax. +If that's not possible, then prepare them to accept +the flaws or the weirdness before they see them. diff --git a/articles/cowboy-2.0.0-pre.4/index.html b/articles/cowboy-2.0.0-pre.4/index.html index 3ce369fb..0d1f82c2 100644 --- a/articles/cowboy-2.0.0-pre.4/index.html +++ b/articles/cowboy-2.0.0-pre.4/index.html @@ -194,6 +194,8 @@ added back.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/cowboy2-qs/index.html b/articles/cowboy2-qs/index.html index 42343c77..bbbfadfd 100644 --- a/articles/cowboy2-qs/index.html +++ b/articles/cowboy2-qs/index.html @@ -233,6 +233,8 @@ thoughts that went into this rather than just the conclusion.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/dont-let-it-crash/index.html b/articles/dont-let-it-crash/index.html index 9fe54196..d6a080a9 100644 --- a/articles/dont-let-it-crash/index.html +++ b/articles/dont-let-it-crash/index.html @@ -196,6 +196,8 @@ make more.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/erlang-scalability/index.html b/articles/erlang-scalability/index.html index 04a4c42f..85a5d99b 100644 --- a/articles/erlang-scalability/index.html +++ b/articles/erlang-scalability/index.html @@ -218,6 +218,8 @@ concurrently.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/erlang-validate-utf8/index.html b/articles/erlang-validate-utf8/index.html index cc0068ce..b4af0379 100644 --- a/articles/erlang-validate-utf8/index.html +++ b/articles/erlang-validate-utf8/index.html @@ -269,6 +269,8 @@ http://www.gnu.org/software/src-highlite --> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/erlang.mk-and-relx/index.html b/articles/erlang.mk-and-relx/index.html index 0a966c02..afb63234 100644 --- a/articles/erlang.mk-and-relx/index.html +++ b/articles/erlang.mk-and-relx/index.html @@ -172,6 +172,8 @@ containing all the flags to pass to the Erlang VM, for example <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/erlanger-playbook-september-2015-update/index.html b/articles/erlanger-playbook-september-2015-update/index.html index 0b8026b9..bb4977c8 100644 --- a/articles/erlanger-playbook-september-2015-update/index.html +++ b/articles/erlanger-playbook-september-2015-update/index.html @@ -97,6 +97,8 @@ will be used to allow me to work on open source full time.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/erlanger-playbook/index.html b/articles/erlanger-playbook/index.html index 4ec81c34..20b39b17 100644 --- a/articles/erlanger-playbook/index.html +++ b/articles/erlanger-playbook/index.html @@ -150,6 +150,8 @@ You will receive updates to the book for free as soon as they are available.</p> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/farwest-funded/index.html b/articles/farwest-funded/index.html index a3ec6011..3c568bab 100644 --- a/articles/farwest-funded/index.html +++ b/articles/farwest-funded/index.html @@ -105,6 +105,8 @@ can help!</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/index.html b/articles/index.html index 9e473f54..4c5946f4 100644 --- a/articles/index.html +++ b/articles/index.html @@ -74,6 +74,23 @@ <article class="blog_item"> <header> + <h2><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></h2> + <p class="date"> + <span class="day">26</span> + <span class="month">Mar</span> + </p> + </header> + + <p>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.</p> + + <p style="text-align:right"> + <a class="read_more" href="https://ninenines.eu/articles/the-elephant-in-the-room/">Read More</a> + </p> + </article> + + <article class="blog_item"> + <header> <h2><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></h2> <p class="date"> <span class="day">22</span> @@ -414,24 +431,6 @@ </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> - <nav class="pagination" role="pagination"> diff --git a/articles/index.xml b/articles/index.xml index dbb9bb8f..70dc98a5 100644 --- a/articles/index.xml +++ b/articles/index.xml @@ -6,10 +6,152 @@ <description>Recent content in Articles-rsses on Nine Nines</description> <generator>Hugo -- gohugo.io</generator> <language>en-us</language> - <lastBuildDate>Sun, 22 Jan 2017 00:00:00 +0100</lastBuildDate> + <lastBuildDate>Sun, 26 Mar 2017 00:00:00 +0100</lastBuildDate> <atom:link href="https://ninenines.eu/articles/index.xml" rel="self" type="application/rss+xml" /> <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><div class="paragraph"><p>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.</p></div>
+<div class="paragraph"><p>You lost them. You know you lost them. They comment on the
+syntax, or perhaps you do, already admitting defeat. It&#8217;s
+unlike anything they have ever used before. And they will
+most likely end up not using it.</p></div>
+<div class="paragraph"><p>What about people who already know what the syntax looks
+like? As soon as you mention Erlang, the topic of the syntax
+comes in. It&#8217;s like nothing else matters.</p></div>
+<div class="paragraph"><p>Perhaps the topic of syntax didn&#8217;t come up. But they&#8217;re
+still not going to try Erlang because of it.</p></div>
+<div class="paragraph"><p>You&#8217;re probably not having these kinds of interactions at
+Erlang conferences. This doesn&#8217;t happen with people who are
+already somewhat interested in, or need, the features that
+Erlang provides. With them the syntax is at worst a minor
+inconvenience.</p></div>
+<div class="paragraph"><p>This happens because most developers are familiar with
+syntaxes that look nothing like Erlang. To be clear, I
+include language features and other concepts like objects
+as part of "syntax" here. Familiarity is a very important
+factor to drive adoption.</p></div>
+<div class="paragraph"><p>You can see an example of that in the Elixir world, where
+the majority of people come from Ruby or already knew and
+liked Ruby. The 2016 survey tells us that 59% of Elixir
+developers were using Ruby primarily before. That&#8217;s in
+large part because of the syntax. They will deny it of
+course and find other reasons. And yet, we don&#8217;t see such
+a strong adoption of Erlang from Ruby developers, before
+or after Elixir appeared.</p></div>
+<div class="paragraph"><p>Side note: have you ever wondered why the Elixir community
+is, I quote, much friendlier than the Ruby community?
+Despite having much of the same people?</p></div>
+<div class="paragraph"><p>Before we continue, let me be clear. I love the Erlang
+syntax. It is simple and explicit. It is powerful, especially
+when dealing with binary data. It has very few quirks.
+It has little to no ambiguity. It&#8217;s great. Except for
+persuading people to use it.</p></div>
+<div class="paragraph"><p>Over the years I have been writing Erlang, I have seen
+very few people point out that the syntax slows down
+adoption. We have no problem with it, so why would others?
+At the same time, people coming to Erlang come to solve
+a real problem they&#8217;re having, so the syntax is fairly
+secondary. Even if they hate it at first, they know they
+can solve their problems despite the syntax.</p></div>
+<div class="paragraph"><p>You don&#8217;t build a popular product or language by solving
+people&#8217;s problems though. In general you end up solving
+some problems and creating new problems. No, you build
+a popular product by <strong>convincing people to use it</strong>. And
+you make them stay with your product by making them
+<strong>commit</strong> to using it.</p></div>
+<div class="paragraph"><p>Take MongoDB for example. It didn&#8217;t become popular by
+working, or even by being practical. It wasn&#8217;t performing
+its primary function and was losing people&#8217;s data. That
+didn&#8217;t stop it from becoming popular. Smart people would
+knowingly use a database that was losing data. Think about
+that for a minute.</p></div>
+<div class="paragraph"><p>MongoDB of course had a huge marketing machine, and they
+focused on that. They helped organize many meetups all
+over the world, complete with various swag items given
+for free, including a small handbook about MongoDB. All
+people had to do was show up.</p></div>
+<div class="paragraph"><p>They didn&#8217;t go tell people to look at all the weaknesses
+their product had. They focused on the strengths. On
+what would convince people to try it. People would go
+to meetups, discuss with people, commit to try it (or
+try it at meetups directly), and by doing so sell MongoDB
+to themselves.</p></div>
+<div class="paragraph"><p>How do we get people to meetups though? That&#8217;d be the
+first step: you need to <strong>catch people&#8217;s attention</strong>.
+I believe MongoDB did this using benchmark results.
+Ironic isn&#8217;t it? MongoDB gets fast benchmark results
+because they lose data, and this gets everyone to buy
+into the product.</p></div>
+<div class="paragraph"><p>The key points to remember about this are:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+catch people&#8217;s attention
+</p>
+</li>
+<li>
+<p>
+show your product&#8217;s strengths
+</p>
+</li>
+<li>
+<p>
+make people take a commitment
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Once they commit to something, you win. Everyone will not
+end up ultimately using your product of course, but it&#8217;s
+at the very least become a consideration. It&#8217;s on their
+mind. Their resolve will be stronger when they ultimately
+try it and inevitably run into issues.</p></div>
+<div class="paragraph"><p>Erlang&#8217;s syntax is a weakness. Almost nobody looks at the
+Erlang syntax and falls in love with it at first sight.
+No, it takes time to learn it and understand how good it
+is. You need to sell Erlang to people without showing
+the Erlang syntax. If you do show it, then you need to
+hide the parts that feel alien. Function calls are OK.
+Recursion, not so much. Maps are OK. Records, not.</p></div>
+<div class="paragraph"><p>Avoiding code is not always possible when you try
+to sell it, especially to developers. You can however
+prepare them to accept the alien syntax by admitting
+that the syntax is not perfect before you show it.
+You can do this while praising it at the same time.
+For example, "the syntax is a little out there, but
+it matches the concepts perfectly, it will all make
+sense when you start learning".</p></div>
+<div class="paragraph"><p>This might not be the best introduction. Someone will
+need to A/B test it to find the one that gives the
+best results. But that should give you ideas.</p></div>
+<div class="paragraph"><p>When something terrible happens, mentioning that this
+isn&#8217;t the end of the world <strong>before</strong> you tell others what
+happened will soften their reaction. When someone
+breaks your favorite item and cries over it calling
+themselves stupid, it&#8217;s harder to get mad at them,
+compared to the same event with no emotional reaction.</p></div>
+<div class="paragraph"><p>Our behavior is largely dependent on what&#8217;s at the
+top of our mind, so it&#8217;s up to you to take advantage
+of this to make your case in the best conditions.</p></div>
+<div class="paragraph"><p>Next time you try to make someone use Erlang, remember
+that you should aim for getting a spoken commitment
+out of them, if possible before you show the syntax.
+If that&#8217;s not possible, then prepare them to accept
+the flaws or the weirdness before they see them.</p></div>
+</description> + </item> + + <item> <title>Don'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> @@ -1509,144 +1651,5 @@ containing all the flags to pass to the Erlang VM, for example </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><div class="paragraph"><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&#8217;s body, replacing our interpreter.</p></div>
-<div class="paragraph"><p>This is what we want to have when all the work is done:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>xerl -&gt; tokens -&gt; AST -&gt; intermediate -&gt; cerl</code></pre>
-</div></div>
-<div class="paragraph"><p>Today we will perform this work only on the atomic integer
-expression however, so we will not build any module at the end.
-We have a few more things to take care of before getting there.
-This does mean that we completely break compilation of modules
-though, so hopefully we can resolve that soon.</p></div>
-<div class="paragraph"><p>This intermediate representation is in the form of a module
-which contains a single function: <code>run/0</code>. This function
-contains all the expressions from our Xerl source file.</p></div>
-<div class="paragraph"><p>In the case of a Xerl source file only containing the integer
-<code>42</code>, we will obtain the following module ready to
-be executed:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #000080">-module</span></span>(<span style="color: #FF6600">'$xerl_intermediate'</span>)<span style="color: #990000">.</span>
-<span style="font-weight: bold"><span style="color: #000080">-export</span></span>([<span style="font-weight: bold"><span style="color: #000000">run</span></span><span style="color: #990000">/</span><span style="color: #993399">0</span>])<span style="color: #990000">.</span>
-
-<span style="font-weight: bold"><span style="color: #000000">run</span></span>() <span style="color: #990000">-&gt;</span>
- <span style="color: #993399">42</span><span style="color: #990000">.</span></tt></pre></div></div>
-<div class="paragraph"><p>Running it will of course give us a result of <code>42</code>,
-the same we had when interpreting expressions.</p></div>
-<div class="paragraph"><p>The resulting Core Erlang code looks like this:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="color: #FF6600">module</span> <span style="color: #FF6600">'$xerl_intermediate'</span> [<span style="color: #FF6600">'run'</span><span style="color: #990000">/</span><span style="color: #993399">0</span>]
- <span style="color: #FF6600">attributes</span> []
-<span style="color: #FF6600">'run'</span><span style="color: #990000">/</span><span style="color: #993399">0</span> <span style="color: #990000">=</span>
- <span style="font-weight: bold"><span style="color: #0000FF">fun</span></span> () <span style="color: #990000">-&gt;</span>
- <span style="color: #993399">42</span>
-<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>
-<div class="paragraph"><p>The nice thing about doing it like this is that other than the
-definition of the intermediate module and its <code>run/0</code>
-function, we can use the same code we are using for generating
-the final Beam file. It may also be faster than interpreting
-if you have complex modules.</p></div>
-<div class="paragraph"><p>Of course this here only works for the simplest cases, as you
-cannot declare a module or a function inside another Erlang function.
-We will need to wrap these into function calls to the Xerl compiler
-that will take care of compiling them, making them available for
-any subsequent expression. We will also need to pass the environment
-to the <code>run</code> function to keep track of all this.</p></div>
-<div class="paragraph"><p>This does mean that we will have different code for compiling
-<code>fun</code> and <code>mod</code> expressions when creating
-the intermediate module. But the many other expressions don&#8217;t need
-any special care.</p></div>
-<div class="paragraph"><p>Right now we&#8217;ve used the <code>'$xerl_intermediate'</code> atom
-for the intermediate module name because we only have one, but we
-will need to have a more random name later on when we&#8217;ll implement
-modules this way.</p></div>
-<div class="paragraph"><p>The attentive mind will know by now that when compiling a Xerl
-file containing one module, we will need to compile two intermediate
-modules: one for the file body, and one for the module&#8217;s body. Worry
-not though, if we only detect <code>mod</code> instructions in the file
-body, we can just skip this phase.</p></div>
-<div class="paragraph"><p>While we&#8217;re at it, we&#8217;ll modify our code generator to handle lists
-of expressions, which didn&#8217;t actually work with integer literals
-before.</p></div>
-<div class="paragraph"><p>We&#8217;re going to use Core Erlang sequences for running the many
-expressions. Sequences work like <code>let</code>, except no value
-is actually bound. Perfect for our case, since we don&#8217;t support
-binding values at this time anyway.</p></div>
-<div class="paragraph"><p>Sequences have an argument and a body, both being Core Erlang
-expressions. The simplest way to have many expressions is to use
-a simple expression for the argument and a sequence for the rest
-of the expressions. When we encounter the last expression in the
-list, we do not create a sequence.</p></div>
-<div class="paragraph"><p>The result is this very simple function:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #000000">comp_body</span></span>([<span style="color: #009900">Expr</span>]) <span style="color: #990000">-&gt;</span>
- <span style="font-weight: bold"><span style="color: #000000">expr</span></span>(<span style="color: #009900">Expr</span>);
-<span style="font-weight: bold"><span style="color: #000000">comp_body</span></span>([<span style="color: #009900">Expr</span>|<span style="color: #009900">Exprs</span>]) <span style="color: #990000">-&gt;</span>
- <span style="color: #009900">Arg</span> <span style="color: #990000">=</span> <span style="font-weight: bold"><span style="color: #000000">expr</span></span>(<span style="color: #009900">Expr</span>),
- <span style="color: #009900">Body</span> <span style="color: #990000">=</span> <span style="font-weight: bold"><span style="color: #000000">comp_body</span></span>(<span style="color: #009900">Exprs</span>),
- <span style="font-weight: bold"><span style="color: #000000">cerl:c_seq</span></span>(<span style="color: #009900">Arg</span>, <span style="color: #009900">Body</span>)<span style="color: #990000">.</span></tt></pre></div></div>
-<div class="paragraph"><p>In the case of our example above, a sequence will not be created,
-we only have one expression. If we were to have <code>42, 43, 44</code>
-in our Xerl source file, we would have a result equivalent to the
-following before optimization:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #000080">-module</span></span>(<span style="color: #FF6600">'$xerl_intermediate'</span>)<span style="color: #990000">.</span>
-<span style="font-weight: bold"><span style="color: #000080">-export</span></span>([<span style="font-weight: bold"><span style="color: #000000">run</span></span><span style="color: #990000">/</span><span style="color: #993399">0</span>])<span style="color: #990000">.</span>
-
-<span style="font-weight: bold"><span style="color: #000000">run</span></span>() <span style="color: #990000">-&gt;</span>
- <span style="color: #993399">42</span>,
- <span style="color: #993399">43</span>,
- <span style="color: #993399">44</span><span style="color: #990000">.</span></tt></pre></div></div>
-<div class="paragraph"><p>And the result is of course <code>44</code>.</p></div>
-<div class="paragraph"><p>The resulting Core Erlang code looks like this:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight 3.1.8
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="color: #FF6600">module</span> <span style="color: #FF6600">'$xerl_intermediate'</span> [<span style="color: #FF6600">'run'</span><span style="color: #990000">/</span><span style="color: #993399">0</span>]
- <span style="color: #FF6600">attributes</span> []
-<span style="color: #FF6600">'run'</span><span style="color: #990000">/</span><span style="color: #993399">0</span> <span style="color: #990000">=</span>
- <span style="font-weight: bold"><span style="color: #0000FF">fun</span></span> () <span style="color: #990000">-&gt;</span>
- <span style="color: #FF6600">do</span> <span style="color: #993399">42</span>
- <span style="color: #FF6600">do</span> <span style="color: #993399">43</span>
- <span style="color: #993399">44</span>
-<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>
-<div class="paragraph"><p>Feels very lisp-y, right? Yep.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="https://github.com/extend/xerl/blob/0.5/">View the source</a>
-</p>
-</li>
-</ul></div>
-</description> - </item> - </channel> </rss>
\ No newline at end of file diff --git a/articles/january-2014-status/index.html b/articles/january-2014-status/index.html index da0a5b8d..5b106f0e 100644 --- a/articles/january-2014-status/index.html +++ b/articles/january-2014-status/index.html @@ -224,6 +224,8 @@ the sponsoring idea, anything really! Thanks.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/ml-archives/index.html b/articles/ml-archives/index.html index 6284b2d5..f8f61510 100644 --- a/articles/ml-archives/index.html +++ b/articles/ml-archives/index.html @@ -94,6 +94,8 @@ underlying problem in the project or its documentation.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/on-open-source/index.html b/articles/on-open-source/index.html index a21b30eb..3c237369 100644 --- a/articles/on-open-source/index.html +++ b/articles/on-open-source/index.html @@ -201,6 +201,8 @@ of your company’s money.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/page/2/index.html b/articles/page/2/index.html index b7448109..12b7cefb 100644 --- a/articles/page/2/index.html +++ b/articles/page/2/index.html @@ -74,6 +74,24 @@ <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> diff --git a/articles/ranch-1.3/index.html b/articles/ranch-1.3/index.html index 8e182a0e..1636fdd5 100644 --- a/articles/ranch-1.3/index.html +++ b/articles/ranch-1.3/index.html @@ -166,6 +166,8 @@ that need fixing sooner rather than later.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/ranch-ftp/index.html b/articles/ranch-ftp/index.html index f20cefcc..0ce49201 100644 --- a/articles/ranch-ftp/index.html +++ b/articles/ranch-ftp/index.html @@ -294,6 +294,8 @@ binary protocol implementations in just a few lines of code.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/the-elephant-in-the-room/index.html b/articles/the-elephant-in-the-room/index.html new file mode 100644 index 00000000..53db28e8 --- /dev/null +++ b/articles/the-elephant-in-the-room/index.html @@ -0,0 +1,304 @@ +<!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: The elephant in the room</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"> + + +</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"> +<div class="container"> +<div class="row"> +<div class="span9 maincol"> + +<article class="blog_item"> +<header> + <h1 class="lined-header"><span>The elephant in the room</span></h1> + <p class="date"> + <span class="day">26</span> + <span class="month">Mar</span> + </p> +</header> + +<div class="paragraph"><p>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.</p></div>
+<div class="paragraph"><p>You lost them. You know you lost them. They comment on the
+syntax, or perhaps you do, already admitting defeat. It’s
+unlike anything they have ever used before. And they will
+most likely end up not using it.</p></div>
+<div class="paragraph"><p>What about people who already know what the syntax looks
+like? As soon as you mention Erlang, the topic of the syntax
+comes in. It’s like nothing else matters.</p></div>
+<div class="paragraph"><p>Perhaps the topic of syntax didn’t come up. But they’re
+still not going to try Erlang because of it.</p></div>
+<div class="paragraph"><p>You’re probably not having these kinds of interactions at
+Erlang conferences. This doesn’t happen with people who are
+already somewhat interested in, or need, the features that
+Erlang provides. With them the syntax is at worst a minor
+inconvenience.</p></div>
+<div class="paragraph"><p>This happens because most developers are familiar with
+syntaxes that look nothing like Erlang. To be clear, I
+include language features and other concepts like objects
+as part of "syntax" here. Familiarity is a very important
+factor to drive adoption.</p></div>
+<div class="paragraph"><p>You can see an example of that in the Elixir world, where
+the majority of people come from Ruby or already knew and
+liked Ruby. The 2016 survey tells us that 59% of Elixir
+developers were using Ruby primarily before. That’s in
+large part because of the syntax. They will deny it of
+course and find other reasons. And yet, we don’t see such
+a strong adoption of Erlang from Ruby developers, before
+or after Elixir appeared.</p></div>
+<div class="paragraph"><p>Side note: have you ever wondered why the Elixir community
+is, I quote, much friendlier than the Ruby community?
+Despite having much of the same people?</p></div>
+<div class="paragraph"><p>Before we continue, let me be clear. I love the Erlang
+syntax. It is simple and explicit. It is powerful, especially
+when dealing with binary data. It has very few quirks.
+It has little to no ambiguity. It’s great. Except for
+persuading people to use it.</p></div>
+<div class="paragraph"><p>Over the years I have been writing Erlang, I have seen
+very few people point out that the syntax slows down
+adoption. We have no problem with it, so why would others?
+At the same time, people coming to Erlang come to solve
+a real problem they’re having, so the syntax is fairly
+secondary. Even if they hate it at first, they know they
+can solve their problems despite the syntax.</p></div>
+<div class="paragraph"><p>You don’t build a popular product or language by solving
+people’s problems though. In general you end up solving
+some problems and creating new problems. No, you build
+a popular product by <strong>convincing people to use it</strong>. And
+you make them stay with your product by making them
+<strong>commit</strong> to using it.</p></div>
+<div class="paragraph"><p>Take MongoDB for example. It didn’t become popular by
+working, or even by being practical. It wasn’t performing
+its primary function and was losing people’s data. That
+didn’t stop it from becoming popular. Smart people would
+knowingly use a database that was losing data. Think about
+that for a minute.</p></div>
+<div class="paragraph"><p>MongoDB of course had a huge marketing machine, and they
+focused on that. They helped organize many meetups all
+over the world, complete with various swag items given
+for free, including a small handbook about MongoDB. All
+people had to do was show up.</p></div>
+<div class="paragraph"><p>They didn’t go tell people to look at all the weaknesses
+their product had. They focused on the strengths. On
+what would convince people to try it. People would go
+to meetups, discuss with people, commit to try it (or
+try it at meetups directly), and by doing so sell MongoDB
+to themselves.</p></div>
+<div class="paragraph"><p>How do we get people to meetups though? That’d be the
+first step: you need to <strong>catch people’s attention</strong>.
+I believe MongoDB did this using benchmark results.
+Ironic isn’t it? MongoDB gets fast benchmark results
+because they lose data, and this gets everyone to buy
+into the product.</p></div>
+<div class="paragraph"><p>The key points to remember about this are:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+catch people’s attention
+</p>
+</li>
+<li>
+<p>
+show your product’s strengths
+</p>
+</li>
+<li>
+<p>
+make people take a commitment
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Once they commit to something, you win. Everyone will not
+end up ultimately using your product of course, but it’s
+at the very least become a consideration. It’s on their
+mind. Their resolve will be stronger when they ultimately
+try it and inevitably run into issues.</p></div>
+<div class="paragraph"><p>Erlang’s syntax is a weakness. Almost nobody looks at the
+Erlang syntax and falls in love with it at first sight.
+No, it takes time to learn it and understand how good it
+is. You need to sell Erlang to people without showing
+the Erlang syntax. If you do show it, then you need to
+hide the parts that feel alien. Function calls are OK.
+Recursion, not so much. Maps are OK. Records, not.</p></div>
+<div class="paragraph"><p>Avoiding code is not always possible when you try
+to sell it, especially to developers. You can however
+prepare them to accept the alien syntax by admitting
+that the syntax is not perfect before you show it.
+You can do this while praising it at the same time.
+For example, "the syntax is a little out there, but
+it matches the concepts perfectly, it will all make
+sense when you start learning".</p></div>
+<div class="paragraph"><p>This might not be the best introduction. Someone will
+need to A/B test it to find the one that gives the
+best results. But that should give you ideas.</p></div>
+<div class="paragraph"><p>When something terrible happens, mentioning that this
+isn’t the end of the world <strong>before</strong> you tell others what
+happened will soften their reaction. When someone
+breaks your favorite item and cries over it calling
+themselves stupid, it’s harder to get mad at them,
+compared to the same event with no emotional reaction.</p></div>
+<div class="paragraph"><p>Our behavior is largely dependent on what’s at the
+top of our mind, so it’s up to you to take advantage
+of this to make your case in the best conditions.</p></div>
+<div class="paragraph"><p>Next time you try to make someone use Erlang, remember
+that you should aim for getting a spoken commitment
+out of them, if possible before you show the syntax.
+If that’s not possible, then prepare them to accept
+the flaws or the weirdness before they see them.</p></div>
+ +</article> +</div> + +<div class="span3 sidecol"> +<h3>More articles</h3> +<ul id="articles-nav" class="extra_margin"> + + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> + + <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> + + <li><a href="https://ninenines.eu/articles/ranch-1.3/">Ranch 1.3</a></li> + + <li><a href="https://ninenines.eu/articles/ml-archives/">Mailing list archived</a></li> + + <li><a href="https://ninenines.eu/articles/website-update/">Website update</a></li> + + <li><a href="https://ninenines.eu/articles/erlanger-playbook-september-2015-update/">The Erlanger Playbook September 2015 Update</a></li> + + <li><a href="https://ninenines.eu/articles/erlanger-playbook/">The Erlanger Playbook</a></li> + + <li><a href="https://ninenines.eu/articles/erlang-validate-utf8/">Validating UTF-8 binaries with Erlang</a></li> + + <li><a href="https://ninenines.eu/articles/on-open-source/">On open source</a></li> + + <li><a href="https://ninenines.eu/articles/the-story-so-far/">The story so far</a></li> + + <li><a href="https://ninenines.eu/articles/cowboy2-qs/">Cowboy 2.0 and query strings</a></li> + + <li><a href="https://ninenines.eu/articles/january-2014-status/">January 2014 status</a></li> + + <li><a href="https://ninenines.eu/articles/farwest-funded/">Farwest got funded!</a></li> + + <li><a href="https://ninenines.eu/articles/erlang.mk-and-relx/">Build Erlang releases with Erlang.mk and Relx</a></li> + + <li><a href="https://ninenines.eu/articles/xerl-0.5-intermediate-module/">Xerl: intermediate module</a></li> + + <li><a href="https://ninenines.eu/articles/xerl-0.4-expression-separator/">Xerl: expression separator</a></li> + + <li><a href="https://ninenines.eu/articles/erlang-scalability/">Erlang Scalability</a></li> + + <li><a href="https://ninenines.eu/articles/xerl-0.3-atomic-expressions/">Xerl: atomic expressions</a></li> + + <li><a href="https://ninenines.eu/articles/xerl-0.2-two-modules/">Xerl: two modules</a></li> + + <li><a href="https://ninenines.eu/articles/xerl-0.1-empty-modules/">Xerl: empty modules</a></li> + + <li><a href="https://ninenines.eu/articles/ranch-ftp/">Build an FTP Server with Ranch in 30 Minutes</a></li> + + <li><a href="https://ninenines.eu/articles/tictactoe/">Erlang Tic Tac Toe</a></li> + +</ul> + +<h3>Feedback</h3> +<p>Feel free to <a href="mailto:[email protected]">email us</a> +if you found any mistake or need clarification on any of the +articles.</p> + +</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> + diff --git a/articles/the-story-so-far/index.html b/articles/the-story-so-far/index.html index 2e6d1db6..13b53d4b 100644 --- a/articles/the-story-so-far/index.html +++ b/articles/the-story-so-far/index.html @@ -308,6 +308,8 @@ project and make sure it doesn’t happen again.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/tictactoe/index.html b/articles/tictactoe/index.html index dfeff96b..0ed91bf5 100644 --- a/articles/tictactoe/index.html +++ b/articles/tictactoe/index.html @@ -167,6 +167,8 @@ of writing algorithms to do things.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/website-update/index.html b/articles/website-update/index.html index aa890a89..28c13f41 100644 --- a/articles/website-update/index.html +++ b/articles/website-update/index.html @@ -141,6 +141,8 @@ upgrading JS libraries.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/xerl-0.1-empty-modules/index.html b/articles/xerl-0.1-empty-modules/index.html index 1fb11ce7..4a791493 100644 --- a/articles/xerl-0.1-empty-modules/index.html +++ b/articles/xerl-0.1-empty-modules/index.html @@ -222,6 +222,8 @@ the next few articles.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/xerl-0.2-two-modules/index.html b/articles/xerl-0.2-two-modules/index.html index 9651e83a..e979fc0b 100644 --- a/articles/xerl-0.2-two-modules/index.html +++ b/articles/xerl-0.2-two-modules/index.html @@ -227,6 +227,8 @@ though, so let’s get back to it after we add more.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/xerl-0.3-atomic-expressions/index.html b/articles/xerl-0.3-atomic-expressions/index.html index 32e6fc1c..089683b6 100644 --- a/articles/xerl-0.3-atomic-expressions/index.html +++ b/articles/xerl-0.3-atomic-expressions/index.html @@ -231,6 +231,8 @@ do that.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/xerl-0.4-expression-separator/index.html b/articles/xerl-0.4-expression-separator/index.html index 039ff166..b3cde89e 100644 --- a/articles/xerl-0.4-expression-separator/index.html +++ b/articles/xerl-0.4-expression-separator/index.html @@ -136,6 +136,8 @@ expressions so I thought it was a good idea to anticipate.</p></div> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/articles/xerl-0.5-intermediate-module/index.html b/articles/xerl-0.5-intermediate-module/index.html index be22f0d4..6835c906 100644 --- a/articles/xerl-0.5-intermediate-module/index.html +++ b/articles/xerl-0.5-intermediate-module/index.html @@ -214,6 +214,8 @@ http://www.gnu.org/software/src-highlite --> <h3>More articles</h3> <ul id="articles-nav" class="extra_margin"> + <li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li> + <li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li> <li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li> diff --git a/docs/en/cowboy/2.0/guide/architecture/index.html b/docs/en/cowboy/2.0/guide/architecture/index.html index a82159d2..acec6fe6 100644 --- a/docs/en/cowboy/2.0/guide/architecture/index.html +++ b/docs/en/cowboy/2.0/guide/architecture/index.html @@ -127,8 +127,8 @@ only processing short-lived requests.</p></div> <nav style="margin:1em 0"> - <a style="float:left" href="https://ninenines.eu/docs/en/cowboy/2.0/guide/sub_protocols/"> - Sub protocols + <a style="float:left" href="https://ninenines.eu/docs/en/cowboy/2.0/guide/specs/"> + HTTP and other specifications </a> diff --git a/docs/en/cowboy/2.0/guide/index.html b/docs/en/cowboy/2.0/guide/index.html index d79f8e50..3aed18ff 100644 --- a/docs/en/cowboy/2.0/guide/index.html +++ b/docs/en/cowboy/2.0/guide/index.html @@ -253,6 +253,18 @@ </div>
</div>
<div class="sect1">
+<h2 id="_additional_information">Additional information</h2>
+<div class="sectionbody">
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="specs/">HTTP and other specifications</a>
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_deprecated_chapters">Deprecated chapters</h2>
<div class="sectionbody">
</div>
diff --git a/docs/en/cowboy/2.0/guide/specs.asciidoc b/docs/en/cowboy/2.0/guide/specs.asciidoc new file mode 100644 index 00000000..78db4b18 --- /dev/null +++ b/docs/en/cowboy/2.0/guide/specs.asciidoc @@ -0,0 +1,182 @@ +== HTTP and other specifications + +This chapter intends to list all the specification documents +for or related to HTTP. + +=== HTTP + +==== IANA Registries + +* https://www.iana.org/assignments/http-methods/http-methods.xhtml[HTTP Method Registry] +* https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml[HTTP Status Code Registry] +* https://www.iana.org/assignments/message-headers/message-headers.xhtml[Message Headers] +* https://www.iana.org/assignments/http-parameters/http-parameters.xhtml[HTTP Parameters] +* https://www.iana.org/assignments/http-alt-svc-parameters/http-alt-svc-parameters.xhtml[HTTP Alt-Svc Parameter Registry] +* https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml[HTTP Authentication Scheme Registry] +* https://www.iana.org/assignments/http-cache-directives/http-cache-directives.xhtml[HTTP Cache Directive Registry] +* https://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml[HTTP Digest Algorithm Values] +* https://www.iana.org/assignments/hoba-device-identifiers/hoba-device-identifiers.xhtml[HTTP Origin-Bound Authentication Device Identifier Types] +* https://www.iana.org/assignments/http-upgrade-tokens/http-upgrade-tokens.xhtml[HTTP Upgrade Token Registry] +* https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml[HTTP Warn Codes] +* https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml[HTTP/2 Parameters] +* https://www.ietf.org/assignments/websocket/websocket.xml[WebSocket Protocol Registries] + +==== Current + +* http://www.w3.org/TR/cors/[CORS]: Cross-Origin Resource Sharing +* http://www.w3.org/TR/CSP2/[CSP2]: Content Security Policy Level 2 +* http://www.w3.org/TR/tracking-dnt/[DNT]: Tracking Preference Expression (DNT) +* http://www.w3.org/TR/eventsource/[eventsource]: Server-Sent Events +* https://www.w3.org/TR/html4/interact/forms.html#h-17.13.4[Form content types]: Form content types +* https://www.w3.org/TR/preload/[Preload]: Preload +* http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm[REST]: Fielding's Dissertation +* https://tools.ietf.org/html/rfc1945[RFC 1945]: HTTP/1.0 +* https://tools.ietf.org/html/rfc1951[RFC 1951]: DEFLATE Compressed Data Format Specification version 1.3 +* https://tools.ietf.org/html/rfc1952[RFC 1952]: GZIP file format specification version 4.3 +* https://tools.ietf.org/html/rfc2046#section-5.1[RFC 2046]: Multipart media type (in MIME Part Two: Media Types) +* https://tools.ietf.org/html/rfc2295[RFC 2295]: Transparent Content Negotiation in HTTP +* https://tools.ietf.org/html/rfc2296[RFC 2296]: HTTP Remote Variant Selection Algorithm: RVSA/1.0 +* https://tools.ietf.org/html/rfc2817[RFC 2817]: Upgrading to TLS Within HTTP/1.1 +* https://tools.ietf.org/html/rfc2818[RFC 2818]: HTTP Over TLS +* https://tools.ietf.org/html/rfc3230[RFC 3230]: Instance Digests in HTTP +* https://tools.ietf.org/html/rfc4559[RFC 4559]: SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows +* https://tools.ietf.org/html/rfc5789[RFC 5789]: PATCH Method for HTTP +* https://tools.ietf.org/html/rfc5843[RFC 5843]: Additional Hash Algorithms for HTTP Instance Digests +* https://tools.ietf.org/html/rfc5861[RFC 5861]: HTTP Cache-Control Extensions for Stale Content +* https://tools.ietf.org/html/rfc5987[RFC 5987]: Character Set and Language Encoding for HTTP Header Field Parameters +* https://tools.ietf.org/html/rfc5988[RFC 5988]: Web Linking +* https://tools.ietf.org/html/rfc6265[RFC 6265]: HTTP State Management Mechanism +* https://tools.ietf.org/html/rfc6266[RFC 6266]: Use of the Content-Disposition Header Field +* https://tools.ietf.org/html/rfc6454[RFC 6454]: The Web Origin Concept +* https://tools.ietf.org/html/rfc6455[RFC 6455]: The WebSocket Protocol +* https://tools.ietf.org/html/rfc6585[RFC 6585]: Additional HTTP Status Codes +* https://tools.ietf.org/html/rfc6750[RFC 6750]: The OAuth 2.0 Authorization Framework: Bearer Token Usage +* https://tools.ietf.org/html/rfc6797[RFC 6797]: HTTP Strict Transport Security (HSTS) +* https://tools.ietf.org/html/rfc6903[RFC 6903]: Additional Link Relation Types +* https://tools.ietf.org/html/rfc7034[RFC 7034]: HTTP Header Field X-Frame-Options +* https://tools.ietf.org/html/rfc7089[RFC 7089]: Time-Based Access to Resource States: Memento +* https://tools.ietf.org/html/rfc7230[RFC 7230]: HTTP/1.1 Message Syntax and Routing +* https://tools.ietf.org/html/rfc7231[RFC 7231]: HTTP/1.1 Semantics and Content +* https://tools.ietf.org/html/rfc7232[RFC 7232]: HTTP/1.1 Conditional Requests +* https://tools.ietf.org/html/rfc7233[RFC 7233]: HTTP/1.1 Range Requests +* https://tools.ietf.org/html/rfc7234[RFC 7234]: HTTP/1.1 Caching +* https://tools.ietf.org/html/rfc7235[RFC 7235]: HTTP/1.1 Authentication +* https://tools.ietf.org/html/rfc7239[RFC 7239]: Forwarded HTTP Extension +* https://tools.ietf.org/html/rfc7240[RFC 7240]: Prefer Header for HTTP +* https://tools.ietf.org/html/rfc7469[RFC 7469]: Public Key Pinning Extension for HTTP +* https://tools.ietf.org/html/rfc7486[RFC 7486]: HTTP Origin-Bound Authentication (HOBA) +* https://tools.ietf.org/html/rfc7538[RFC 7538]: HTTP Status Code 308 (Permanent Redirect) +* https://tools.ietf.org/html/rfc7540[RFC 7540]: Hypertext Transfer Protocol Version 2 (HTTP/2) +* https://tools.ietf.org/html/rfc7541[RFC 7541]: HPACK: Header Compression for HTTP/2 +* https://tools.ietf.org/html/rfc7578[RFC 7578]: Returning Values from Forms: multipart/form-data +* https://tools.ietf.org/html/rfc7615[RFC 7615]: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields +* https://tools.ietf.org/html/rfc7616[RFC 7616]: HTTP Digest Access Authentication +* https://tools.ietf.org/html/rfc7617[RFC 7617]: The 'Basic' HTTP Authentication Scheme +* https://tools.ietf.org/html/rfc7639[RFC 7639]: The ALPN HTTP Header Field +* https://tools.ietf.org/html/rfc7692[RFC 7692]: Compression Extensions for WebSocket +* https://tools.ietf.org/html/rfc7694[RFC 7694]: HTTP Client-Initiated Content-Encoding +* https://tools.ietf.org/html/rfc7725[RFC 7725]: An HTTP Status Code to Report Legal Obstacles +* https://tools.ietf.org/html/rfc7804[RFC 7804]: Salted Challenge Response HTTP Authentication Mechanism +* https://tools.ietf.org/html/rfc7838[RFC 7838]: HTTP Alternative Services +* https://tools.ietf.org/html/rfc7932[RFC 7932]: Brotli Compressed Data Format +* https://tools.ietf.org/html/rfc8053[RFC 8053]: HTTP Authentication Extensions for Interactive Clients +* https://www.w3.org/TR/webmention/[Webmention]: Webmention + +==== Upcoming + +* https://www.w3.org/TR/csp-cookies/[Content Security Policy: Cookie Controls] +* https://www.w3.org/TR/csp-embedded-enforcement/[Content Security Policy: Embedded Enforcement] +* https://www.w3.org/TR/CSP3/[Content Security Policy Level 3] +* https://www.w3.org/TR/csp-pinning/[Content Security Policy Pinning] +* http://www.w3.org/TR/referrer-policy/[Referrer Policy] +* http://www.w3.org/TR/UISecurity/[User Interface Security Directives for Content Security Policy] + +==== Informative + +* http://www.w3.org/TR/webarch/[Architecture of the World Wide Web] +* https://tools.ietf.org/html/rfc2936[RFC 2936]: HTTP MIME Type Handler Detection +* https://tools.ietf.org/html/rfc2964[RFC 2964]: Use of HTTP State Management +* https://tools.ietf.org/html/rfc3143[RFC 3143]: Known HTTP Proxy/Caching Problems +* https://tools.ietf.org/html/rfc6202[RFC 6202]: Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP +* https://tools.ietf.org/html/rfc6838[RFC 6838]: Media Type Specifications and Registration Procedures +* https://tools.ietf.org/html/rfc7478[RFC 7478]: Web Real-Time Communication Use Cases and Requirements + +==== Related + +* http://www.w3.org/TR/app-uri/[app: URL Scheme] +* http://www.w3.org/TR/beacon/[Beacon] +* http://www.w3.org/TR/FileAPI/[File API] +* https://tools.ietf.org/html/rfc8030[Generic Event Delivery Using HTTP Push] +* http://www.w3.org/TR/capability-urls/[Good Practices for Capability URLs] +* https://html.spec.whatwg.org/multipage/[HTML Living Standard] +* https://developers.whatwg.org/[HTML Living Standard for Web developers] +* http://www.w3.org/TR/html401/[HTML4.01] +* http://www.w3.org/TR/html5/[HTML5] +* http://www.w3.org/TR/html51/[HTML5.1] +* https://www.w3.org/TR/html52/[HTML5.2] +* http://www.w3.org/TR/media-frags/[Media Fragments URI 1.0] +* https://tools.ietf.org/html/rfc6690[RFC 6690]: Constrained RESTful Environments (CoRE) Link Format +* https://tools.ietf.org/html/rfc7807[RFC 7807]: Problem Details for HTTP APIs +* https://tools.ietf.org/html/rfc6906[RFC 6906]: The 'profile' Link Relation Type +* http://www.w3.org/TR/SRI/[Subresource Integrity] +* http://www.w3.org/TR/tracking-compliance/[Tracking Compliance and Scope] +* http://www.w3.org/TR/media-frags-reqs/[Use cases and requirements for Media Fragments] +* http://www.w3.org/TR/webrtc/[WebRTC 1.0: Real-time Communication Between Browsers] +* http://www.w3.org/TR/websockets/[Websocket API] +* http://www.w3.org/TR/XMLHttpRequest/[XMLHttpRequest Level 1] +* https://xhr.spec.whatwg.org/[XMLHttpRequest Living Standard] + +==== Seemingly obsolete + +* https://tools.ietf.org/html/rfc2227[RFC 2227]: Simple Hit-Metering and Usage-Limiting for HTTP +* https://tools.ietf.org/html/rfc2310[RFC 2310]: The Safe Response Header Field +* https://tools.ietf.org/html/rfc2324[RFC 2324]: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) +* https://tools.ietf.org/html/rfc2660[RFC 2660]: The Secure HyperText Transfer Protocol +* https://tools.ietf.org/html/rfc2774[RFC 2774]: An HTTP Extension Framework +* https://tools.ietf.org/html/rfc2965[RFC 2965]: HTTP State Management Mechanism (Cookie2) +* https://tools.ietf.org/html/rfc3229[RFC 3229]: Delta encoding in HTTP +* https://tools.ietf.org/html/rfc7168[RFC 7168]: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA) +* http://dev.chromium.org/spdy/spdy-protocol[SPDY]: SPDY Protocol +* https://tools.ietf.org/html/draft-tyoshino-hybi-websocket-perframe-deflate-06[x-webkit-deflate-frame]: Deprecated Websocket compression + +=== URL + +* https://tools.ietf.org/html/rfc3986[RFC 3986]: URI Generic Syntax +* https://tools.ietf.org/html/rfc6570[RFC 6570]: URI Template +* https://tools.ietf.org/html/rfc6874[RFC 6874]: Representing IPv6 Zone Identifiers in Address Literals and URIs +* https://tools.ietf.org/html/rfc7320[RFC 7320]: URI Design and Ownership +* http://www.w3.org/TR/url-1/[URL] +* https://url.spec.whatwg.org/[URL Living Standard] + +=== WebDAV + +* https://tools.ietf.org/html/rfc3253[RFC 3253]: Versioning Extensions to WebDAV +* https://tools.ietf.org/html/rfc3648[RFC 3648]: WebDAV Ordered Collections Protocol +* https://tools.ietf.org/html/rfc3744[RFC 3744]: WebDAV Access Control Protocol +* https://tools.ietf.org/html/rfc4316[RFC 4316]: Datatypes for WebDAV Properties +* https://tools.ietf.org/html/rfc4331[RFC 4331]: Quota and Size Properties for DAV Collections +* https://tools.ietf.org/html/rfc4437[RFC 4437]: WebDAV Redirect Reference Resources +* https://tools.ietf.org/html/rfc4709[RFC 4709]: Mounting WebDAV Servers +* https://tools.ietf.org/html/rfc4791[RFC 4791]: Calendaring Extensions to WebDAV (CalDAV) +* https://tools.ietf.org/html/rfc4918[RFC 4918]: HTTP Extensions for WebDAV +* https://tools.ietf.org/html/rfc5323[RFC 5323]: WebDAV SEARCH +* https://tools.ietf.org/html/rfc5397[RFC 5397]: WebDAV Current Principal Extension +* https://tools.ietf.org/html/rfc5689[RFC 5689]: Extended MKCOL for WebDAV +* https://tools.ietf.org/html/rfc5842[RFC 5842]: Binding Extensions to WebDAV +* https://tools.ietf.org/html/rfc5995[RFC 5995]: Using POST to Add Members to WebDAV Collections +* https://tools.ietf.org/html/rfc6352[RFC 6352]: CardDAV: vCard Extensions to WebDAV +* https://tools.ietf.org/html/rfc6578[RFC 6578]: Collection Synchronization for WebDAV +* https://tools.ietf.org/html/rfc6638[RFC 6638]: Scheduling Extensions to CalDAV +* https://tools.ietf.org/html/rfc6764[RFC 6764]: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV) +* https://tools.ietf.org/html/rfc7809[RFC 7809]: Calendaring Extensions to WebDAV (CalDAV): Time Zones by Reference +* https://tools.ietf.org/html/rfc7953[RFC 7953]: Calendar Availability + +=== CoAP + +* https://tools.ietf.org/html/rfc7252[RFC 7252]: The Constrained Application Protocol (CoAP) +* https://tools.ietf.org/html/rfc7390[RFC 7390]: Group Communication for CoAP +* https://tools.ietf.org/html/rfc7641[RFC 7641]: Observing Resources in CoAP +* https://tools.ietf.org/html/rfc7650[RFC 7650]: A CoAP Usage for REsource LOcation And Discovery (RELOAD) +* https://tools.ietf.org/html/rfc7959[RFC 7959]: Block-Wise Transfers in CoAP +* https://tools.ietf.org/html/rfc7967[RFC 7967]: CoAP Option for No Server Response +* https://tools.ietf.org/html/rfc8075[RFC 8075]: Guidelines for Mapping Implementations: HTTP to CoAP diff --git a/docs/en/cowboy/2.0/guide/specs/index.html b/docs/en/cowboy/2.0/guide/specs/index.html new file mode 100644 index 00000000..f7abc6b5 --- /dev/null +++ b/docs/en/cowboy/2.0/guide/specs/index.html @@ -0,0 +1,966 @@ +<!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: HTTP and other specifications</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"> + + +</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><a title="Hear my thoughts" href="/articles">Articles</a></li> + <li><a title="Watch my talks" href="/talks">Talks</a></li> + <li class="active"><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 id="docs" class="span9 maincol"> + +<h1 class="lined-header"><span>HTTP and other specifications</span></h1> + +<div class="paragraph"><p>This chapter intends to list all the specification documents
+for or related to HTTP.</p></div>
+<div class="sect1">
+<h2 id="_http">HTTP</h2>
+<div class="sectionbody">
+<div class="sect3">
+<h4 id="_iana_registries">IANA Registries</h4>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-methods/http-methods.xhtml">HTTP Method Registry</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml">HTTP Status Code Registry</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/message-headers/message-headers.xhtml">Message Headers</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-parameters/http-parameters.xhtml">HTTP Parameters</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-alt-svc-parameters/http-alt-svc-parameters.xhtml">HTTP Alt-Svc Parameter Registry</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml">HTTP Authentication Scheme Registry</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-cache-directives/http-cache-directives.xhtml">HTTP Cache Directive Registry</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml">HTTP Digest Algorithm Values</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/hoba-device-identifiers/hoba-device-identifiers.xhtml">HTTP Origin-Bound Authentication Device Identifier Types</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-upgrade-tokens/http-upgrade-tokens.xhtml">HTTP Upgrade Token Registry</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml">HTTP Warn Codes</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.iana.org/assignments/http2-parameters/http2-parameters.xhtml">HTTP/2 Parameters</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.ietf.org/assignments/websocket/websocket.xml">WebSocket Protocol Registries</a>
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect3">
+<h4 id="_current">Current</h4>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="http://www.w3.org/TR/cors/">CORS</a>: Cross-Origin Resource Sharing
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/CSP2/">CSP2</a>: Content Security Policy Level 2
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/tracking-dnt/">DNT</a>: Tracking Preference Expression (DNT)
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/eventsource/">eventsource</a>: Server-Sent Events
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/html4/interact/forms.html#h-17.13.4">Form content types</a>: Form content types
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/preload/">Preload</a>: Preload
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">REST</a>: Fielding’s Dissertation
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc1945">RFC 1945</a>: HTTP/1.0
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc1951">RFC 1951</a>: DEFLATE Compressed Data Format Specification version 1.3
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc1952">RFC 1952</a>: GZIP file format specification version 4.3
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2046#section-5.1">RFC 2046</a>: Multipart media type (in MIME Part Two: Media Types)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2295">RFC 2295</a>: Transparent Content Negotiation in HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2296">RFC 2296</a>: HTTP Remote Variant Selection Algorithm: RVSA/1.0
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2817">RFC 2817</a>: Upgrading to TLS Within HTTP/1.1
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2818">RFC 2818</a>: HTTP Over TLS
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3230">RFC 3230</a>: Instance Digests in HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4559">RFC 4559</a>: SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5789">RFC 5789</a>: PATCH Method for HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5843">RFC 5843</a>: Additional Hash Algorithms for HTTP Instance Digests
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5861">RFC 5861</a>: HTTP Cache-Control Extensions for Stale Content
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5987">RFC 5987</a>: Character Set and Language Encoding for HTTP Header Field Parameters
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5988">RFC 5988</a>: Web Linking
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6265">RFC 6265</a>: HTTP State Management Mechanism
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6266">RFC 6266</a>: Use of the Content-Disposition Header Field
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6454">RFC 6454</a>: The Web Origin Concept
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6455">RFC 6455</a>: The WebSocket Protocol
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6585">RFC 6585</a>: Additional HTTP Status Codes
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6750">RFC 6750</a>: The OAuth 2.0 Authorization Framework: Bearer Token Usage
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6797">RFC 6797</a>: HTTP Strict Transport Security (HSTS)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6903">RFC 6903</a>: Additional Link Relation Types
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7034">RFC 7034</a>: HTTP Header Field X-Frame-Options
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7089">RFC 7089</a>: Time-Based Access to Resource States: Memento
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7230">RFC 7230</a>: HTTP/1.1 Message Syntax and Routing
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7231">RFC 7231</a>: HTTP/1.1 Semantics and Content
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7232">RFC 7232</a>: HTTP/1.1 Conditional Requests
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7233">RFC 7233</a>: HTTP/1.1 Range Requests
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7234">RFC 7234</a>: HTTP/1.1 Caching
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7235">RFC 7235</a>: HTTP/1.1 Authentication
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7239">RFC 7239</a>: Forwarded HTTP Extension
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7240">RFC 7240</a>: Prefer Header for HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7469">RFC 7469</a>: Public Key Pinning Extension for HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7486">RFC 7486</a>: HTTP Origin-Bound Authentication (HOBA)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7538">RFC 7538</a>: HTTP Status Code 308 (Permanent Redirect)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7540">RFC 7540</a>: Hypertext Transfer Protocol Version 2 (HTTP/2)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7541">RFC 7541</a>: HPACK: Header Compression for HTTP/2
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7578">RFC 7578</a>: Returning Values from Forms: multipart/form-data
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7615">RFC 7615</a>: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7616">RFC 7616</a>: HTTP Digest Access Authentication
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7617">RFC 7617</a>: The <em>Basic</em> HTTP Authentication Scheme
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7639">RFC 7639</a>: The ALPN HTTP Header Field
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7692">RFC 7692</a>: Compression Extensions for WebSocket
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7694">RFC 7694</a>: HTTP Client-Initiated Content-Encoding
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7725">RFC 7725</a>: An HTTP Status Code to Report Legal Obstacles
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7804">RFC 7804</a>: Salted Challenge Response HTTP Authentication Mechanism
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7838">RFC 7838</a>: HTTP Alternative Services
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7932">RFC 7932</a>: Brotli Compressed Data Format
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc8053">RFC 8053</a>: HTTP Authentication Extensions for Interactive Clients
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/webmention/">Webmention</a>: Webmention
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect3">
+<h4 id="_upcoming">Upcoming</h4>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="https://www.w3.org/TR/csp-cookies/">Content Security Policy: Cookie Controls</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/csp-embedded-enforcement/">Content Security Policy: Embedded Enforcement</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/CSP3/">Content Security Policy Level 3</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/csp-pinning/">Content Security Policy Pinning</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/referrer-policy/">Referrer Policy</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/UISecurity/">User Interface Security Directives for Content Security Policy</a>
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect3">
+<h4 id="_informative">Informative</h4>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="http://www.w3.org/TR/webarch/">Architecture of the World Wide Web</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2936">RFC 2936</a>: HTTP MIME Type Handler Detection
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2964">RFC 2964</a>: Use of HTTP State Management
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3143">RFC 3143</a>: Known HTTP Proxy/Caching Problems
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6202">RFC 6202</a>: Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6838">RFC 6838</a>: Media Type Specifications and Registration Procedures
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7478">RFC 7478</a>: Web Real-Time Communication Use Cases and Requirements
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect3">
+<h4 id="_related">Related</h4>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="http://www.w3.org/TR/app-uri/">app: URL Scheme</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/beacon/">Beacon</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/FileAPI/">File API</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc8030">Generic Event Delivery Using HTTP Push</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/capability-urls/">Good Practices for Capability URLs</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://html.spec.whatwg.org/multipage/">HTML Living Standard</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://developers.whatwg.org/">HTML Living Standard for Web developers</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/html401/">HTML4.01</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/html5/">HTML5</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/html51/">HTML5.1</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://www.w3.org/TR/html52/">HTML5.2</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/media-frags/">Media Fragments URI 1.0</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6690">RFC 6690</a>: Constrained RESTful Environments (CoRE) Link Format
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7807">RFC 7807</a>: Problem Details for HTTP APIs
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6906">RFC 6906</a>: The <em>profile</em> Link Relation Type
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/SRI/">Subresource Integrity</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/tracking-compliance/">Tracking Compliance and Scope</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/media-frags-reqs/">Use cases and requirements for Media Fragments</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/webrtc/">WebRTC 1.0: Real-time Communication Between Browsers</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/websockets/">Websocket API</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/XMLHttpRequest/">XMLHttpRequest Level 1</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://xhr.spec.whatwg.org/">XMLHttpRequest Living Standard</a>
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect3">
+<h4 id="_seemingly_obsolete">Seemingly obsolete</h4>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2227">RFC 2227</a>: Simple Hit-Metering and Usage-Limiting for HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2310">RFC 2310</a>: The Safe Response Header Field
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2324">RFC 2324</a>: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2660">RFC 2660</a>: The Secure HyperText Transfer Protocol
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2774">RFC 2774</a>: An HTTP Extension Framework
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc2965">RFC 2965</a>: HTTP State Management Mechanism (Cookie2)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3229">RFC 3229</a>: Delta encoding in HTTP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7168">RFC 7168</a>: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
+</p>
+</li>
+<li>
+<p>
+<a href="http://dev.chromium.org/spdy/spdy-protocol">SPDY</a>: SPDY Protocol
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/draft-tyoshino-hybi-websocket-perframe-deflate-06">x-webkit-deflate-frame</a>: Deprecated Websocket compression
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_url">URL</h2>
+<div class="sectionbody">
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3986">RFC 3986</a>: URI Generic Syntax
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6570">RFC 6570</a>: URI Template
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6874">RFC 6874</a>: Representing IPv6 Zone Identifiers in Address Literals and URIs
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7320">RFC 7320</a>: URI Design and Ownership
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.w3.org/TR/url-1/">URL</a>
+</p>
+</li>
+<li>
+<p>
+<a href="https://url.spec.whatwg.org/">URL Living Standard</a>
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_webdav">WebDAV</h2>
+<div class="sectionbody">
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3253">RFC 3253</a>: Versioning Extensions to WebDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3648">RFC 3648</a>: WebDAV Ordered Collections Protocol
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc3744">RFC 3744</a>: WebDAV Access Control Protocol
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4316">RFC 4316</a>: Datatypes for WebDAV Properties
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4331">RFC 4331</a>: Quota and Size Properties for DAV Collections
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4437">RFC 4437</a>: WebDAV Redirect Reference Resources
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4709">RFC 4709</a>: Mounting WebDAV Servers
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4791">RFC 4791</a>: Calendaring Extensions to WebDAV (CalDAV)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc4918">RFC 4918</a>: HTTP Extensions for WebDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5323">RFC 5323</a>: WebDAV SEARCH
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5397">RFC 5397</a>: WebDAV Current Principal Extension
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5689">RFC 5689</a>: Extended MKCOL for WebDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5842">RFC 5842</a>: Binding Extensions to WebDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc5995">RFC 5995</a>: Using POST to Add Members to WebDAV Collections
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6352">RFC 6352</a>: CardDAV: vCard Extensions to WebDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6578">RFC 6578</a>: Collection Synchronization for WebDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6638">RFC 6638</a>: Scheduling Extensions to CalDAV
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc6764">RFC 6764</a>: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7809">RFC 7809</a>: Calendaring Extensions to WebDAV (CalDAV): Time Zones by Reference
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7953">RFC 7953</a>: Calendar Availability
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_coap">CoAP</h2>
+<div class="sectionbody">
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7252">RFC 7252</a>: The Constrained Application Protocol (CoAP)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7390">RFC 7390</a>: Group Communication for CoAP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7641">RFC 7641</a>: Observing Resources in CoAP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7650">RFC 7650</a>: A CoAP Usage for REsource LOcation And Discovery (RELOAD)
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7959">RFC 7959</a>: Block-Wise Transfers in CoAP
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc7967">RFC 7967</a>: CoAP Option for No Server Response
+</p>
+</li>
+<li>
+<p>
+<a href="https://tools.ietf.org/html/rfc8075">RFC 8075</a>: Guidelines for Mapping Implementations: HTTP to CoAP
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+ + + + + + + + <nav style="margin:1em 0"> + + <a style="float:left" href="https://ninenines.eu/docs/en/cowboy/2.0/guide/sub_protocols/"> + Sub protocols + </a> + + + + <a style="float:right" href="https://ninenines.eu/docs/en/cowboy/2.0/guide/architecture/"> + Architecture + </a> + + </nav> + + + + +</div> + +<div class="span3 sidecol"> + + +<h3> + Cowboy + 2.0 + + User Guide +</h3> + +<ul> + + <li><a href="/docs/en/cowboy/2.0/guide">User Guide</a></li> + + + <li><a href="/docs/en/cowboy/2.0/manual">Function Reference</a></li> + + +</ul> + +<h4 id="docs-nav">Navigation</h4> + +<h4>Version select</h4> +<ul> + + + + <li><a href="/docs/en/cowboy/2.0/guide">2.0</a></li> + + <li><a href="/docs/en/cowboy/1.0/guide">1.0</a></li> + +</ul> + +</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> + + diff --git a/docs/en/cowboy/2.0/guide/sub_protocols/index.html b/docs/en/cowboy/2.0/guide/sub_protocols/index.html index 0d6e1bfc..df7372a3 100644 --- a/docs/en/cowboy/2.0/guide/sub_protocols/index.html +++ b/docs/en/cowboy/2.0/guide/sub_protocols/index.html @@ -153,8 +153,8 @@ the optional <code>terminate/3</code> callback is called, if present.</p></div> - <a style="float:right" href="https://ninenines.eu/docs/en/cowboy/2.0/guide/architecture/"> - Architecture + <a style="float:right" href="https://ninenines.eu/docs/en/cowboy/2.0/guide/specs/"> + HTTP and other specifications </a> </nav> diff --git a/docs/index.xml b/docs/index.xml index edeafd2e..cb2e34ae 100644 --- a/docs/index.xml +++ b/docs/index.xml @@ -363,6 +363,18 @@ environment configuration parameters.</p></div> </div>
</div>
<div class="sect1">
+<h2 id="_additional_information">Additional information</h2>
+<div class="sectionbody">
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="specs/">HTTP and other specifications</a>
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_deprecated_chapters">Deprecated chapters</h2>
<div class="sectionbody">
</div>
diff --git a/donate/index.html b/donate/index.html index c3e254e8..f5d4ab38 100644 --- a/donate/index.html +++ b/donate/index.html @@ -107,6 +107,8 @@ and Erlang.mk is fantastic:</p></div> + + <div class="sect2">
<h3 id="_like_my_work_donate">Like my work? Donate!</h3>
<div class="paragraph"><p>Donate to Loïc Hoguin because his work on Cowboy
@@ -480,6 +482,8 @@ and Erlang.mk is fantastic:</p></div> + + </div> </div> </div> @@ -265,6 +265,8 @@ + + <div class="paragraph"><p>The Erlanger Playbook is now available!<br />
<a href="/articles/erlanger-playbook">Buy now</a> — <a href="/services">Become a Cowboy project sponsor</a></p></div>
@@ -620,6 +622,8 @@ + + </div> </div> @@ -6,10 +6,152 @@ <description>Recent content on Nine Nines</description> <generator>Hugo -- gohugo.io</generator> <language>en-us</language> - <lastBuildDate>Sun, 22 Jan 2017 00:00:00 +0100</lastBuildDate> + <lastBuildDate>Sun, 26 Mar 2017 00:00:00 +0100</lastBuildDate> <atom:link href="https://ninenines.eu/index.xml" rel="self" type="application/rss+xml" /> <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><div class="paragraph"><p>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.</p></div>
+<div class="paragraph"><p>You lost them. You know you lost them. They comment on the
+syntax, or perhaps you do, already admitting defeat. It&#8217;s
+unlike anything they have ever used before. And they will
+most likely end up not using it.</p></div>
+<div class="paragraph"><p>What about people who already know what the syntax looks
+like? As soon as you mention Erlang, the topic of the syntax
+comes in. It&#8217;s like nothing else matters.</p></div>
+<div class="paragraph"><p>Perhaps the topic of syntax didn&#8217;t come up. But they&#8217;re
+still not going to try Erlang because of it.</p></div>
+<div class="paragraph"><p>You&#8217;re probably not having these kinds of interactions at
+Erlang conferences. This doesn&#8217;t happen with people who are
+already somewhat interested in, or need, the features that
+Erlang provides. With them the syntax is at worst a minor
+inconvenience.</p></div>
+<div class="paragraph"><p>This happens because most developers are familiar with
+syntaxes that look nothing like Erlang. To be clear, I
+include language features and other concepts like objects
+as part of "syntax" here. Familiarity is a very important
+factor to drive adoption.</p></div>
+<div class="paragraph"><p>You can see an example of that in the Elixir world, where
+the majority of people come from Ruby or already knew and
+liked Ruby. The 2016 survey tells us that 59% of Elixir
+developers were using Ruby primarily before. That&#8217;s in
+large part because of the syntax. They will deny it of
+course and find other reasons. And yet, we don&#8217;t see such
+a strong adoption of Erlang from Ruby developers, before
+or after Elixir appeared.</p></div>
+<div class="paragraph"><p>Side note: have you ever wondered why the Elixir community
+is, I quote, much friendlier than the Ruby community?
+Despite having much of the same people?</p></div>
+<div class="paragraph"><p>Before we continue, let me be clear. I love the Erlang
+syntax. It is simple and explicit. It is powerful, especially
+when dealing with binary data. It has very few quirks.
+It has little to no ambiguity. It&#8217;s great. Except for
+persuading people to use it.</p></div>
+<div class="paragraph"><p>Over the years I have been writing Erlang, I have seen
+very few people point out that the syntax slows down
+adoption. We have no problem with it, so why would others?
+At the same time, people coming to Erlang come to solve
+a real problem they&#8217;re having, so the syntax is fairly
+secondary. Even if they hate it at first, they know they
+can solve their problems despite the syntax.</p></div>
+<div class="paragraph"><p>You don&#8217;t build a popular product or language by solving
+people&#8217;s problems though. In general you end up solving
+some problems and creating new problems. No, you build
+a popular product by <strong>convincing people to use it</strong>. And
+you make them stay with your product by making them
+<strong>commit</strong> to using it.</p></div>
+<div class="paragraph"><p>Take MongoDB for example. It didn&#8217;t become popular by
+working, or even by being practical. It wasn&#8217;t performing
+its primary function and was losing people&#8217;s data. That
+didn&#8217;t stop it from becoming popular. Smart people would
+knowingly use a database that was losing data. Think about
+that for a minute.</p></div>
+<div class="paragraph"><p>MongoDB of course had a huge marketing machine, and they
+focused on that. They helped organize many meetups all
+over the world, complete with various swag items given
+for free, including a small handbook about MongoDB. All
+people had to do was show up.</p></div>
+<div class="paragraph"><p>They didn&#8217;t go tell people to look at all the weaknesses
+their product had. They focused on the strengths. On
+what would convince people to try it. People would go
+to meetups, discuss with people, commit to try it (or
+try it at meetups directly), and by doing so sell MongoDB
+to themselves.</p></div>
+<div class="paragraph"><p>How do we get people to meetups though? That&#8217;d be the
+first step: you need to <strong>catch people&#8217;s attention</strong>.
+I believe MongoDB did this using benchmark results.
+Ironic isn&#8217;t it? MongoDB gets fast benchmark results
+because they lose data, and this gets everyone to buy
+into the product.</p></div>
+<div class="paragraph"><p>The key points to remember about this are:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+catch people&#8217;s attention
+</p>
+</li>
+<li>
+<p>
+show your product&#8217;s strengths
+</p>
+</li>
+<li>
+<p>
+make people take a commitment
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Once they commit to something, you win. Everyone will not
+end up ultimately using your product of course, but it&#8217;s
+at the very least become a consideration. It&#8217;s on their
+mind. Their resolve will be stronger when they ultimately
+try it and inevitably run into issues.</p></div>
+<div class="paragraph"><p>Erlang&#8217;s syntax is a weakness. Almost nobody looks at the
+Erlang syntax and falls in love with it at first sight.
+No, it takes time to learn it and understand how good it
+is. You need to sell Erlang to people without showing
+the Erlang syntax. If you do show it, then you need to
+hide the parts that feel alien. Function calls are OK.
+Recursion, not so much. Maps are OK. Records, not.</p></div>
+<div class="paragraph"><p>Avoiding code is not always possible when you try
+to sell it, especially to developers. You can however
+prepare them to accept the alien syntax by admitting
+that the syntax is not perfect before you show it.
+You can do this while praising it at the same time.
+For example, "the syntax is a little out there, but
+it matches the concepts perfectly, it will all make
+sense when you start learning".</p></div>
+<div class="paragraph"><p>This might not be the best introduction. Someone will
+need to A/B test it to find the one that gives the
+best results. But that should give you ideas.</p></div>
+<div class="paragraph"><p>When something terrible happens, mentioning that this
+isn&#8217;t the end of the world <strong>before</strong> you tell others what
+happened will soften their reaction. When someone
+breaks your favorite item and cries over it calling
+themselves stupid, it&#8217;s harder to get mad at them,
+compared to the same event with no emotional reaction.</p></div>
+<div class="paragraph"><p>Our behavior is largely dependent on what&#8217;s at the
+top of our mind, so it&#8217;s up to you to take advantage
+of this to make your case in the best conditions.</p></div>
+<div class="paragraph"><p>Next time you try to make someone use Erlang, remember
+that you should aim for getting a spoken commitment
+out of them, if possible before you show the syntax.
+If that&#8217;s not possible, then prepare them to accept
+the flaws or the weirdness before they see them.</p></div>
+</description> + </item> + + <item> <title>Don'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> @@ -1020,238 +1162,5 @@ of your company&#8217;s money.</p></div> </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><div class="paragraph"><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&#8217;ll be an article that&#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.</p></div>
-<div class="paragraph"><p>Once upon a time-- Okay this isn&#8217;t a fairy tale. The story
-begins with a short chapter in 2010. The year 2010 started
-with a fairly major event in my life: the US servers for the
-online game I stopped playing a few months before, but was
-still involved with through its community, were closing. OMG!
-Someone found a way to log packets and started working on a
-private server; meanwhile the JP servers were still up. And
-that&#8217;s pretty much it.</p></div>
-<div class="paragraph"><p>Fast forward a few months and it became pretty clear that
-the private server was going nowhere considering all the drama
-surrounding it-- which is actually not unusual, but it was
-more entertaining than average and the technical abilities of
-people running the project were obviously lacking so I decided
-to obtain those logged packets and look at things myself. I
-didn&#8217;t want to do a private server yet, I only wanted to take
-a peek to see how things worked, and perhaps organize some
-effort to document the protocol.</p></div>
-<div class="paragraph"><p>There was 10GB of logs. I didn&#8217;t have an easy to use
-language to analyze them, and hex editors wouldn&#8217;t cut it for
-most purposes, so I had to look elsewhere. This was a good
-opportunity to start learning this PHP killer I read about
-before, which also happens to feature syntax for matching
-binaries, called Erlang. To be perfectly honest I wouldn&#8217;t
-have touched the logs if I didn&#8217;t have the added motivation
-to play with and learn a new language.</p></div>
-<div class="paragraph"><p>At the time it was pretty hard to learn Erlang. In my
-experience there was Joe&#8217;s book (which I always recommend
-first as I believe it is the best to learn the Erlang side
-of things; but falls a little short on OTP), and there was
-about 5 chapters of LYSE. There were a couple other books
-I never managed to get into (sorry guys), and there was also
-a few interesting blogs, some of which I can&#8217;t find anymore.
-Finally the #erlang IRC community was there but I was strictly
-lurking at the time.</p></div>
-<div class="paragraph"><p>What a difference compared to 4 years later! (That&#8217;s
-today, by the way!) Now we have more books than I can
-remember, tons of articles covering various aspects of the
-language and platform, many targeting beginners but a good
-number of them also about advanced topics. We even have a
-free online book, LYSE, with more than 30 chapters covering
-pretty much everything. Needless to say I never finished
-reading LYSE as it got written slower than I learnt.</p></div>
-<div class="paragraph"><p>Back to 2010. I wrote a parser for the logs, and
-aggregated those results into one CSV file per packet type
-so I could open them in Gnumeric and aggregate some more,
-but manually this time, and draw conclusions on the packet
-structures. That was pretty easy. Even for a beginner.
-Anyone can go from zero to that level in a day or two.
-Then, having mastered binary pattern matching, I wanted
-to learn some more Erlang, by making this aggregation
-faster. What I had done before worked, but I wasn&#8217;t going
-to wait forever to process everything sequentially. So I
-looked and found a project called <code>plists</code> (still exists,
-but not maintained AFAIK). I downloaded that project and
-replaced my <code>lists:</code> calls to <code>plists:</code>.
-Boom. In just a few minutes all logs were processed, and
-I had learnt something new.</p></div>
-<div class="paragraph"><p>It is particularly interesting to note that the lack of
-a package manager or index never bothered me. Neither before
-nor after learning Erlang. My experience with package
-managers was mostly related to Ubuntu, a little Perl and
-Python, and PHP&#8217;s Pear. Let&#8217;s just stay polite and say it
-was always a terrible experience. So searching on the Web
-didn&#8217;t feel awkward, because even if I used a tool or
-website I would have ended up doing a search or two anyway.
-This is in contrast to the package index feature in
-<a href="https://github.com/ninenines/erlang.mk">Erlang.mk</a>,
-which is meant to simplify specifying dependencies more
-than anything: <code>DEPS = cowboy</code>. It does not
-attempt to solve any other problem, and will only attempt
-to solve one extra problem in the near future, which is
-the discovery of packages. So expect some kind of website
-listing packages soon enough.</p></div>
-<div class="paragraph"><p>I want to use this parenthese to also point out that at
-the time there was a very small number of projects out there,
-at least compared to today. While you sometimes hear people
-complain about lack of certain libraries, it is so much
-better now than it was before! The situation improves very
-quickly, so much that it&#8217;s not going to be that big an issue
-soon enough.</p></div>
-<div class="paragraph"><p>Wanting to know more about that game&#8217;s protocol, in the
-year 2010, I ended up starting to write more Erlang code to
-simulate a server and use the server to query the client and
-see what was happening, documenting the packets and so on.
-This eventually lead to a larger project implementing more
-and more until people got their hopes up for a revival of
-the game, all the while the now competing original server
-project died in a stream of drama and technical incompetence.
-Of course, I ended up doing what any good Internet citizen
-would do, I crushed people&#8217;s hopes, but that&#8217;s not important
-to our story. The important part is that before giving up
-on this project, I not only learnt a good deal of Erlang
-and a little deal of OTP (which I did not touch until 6
-months after I started with Erlang; see the paragraph
-about learning material above), but I also had an intriguing
-idea pop into my mind for what would become my greatest
-success yet.</p></div>
-<div class="paragraph"><p>The giving up part was not easy. Having had financial
-difficulties all year 2010 and part of 2009, I resolved
-to travel back to Paris to try and make it. I ended up
-sleeping in offices for 6 months, being hosted by a shady
-person, and hearing my fair share of stories about
-the dark side of business. While there I also worked for
-another company with someone who would end up becoming
-another high profile Erlang developer. The situation
-slowly improved, I started taking part in the #erlang
-IRC discussions, giving up my status of lurker and, a
-few months into 2011, started working on the Apache killer
-project: Cowboy.</p></div>
-<div class="paragraph"><p>This is the part where I probably should get accused of
-racism and other fun things, but I never did. And I think
-that speaks lots about the Erlang community. In all my time
-writing Erlang code, I can count the number of conflicts I
-had with other people on a single hand. This is the nicest
-programming community I have ever seen, by far. And the
-humblest too. The Erlang community feels like Japan. And
-I love Japan. So I love the Erlang community. I can&#8217;t say
-this enough. This is something that stayed true for all
-my time using Erlang, and despite the rise of alternative
-languages that are not Japan the Erlang community has
-remained very Japan.</p></div>
-<div class="paragraph"><p>The first published version of Cowboy was written in
-two weeks. A little before those two weeks, during, and
-a while after, pretty much everything I said on the
-Internets was that Cowboy was going to be the greatest
-HTTP server ever, that the other servers were problematic
-(and just to be clear, Yaws was rarely if ever mentioned,
-due to being in a perceived different league of "full
-featured servers" while Cowboy was a "lightweight server"),
-and that Cowboy will be the best replacement to a Mochiweb
-or Misultin application. This, alongside a lot of time
-spent on IRC telling people to use Cowboy when they were
-asking for an HTTP server to use, probably made me sound
-very annoying. But it worked, and Cowboy started getting
-its first users, despite being only a few weeks old. Of
-course, as soon as I got my very first user, I started
-claiming Cowboy had "a lot of users".</p></div>
-<div class="paragraph"><p>Looking back today I would definitely find myself annoying,
-this wasn&#8217;t just an idle comment there. For about a year,
-maybe a little more, all I ever said was that Cowboy was
-the best. This probably made me a little dumber in the
-process (as if I wasn&#8217;t enough! I know). Being French, I
-sometimes would also say things quite abruptly. To stay
-polite, I probably sounded like an asshole. I learnt to
-stop being so French over time thankfully.</p></div>
-<div class="paragraph"><p>I think what was most important to Cowboy at the time,
-was three things. First, it felt fresh. It was new, had new
-ideas, tried to do things differently and followed "new" old
-best practices (the OTP way-- which was simply too obscure
-for most people at the time). Second, it had me spending
-all my time telling people to use it whenever they were
-looking for an HTTP server. Third, it had me helping people
-get started with it and guide them all the steps of the way.
-Mostly because it didn&#8217;t have a very good documentation, but
-still, hand holding does wonders.</p></div>
-<div class="paragraph"><p>To be able to help people every time they had a problem,
-I did not spend all my days reading IRC. Instead I simply
-made sure to be notified when someone said <code>cowboy</code>.
-The same way many people subscribe to alerts when their
-company is mentioned in the news. Nothing fancy.</p></div>
-<div class="paragraph"><p>Time went on, Cowboy grew, or as some like to say,
-completely destroyed the competition, and many people
-eventually moved from Mochiweb and Misultin to Cowboy.
-And then Roberto Ostinelli stopped Misultin development
-and told everyone to move to Cowboy. This is the most
-humble and selfless act I have ever seen in the programming
-sphere, and I only have one thing to say about it: GG.
-Thanks for the fish. He left me with the tasks of improving
-Cowboy examples, documentation and strongly believed that
-the Misultin interface was more user friendly out of all
-the servers. So I added many examples, as many lines of
-documentation as we have of code, and strongly believe
-that Cowboy 2.0 will be the most user friendly interface
-out of all servers. But only time will tell.</p></div>
-<div class="paragraph"><p>With the rise of the project and the rise in the number
-of users, my previous strategy (completely incidental, by
-the way, and definitely not a well thought out plan to
-become popular) stopped working. It was taking me too much
-time. The important aspects slowly drifted. If I wanted to
-support more users, I would have to spend less time with
-each individual user. This was actually a hard problem.
-You basically have to make people understand they can&#8217;t
-just come to you directly when they have a problem, they
-have to follow proper channels. It becomes less personal,
-and might be felt like you don&#8217;t care about them anymore.
-You have to hurt some people&#8217;s feelings at this point. It
-is quite unfortunate, and also quite difficult to do. There
-is some unwritten rule that says early adopters deserve
-more, but in the real world it never works like this. So
-I probably hurt some people&#8217;s feelings at some point. But
-that&#8217;s okay. Because even if you make sure to be as nice
-as possible when you tell people to go through proper
-channels from now on, some people will still get offended.
-There&#8217;s nothing you can do about it.</p></div>
-<div class="paragraph"><p>From that point onward the important points about the
-project was getting the documentation done, making sure
-people knew about the proper channels to get help and
-report issues, etc. Basically making myself less needed.
-This is quite a contrast with the first days, but I believe
-Cowboy made that transition successfully.</p></div>
-<div class="paragraph"><p>Not only did I win time by not having to hold hands with
-everyone all the time (not that I didn&#8217;t like it, but you
-know, the sweat), but I also won time thanks to the increased
-project popularity. Indeed, the more users you have, the more
-annoying guys there are to tell people to use your project
-and that it&#8217;s the best and everything. Which is great. At
-least, it&#8217;s great if you don&#8217;t pay too much attention to it.
-Sometimes people will give an advice that is, in your opinion,
-a bad advice. And that&#8217;s okay. Don&#8217;t intervene every time
-someone gives a bad advice, learn to let it go. People will
-figure it out. You learn by making mistakes, after all. Use
-this extra time to make sure other people don&#8217;t end up
-giving the same bad advice instead. Fix the code or the
-documentation that led to this mistake. Slowly improve the
-project and make sure it doesn&#8217;t happen again.</p></div>
-<div class="paragraph"><p>This is my story. So far, anyway.</p></div>
-</description> - </item> - </channel> </rss>
\ No newline at end of file diff --git a/services/index.html b/services/index.html index 1ebc9586..62c7e1de 100644 --- a/services/index.html +++ b/services/index.html @@ -192,6 +192,8 @@ the same restrictions apply.</p></div> + + <div class="sect2">
<h3 id="_like_my_work_donate">Like my work? Donate!</h3>
<div class="paragraph"><p>Donate to Loïc Hoguin because his work on Cowboy
@@ -565,6 +567,8 @@ and Erlang.mk is fantastic:</p></div> + + </div> </div> </div> diff --git a/sitemap.xml b/sitemap.xml index d70c57e2..770b97f6 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -3,7 +3,12 @@ <url> <loc>https://ninenines.eu/</loc> - <lastmod>2017-01-22T00:00:00+01:00</lastmod> + <lastmod>2017-03-26T00:00:00+01:00</lastmod> + </url> + + <url> + <loc>https://ninenines.eu/articles/the-elephant-in-the-room/</loc> + <lastmod>2017-03-26T00:00:00+01:00</lastmod> </url> <url> @@ -762,6 +767,10 @@ </url> <url> + <loc>https://ninenines.eu/docs/en/cowboy/2.0/guide/specs/</loc> + </url> + + <url> <loc>https://ninenines.eu/docs/en/cowboy/2.0/guide/architecture/</loc> </url> |