The aim is to try to avoid polluting the global wordlist with routing
The alternative would be to have users simply define words that match
their routes, e.g.:
( some definition of hi's handler )
I'm still not entirely convinced that the above method isn't a better
First, define a user-facing word that takes a port and subsequently
starts the server (using gforth's unix/socket.fs).
Second, start defining a user-facing word for specifing routes and their