« first day (6 days earlier)      last day (88 days later) » 

00:05
Yes, Flurry reduces a sequence of applications by first reducing each of the terms and then performing each application in sequence.
Which means [[f a] b] can have different behavior from [f a b] in some situations.
Then can you explain this:
$ ./flurry -nin -c "{{{}{}}}{<({})({}){}>}{<({}){}>}"
9
$ ./flurry -nin -c "{{{}{}}}{}{}" 2 3
8
In the second example, the first pop returns 3 and the second returns 2.
Then it should behave the same as the first.
I suspect what actually happens in the second case is this:
{{{}{}}}{}{}  | 2 3
{{{}{}}}3{}   | 2
{{}{}}{}      | 2 3
{{}{}}3       | 2
{}{}          | 2 3
3{}           | 2
3 2           |
00:23
Ah, never mind
I forgot how my own interpreter works ಠ_ಠ
I guess that's one weird rule you wouldn't have to handle if you wanted a visual interpreter with step-by-step reduction.
00:41
It's not a weird rule, it's a natural consequence of strict evaluation (using normal order I guess, because I just checked for KI(SII(SII)) and it immediately terminates)
 
6 hours later…
06:59
CMC: A non-trivial (entirely consisting of non-comments) answer to Print last, middle, and first of your source code
(A trivial answer is ((({}))), just like trivial Brain-flak answer

« first day (6 days earlier)      last day (88 days later) »