A Little Scheme

I go through phases of playing with Scheme for utility code, maybe even portable dev; while FreePascal is a better language for this, I'm frustrated by the lack of library support and the useless iOS situation.

Scheme's always been an emergency backup language; it was fun to learn back in the '80s and early '90s, and both SICP and TSPL are good books, but nobody wanted to pay for Scheme dev, and anyway the language is very annoying to write. I often treat it as a logic puzzle to get anything done, not a useful tool. But it does have good library support, and it can compile to very fast binaries, despite having GC pauses and consuming 2x as much memory as a C program. Maybe I can get better at solving problems in it, build up some libraries, and make it useful?

So the current landscape is:

  • Chez Scheme:
    • Pros:
      • Very fast to compile and at runtime, competitive with C compilers.
      • Great interactive REPL, not just a half-broken readline history like pretty much every other Scheme.
      • Debugger is reasonably good, and integrated in the REPL. All I really use myself is (trace FOO) and (inspect BAR), but non-caveman coders will make better use of it.
      • Current R6RS implementation plus extensive chezscheme library.
      • By R. Kent Dybvig, author of TSPL, and Cisco currently employs him to maintain Chez Scheme.
      • REPL environment is called a café, which I find charming. Yes, I also liked all the coffee puns and iconography from early Java programming.
    • Cons:
      • Not as widely supported by tools & documentation as Racket.
  • Racket:
    • Pros:
      • Very nice GUI.
      • Current R6RS implementation plus extensive racket library.
      • Built around making multiple languages; I don't really care about this. I loathe "Typed Racket", one of the worst combinations of ideas in history.
      • Tons of documentation.
    • Cons:
      • Mediocre performance. There's a project to rehost Racket on Chez Scheme, which would fix this, but then why use Racket?
      • Doing anything in the GUI destroys your environment, all the objects you've made, unlike any LISP or Scheme ever. So it's utterly fucking useless as an interactive REPL. I can't say enough bad things about this. ★☆☆☆☆ Kill On Sight.
  • Chicken:
    • Pros:
      • Compiles to C and thence to native binaries, with nice FFI to C libraries.
    • Cons:
      • Mostly old R5RS, with a few extension libraries.
      • Terrible REPL, only really usable as a compiled language.
  • Scheme R7RS benchmarks

Chez Scheme is the clear winner for me; if I was a novice, I might choose Racket and not realize that the REPL is a broken abomination for a while. If I was only doing C interop, Chicken would be better.

Editing in BBEdit works OK, but it doesn't know how to find function definitions. I guess Vim has current syntax, but I'm kinda over that habit unless I have to sysadmin. I have never been emacsulated and never will.

Atom's symbols list doesn't do any better. But if you do want to use it, install package language-racket (all other language-schemes are R5RS at best), and then add some file types to config.cson:

      "source.racket": [

In any editor, any language, I use hard tabs (1 char = 1 logical indentation level, obviously), and normally tabstop at 8 chars which discourages very long nesting and encourages me to extract functions. Scheme is indentation hell, so set the tabstop to 4 spaces. (The code blocks below won't show that.)

Do not criticize my C-like paren/brace placement; I prefer clear readability of code structure to some obsolete Emacs dogma.

So, let's see it work, with hello.ss:

#!/usr/bin/env scheme-script
(import (chezscheme))
(format #t "Cheers 🍻 , ~a!~%" (car (command-line-arguments)))
% chmod 755 hello.ss
% ./hello.ss Mark
Cheers 🍻 , Mark!

Now for something more serious:


;; stdlib.ss
;; Copyright © 2015,2018 by Mark Damon Hughes. All Rights Reserved.
(library (stdlib)
    (export inc! dec! currentTimeMillis randomize input atoi)
    (import (chezscheme))

;; Variables

(define-syntax inc!
    (syntax-rules ()
        ((_ x)      (begin (set! x (+ x 1)) x))
        ((_ x n)    (begin (set! x (+ x n)) x))

(define-syntax dec!
    (syntax-rules ()
        ((_ x)      (inc! x -1))
        ((_ x n)    (inc! x (- n)))

;; Date-Time

(define (currentTimeMillis)
    (let [(now (current-time))]
        (+ (* (time-second now) 1000)
            (div0 (time-nanosecond now) 1000000))

;; Random Numbers
;; "Anyone who attempts to generate random numbers by deterministic means is, of course, living in a state of sin." —John von Neumann

(define (randomize)
    (random-seed (bitwise-and (currentTimeMillis) #xffffffff) )

;; Input/Output

;; Reads a line from stdin, ends program on EOF
(define (input)
    (let [(s (get-line (current-input-port)) )]
        (if (eof-object? s)
            [begin (display "Bye!\n")

;; Strings

;; Converts a string to an integer, 0 if invalid
(define (atoi s)
    (let [(n (string->number s))]
        (if (eqv? n #f)
            (inexact->exact (truncate n))



#!/usr/bin/env scheme-script
;; guess.ss
;; Copyright © 2015,2018 by Mark Damon Hughes. All Rights Reserved.

(import (chezscheme))
(import (stdlib))

(define (guess)
    (display "I'm thinking of a number from 1 to 100, try to guess it!\n")
    (let [(theNumber (+ (random 100) 1))]
        (define guesses 1)
        (do [(break #f)] (break)
            (format #t "Guess #~a? " guesses)
            (let [(g (atoi (input)))]
                    [(or (<= g 0) (>= g 100))
                        (display "Try a number from 1 to 100.\n")
                    [(< g theNumber)
                        (display "Too low!\n")
                        (inc! guesses)
                    [(> g theNumber)
                        (display "Too high!\n")
                        (inc! guesses)
                        (display "You got it!\n")
                        (set! break #t)
    (display "***GAME OVER***\n")


chez-compile.zsh, with my thanks to Graham Watt for explaining wpo and libraries:

if [ $# -ne 1 ]; then
    echo "Usage: chez-compile.zsh MAINNAME"
    exit 1
rm -f *.so
rm -f *.wpo
mkdir -p bin

cat <<ENDTEXT |scheme -q --optimize-level 3
(compile-imported-libraries #t)
(generate-wpo-files #t)
(compile-program "$1.ss")
(compile-whole-program "$1.wpo" "bin/$1")

rm -f *.so
rm -f *.wpo
if [ -f "bin/$1" ]; then
    chmod 755 "bin/$1"

Now I just:

% chez-compile.zsh guess
compiling guess.ss with output to guess.so
compiling stdlib.ss with output to stdlib.so
% bin/guess
I'm thinking of a number from 1 to 100, try to guess it!
Guess #1? 50
Too low!
Guess #2? ^DBye!

Well, that was an adventure to get the equivalent of my first BASIC program from 1980, which can be run in Chipmunk BASIC if you don't happen to have a TRS-80 Model I handy:

10 N=INT(100*RND(1))+1:T=1
100 PRINT "GUESS #";T;"? ";:INPUT "",G
110 IF G<=0 OR G>=100 OR G<>INT(G) THEN 200
120 IF G<N THEN 210
130 IF G>N THEN 220
140 GOTO 230
210 PRINT "TOO LOW!":T=T+1:GOTO 100
220 PRINT "TOO HIGH!":T=T+1:GOTO 100

But now I can think about more complex problems in Chez Scheme!

Here's the tiniest piece of what I've been thinking about next:

Island in emoji

The Freedom to Write Garbage

Nice notebooks make it hard to write, because you feel you can't write garbage in them. Cheap notebooks give you the freedom to write garbage.

I used to use a DayRunner®, but then I'd fill it with cheap lined filler paper, and fill those pages with everything, and throw them in a box when I was done; I had a Palm Pilot for scheduling, but writing long notes in it was hard. Later I got into nice big Moleskines, which I rarely used because they seemed too nice for my chaos. Then stacks of Field Notes, which I keep one in my jacket, but use grudgingly. Lately I'm back to cheap 50¢ spiral notebooks and pads, and I write all the time.

I don't use a fancy pen, either. I'm currently using a "TÜL" mechanical pencil which is semi-junky (the eraser holder is loose and pushes down, so I have to tape it in place!) but fat enough for my hand, and a Field Notes clicky ballpoint which needs a 10¢ refill soon. A box of disposable ballpoints will work just as well as your $500 handcrafted engraved gold-plated fountain pen and hand-squeezed squid ink.

None of what I write on paper is important long-term, that's what Markdown files on a computer are for. Instead, every new topic or date gets written at the top of a page, sometimes just one item on that topic. And I'll go forward thru a book until it's full, then move on to the next. Anything worth keeping gets typed in eventually.

Here's a least-embarassing page from my current notepad, tracking Animal Crossing characters because paging thru Contacts in the game is so very slow.

notebook-animal crossing

And yes, my handwriting is appalling and random-looking; no two letter forms are the same. I learned slow and perfect block lettering until I got the Palm Pilot, then Graffiti retrained me and it's been crap ever since. I learned cursive as a kid but have never used it for long writing.

MARK-13 Thursday Music

Just discovered that iTunes Store has Hardware (Richard Stanley, 1990) for $9.99 in HD! Blu-Ray is out of print, DVD was a trash VHS port. Best punk rock SF apocalypse flick. "It's horrible, I love it!"

One rewatch later…

Looks even more prophetic now than when young cyberpunk Mark would watch the VHS over and over on a shitty CRT. Get used to the world of ecological disaster, locked into your apt by security systems installed by panopticon-watching perverts, terrorists with trucks smashing open buildings, people squatting & scavenging in the ruins. When a billion people near the uninhabitable equator starve and try to migrate away from global warming, you think anyone's gonna take them in? Or will we just irradiate the planet fighting wars, sterilize the mutant population, and let Google's autonomous killer robots knock us down to carrying capacity? I never believed in a future, and here it is.

… So, that went a little dark. Have a drink, a joint, a fuck, make some art, and play some cute distracting videogames to forget about the end of the world.

The soundtrack's another OOP classic, but here's the day's music based on it:

On the Use of Communications Networks of Tin Cans and String

Gen-X (remember us? I suppose not.) invented l33tspeek but knew when to stop doing it. Now, "old people" use ellipses… and end texts with a period, and it makes the Millennials upset.

Back in the day, all we had were tin cans & string, er, BBS's, which were like Thunderdome without the sense of fair play, but we also tolerated much weirder behavior, and at worst you couldn't call back to one board in your city. Now if you say anything any one of the kiddie mafia doesn't like, they all have a toddler meltdown at you, over the tin can network we built.

I don't have a solution for any of this, just kicking out Tiny Tim's crutches and laughing at him, as one does this season.

Hire Mark

Indie life has been fun, but not especially profitable even when I ship, which I'm having a hard time doing again without a team, and I know from hard experience I shouldn't be running a business, advertising, or managing a team; I'm a nerd who makes software. So…

I'm looking for a new software engineering position. I'd prefer to write JavaScript front-end and back-end, but equally happy to do Objective-C (or just C!), or server-side Java or Python. I've been doing all of these for a decade or more, and I keep my skills up. I mostly do agile, originally Extreme Programming/Test-Driven Development.

I'd prefer remote work—you don't need me in your office to get work done, and I dislike losing a couple hours a day to commutes and office nonsense—but if you're not in the worst parts of the world, I'd consider moving. If you don't have snow, ever, that's a positive.

Like, subscribe, retweet, write this down on a napkin and slip it to a guy you know. Get Mark hired.

Advent of Code 2017: Week 1

After 7 days, let's see how my Advent of Code 2017 is going.

  • Web framework: I made a standard web console, which I then copy forward to the next day. I could just as easily have put all the buttons on a single page, but it'd get too long by day 31.

  • Unit testing: As seen in stdlib.js, my test framework is very simple: On page load, setup, run some asserts, finish to get stats and redbar/greenbar the test console. This has been a great win, even though several of the days had only one or two examples.

  • 01:

    "The captcha requires you to review a sequence of digits (your puzzle input) and find the sum of all digits that match the next digit in the list. The list is circular, so the digit after the last digit is the first digit in the list."

    • So this is nice and easy, linear problem for JS string processing. On the second variant I turned the inner function to pick the next char into a function, which I pass in. No external state.
  • 02:

    "The spreadsheet consists of rows of apparently-random numbers. To make sure the recovery process is on the right track, they need you to calculate the spreadsheet's checksum. For each row, determine the difference between the largest value and the smallest value; the checksum is the sum of all of these differences."

    • Needed to write more utils, this time to process strings into a table of numbers. My first solution kept it as a table of strings, and then I had problems with JS type coercion. Same strategy of finding a pure functional inner loop and extracting that as a function. Actually, subtotalFunc1 mutates cols, but you'll never use it again so it doesn't matter.
  • 03:

    "Each square on the grid is allocated in a spiral pattern starting at a location marked 1 and then counting up while spiraling outward. For example, the first few squares are allocated like this:

    17 16 15 14 13
    18 5 4 3 12
    19 6 1 2 11
    20 7 8 9 10
    21 22 23---> ...

    While this is very space-efficient (no squares are skipped), requested data must be carried back to square 1 (the location of the only access port for this memory system) by programs that can only move up, down, left, or right. They always take the shortest path: the Manhattan Distance between the location of the data and square 1."

    • This was a little insane. There's apparently a pure math solution, but I am not a mathematician, I am a turtle; also song; also Lewis Carroll; also Gödel Escher Bach. So I solved it by moving a turtle around the spiral, turning left whenever there's an open space, and then I could just examine the spiral for values.
    • Yes, I store points as a vector-2 of numbers, rather than making a "Point" class with x,y. In C using a struct makes more sense (since it only takes 8 bytes intead of the 40+ in any object system!), but in anything else, the vector requires the least memory, least work, and is easiest to serialize, use as a hashtable key, and so on.
    • I just copy-pasted and modified for the second task, instead of making a nice inner function to pass in. It's not incredibly hard to parameterize, but I would need to break out of that inner function to return early, so probably using an exception for flow control?
    • Javascript objects are super-useful, like Python dicts but even easier to use. Stuff a bunch of points for the grid, and properties for the minPt, maxPt (bounds) and lastPt, one structure gets to hold everything about the spiral. Writing this in a type-safe or pure functional language would be annoying.
  • 04:

    "A passphrase consists of a series of words (lowercase letters) separated by spaces.
    To ensure security, a valid passphrase must contain no duplicate words."

    • Super simple, a histogram that only counts to 1. The second part only requires sorting the chars in each word, so you can check they aren't anagrams. I was worried that day 3 was the start of an exponential curve in difficulty, so by the end it'd take to the end of the Earth to finish.
  • 05:

    "The message includes a list of the offsets for each jump. Jumps are relative: -1 moves to the previous instruction, and 2 skips the next one. Start at the first instruction in the list. The goal is to follow the jumps until one leads outside the list.
    In addition, these instructions are a little strange; after each jump, the offset of that instruction increases by 1. So, if you come across an offset of 3, you would move three instructions forward, but change it to a 4 for the next time it is encountered.
    How many steps does it take to reach the exit?"

    • I returned the program counter at first, and that passes the sample data test, so I "guessed" wrong the first time, but then reread and found my bug. Having only one example is a problem. Both parts are as usual solved by passing in a function to determine the next state of the instruction. Trivial one aside from my stupid bug.
    • I'm building up a good library of tools by now.
  • 06:

    "In each cycle, it finds the memory bank with the most blocks (ties won by the lowest-numbered memory bank) and redistributes those blocks among the banks. To do this, it removes all of the blocks from the selected bank, then moves to the next (by index) memory bank and inserts one of the blocks. It continues doing this until it runs out of blocks; if it reaches the last memory bank, it wraps around to the first one.
    The debugger would like to know how many redistributions can be done before a blocks-in-banks configuration is produced that has been seen before."

    • Making the balancer was straightforward, I stored each state as a string in a history array, and a parallel histogram to catch the duplicate; I could get rid of hist but it turned out to make the second task easier.
  • 07: (Don't read this or the code until tomorrow if you don't want a spoiler)

    "You offer to help, but first you need to understand the structure of these towers. You ask each program to yell out their name, their weight, and (if they're holding a disc) the names of the programs immediately above them balancing on that disc. You write this information down (your puzzle input). Unfortunately, in their panic, they don't do this in an orderly fashion; by the time you're done, you're not sure which program gave which information.
    Before you're ready to help them, you need to make sure your information is correct. What is the name of the bottom program?"

    • Building the tree was a good puzzle, but not hard: Parse the text into nodes, keep them in a dictionary, then build the structure, and return the only parentless node (the root). Making a recursive toString so I could debug it was important…
    • Second task looked to be tedious (depth-first search and pass the result all the way up), but then I just looked at my output and saw the unbalanced numbers, so entered it by hand. I am a computer, too.

I've got both gold stars each day. I'm completely incapable of reliably checking in at exactly 21:00 PST, and I'm too fussy about my code to ever be "the fastest", so my rankings are awful; maybe it ought to count from when you read the problem set, but then everyone would cheat on at least the first task.

Advent of Code 2017

I've joined the Advent of Code, and I'll be doing it in JS. Got my 2 stars for the day.

For good discipline (or as a handicap), I'm building a halfway-decent set of pages, unit testing framework, and sort of doing things right (good ES6 practices) instead of easy (hack some inline JS in compatibility mode). I'll link it in the sidebar tomorrow, when challenge 1 expires: My Advent of Code

Go on and do it yourself! I say "easy mode is for babies" and make it hard on myself, but really you can do this in anything. There's a perfectly nice Chipmunk BASIC or FreePascal if you're old-school.

Note: The leaderboard reset time is ridiculous, and I don't care about speed-coding or leaderboards. Don't stress about competing for first 100 completions, just do the thing.

Animal Crossing: Pocket Camp

On December, 2005, Animal Crossing: Wild World (AC:WW) came out for the Nintendo DS, I immediately got it, created a town called Yama, and played at least 15 minutes, often hours, every day for years.

I finally got to the point where my house was maxed out, filled with trophies, mail storage was being used for excess items, I had every K.K.Slider song, most of my town was covered with tree farms, flower farms, or stickers to make roads (and force digging holes to be in specific areas).

I was spending too much time in Yama, and couldn't stop checking it every day, so around 2008 I deleted my town, I couldn't break the habit any other way. I still miss Yama.

Animal Crossing: Wild World Snowman

Now Animal Crossing Pocket Camp (AC:PC) is out on iOS, and I can see I'll have the same problem eventually, but for now it's nice to have anything like it back.

AC:PC Squirrel

It's a little frustrating at first, being forced to do tutorials with no freedom of action; I'm of the theory that a game should have chargen, and then you're loose in the world. If you want tutorials or information, leave NPCs or books around, but don't make the player tap on a person or box to progress. The IAP doesn't seem too aggressive in this, I know I could buy "leaf tickets" (and I have to have them, to get K.K.Slider and Tom Nook for my camp), but I'm building them up at some pace in-game.

The camp is much smaller than a town or expanded house, and I don't like the outdoors theme and hippie bus as much as AC:WW, and you can't alter other camps. There's a really annoying siren wail when you're dragging items around, it's piercing and the least Nintendo-like sound I've ever heard; I'm going to try to file a bug report if they have any way to do that. As usual, Nintendo has never heard of scaling servers, and I'm getting constant errors, which will only get worse as more of the world wakes up and starts playing today.

AC:PC Communications Error

But problems aside, I live there now. If you want to be my friend 😳, my ID is: 1227 6011 048


I normally don't do the self-analysis, why are we here thing, and certainly no self-promotion or "personal braaaaaaand". The joke's only funny until you die, then you leave a stink-bomb corpse and it's really funny, and then they shovel dirt in your face. Until then, I mostly do things I find fun and maybe post them for others.

But what is blogging for?

Social media in the form that Twitter and Facebook have produced, is now clearly seen a mistake; it used to be fun, and is easily compulsive, and I'm the next-to-last guy who could say with a straight face "don't do things that are fun but possibly dangerous to your body or mind", but the toxic side-effects have gone from heroin, to a cocktail of PCP, bath salts, and krokodil. It has turned and is eating your face. Get out while you still can.

Reading blogs is quieter. It can happen when you want, a pull request from a bunch of servers instead of a constantly pushing firehose. I can pick thru categories, since I organize feeds into a score of folders. Not everyone has a useful feed anymore, and there are times when a blog or comic stops updating the RSS and I don't notice until an annual sweep of stale feeds. I don't read everything, I read what I want and clear the rest.

My current OPML export has something like 1200 feeds, which is ridiculous, but with my organization it's not that bad. If I want to read comics, SF blogs, Mac news, dev blogs, etc., it all adds up pretty quick. Many only update a few times a year, which is probably not enough; I only keep a few "Tech Bullshit" blogs that spam more than a couple posts a day.

I used NetNewsWire back when Brent Simmons made it, but switched to various others when iPad came out. The NNW iOS rewrite and the years-delayed Black Pixel re-rewrite were unacceptable, but the Google Reader-pocalypse forced me to finally do something, so ever since I've been using FeedBin; apparently not the most popular since it costs $5/month (paying for the things you use! What a bizarre idea!), but a near-desktop quality interface with great keyboard controls, that works well in Safari, is more useful to me.

In the Dark Ages, Before Computers, you'd read, hear, or think of something, and then spend the next week telling everyone you met a distorted version of it, jabber jabber jabber. Some would write letters and then copy them for different correspondents, and the real maniacs would write letters or columns for newspapers or magazines; the Dragon Magazine Waldorf letters are archetypical.

Now we have the unlimited reach to annoy everyone with the noise in our heads. Many people use Twitter as a stream of consciousness of their food 🍔 and bathroom 💩 habits. It's too easy to type in a box and hit send. And if you "like" that person, and want to see anything halfway smart they write while distracted by everyone else's firehose, you also have to take their bathroom posts. UGH. You were so preoccupied with whether or not you could, that you didn't stop to think if you should..

Take my music posts (please!). On Twitter, I'd sometimes spam a music link every hour or more. Now, I typically have one song in mind, link the album, then use my amnesiac-encylopediac memory of the last 50 years of blues/rock/metal/electronica (a bit more for blues) to find a day's worth of similar albums. Then I keep the post open and hit links for iTunes. It reminds me of my teenage years, pulling a few vinyl or tape albums from my small library and spinning them in between bursts of radio; whole albums, every track unless something annoying was at the start or end of a side; I can't stand the random train-wreck of commercial radio. And my 20s DJing at http://kuoi.org/ with my playlist, I did a lot of deep cuts or half-albums. It's nice if someone else likes my music, but that's not why I post.

This post has been building for a day or two. I write a little, leave it in drafts, change the title, rewrite parts, find le mot juste, a few coherent thoughts, or Suck-like links to emphasize or subvert meanings. When I think it's worth reading, I'll hit Publish. Thinking and writing at any depth is simply impossible in the social media engines.