Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Add blog post about 0.11

  • Loading branch information...
commit d9612040b818b148e4bf8c19e83e967075e2de62 1 parent 02433a6
Doug Beardsley authored February 15, 2013
51  blogdata/content/2013/02/15/brief-0.11-comments.md
Source Rendered
... ...
@@ -0,0 +1,51 @@
  1
+| title: A brief note on 0.11
  2
+| author: Doug Beardsley <mightybyte@gmail.com>
  3
+| published: 2013-02-15T17:10:00-0500
  4
+| updated:   2013-02-15T17:10:00-0500
  5
+| summary: Clarification on the significance of the 0.11 release
  6
+
  7
+The end of last month saw the 0.11 release of the heist and snap packages.  It
  8
+was not accompanied by our traditional announcement and release notes blog
  9
+post, and some people have been asking about it.  Here is a brief description
  10
+of what is going on and how the 0.11 release affects you.
  11
+
  12
+*tl;dr* The core functionality of compiled heist is stable, but the API is
  13
+still maturing.  0.11 is a significant step in the right direction, but it
  14
+didn't get a release announcement because we're making rapid progress and
  15
+might make more major releases in the near future.  If you want to start using
  16
+compiled heist today in production applications, then you should talk to us
  17
+directly on IRC so we can collaborate.
  18
+
  19
+## 0.10
  20
+
  21
+The 0.10 release completely redesigned heist, but those changes did not affect
  22
+snap-core and snap-server at all.  Prior to this, we had made a pattern of
  23
+making major releases of all our packages in lock step.  But since 0.10 made
  24
+no breaking changes to snap-core and snap-server, we decided after much debate
  25
+to not introduce a major version bump to -core and -server that did not
  26
+actually have any breaking changes.
  27
+
  28
+The main motivator here was that we wanted to get the new Heist code out the
  29
+door so we could get more feedback.  We are working up to a 1.0 release and
  30
+wanted to have more experience working with the new compiled heist paradigm
  31
+before giving it 1.0 status.
  32
+
  33
+## Maturing an API
  34
+
  35
+When 0.10 was released we had been working on it for eight months.  The core
  36
+idea of compiled splices was fairly mature and well thought out, but since it
  37
+still had not been used in large-scale production applications the API was
  38
+immature.  This pattern is not unfamiliar.  The basic concept for interpreted
  39
+Heist was there in 0.1, but we didn't discover the incredibly useful
  40
+runChildrenWith pattern until 0.6.  It takes time to tease apart the higher level
  41
+patterns that make a more friendly API.
  42
+
  43
+The compiled Heist paradigm is no different.  I recently started doing a lot
  44
+of work with compiled splices in a real world app.  That is giving me a lot of
  45
+feedback that I am using to improve the API.  I released 0.11 early so that
  46
+people could become aware of these patterns now, rather than getting used to
  47
+the less friendly 0.10 API.  However, the new API is still a work in progress.
  48
+I don't know what tomorrow will bring, so I can't predict how it will evolve.
  49
+But once I feel the API is more stable we will make full release notes for
  50
+everything that happened after 0.10.
  51
+
6  snap-website.cabal
@@ -22,12 +22,12 @@ Executable snap-website
22 22
     containers,
23 23
     directory,
24 24
     filepath,
25  
-    heist >= 0.10 && < 0.11,
26  
-    lens >= 3.7 && < 3.8,
  25
+    heist >= 0.10 && < 0.12,
  26
+    lens,
27 27
     MonadCatchIO-transformers >= 0.2 && < 0.4,
28 28
     mtl >= 2 && <3,
29 29
     process,
30  
-    snap        >= 0.10 && <0.11,
  30
+    snap        >= 0.10 && <0.12,
31 31
     snap-core   >= 0.9 && <0.10,
32 32
     snap-blaze  >= 0.2.1 && <0.3,
33 33
     snap-server >= 0.9 && <0.10,

0 notes on commit d961204

Please sign in to comment.
Something went wrong with that request. Please try again.