I'm always fascinated by how people choose to live while traveling, so thanks for sharing! Curious though how you handle food. Do you prepare your own or eat out? Judging from the lack of utensils, etc I imagine the latter.
If he's in Thailand (which I'm assuming from him having a Thai Macbook), then it's actually much cheaper and more convenient to eat out, at least anywhere outside Bangkok. Same situation in Cambodia -- I initially attempted to cook a lot here but gave up since it's cheaper to eat the food in my alley and around the market near my apartment and it tastes better than anything I can cook.
Why thank you kind sir! Myself (primary dev) and the few people I know who use it agree :)
We've been intentionally quiet, to be honest. Lots of things to get straight since the initial release, much of which was done in 0.8. We're at a more stable point now and I hope to see some momentum build soon. Of course, any ideas you have would be welcome.
I can't speak too intelligently about how Sinatra is architected, but here's a bit about how Pakyow handles routing.
A route is just a regex and set of functions (blocks, procs, whatever). When a request comes in, the following things happen:
1. An AppContext instance is created that contains the request's state
2. Route is matched (narrowed by method then match on path)
3. Each function is evaluated within the context
Hooks, etc aren't special things and are just functions at a particular location in the set. This set is built at startup, so there's no object creation to fulfill a request (except the Request/Response/AppContext objects). The routing bits of pakyow (pakyow-core) are very close to the Rack metal.
Aside from routing, nearly everything in Pakyow is middleware. This makes it easy to completely remove (not just disable) components like static file handling, logging, etc.
He's proven his belief in the product by taking a stand. This is already more than most could hope to do. For that I offer my applause. If this isn't a next big thing, it at least offers a life changing mindset. For that I offer my thanks.
I've noticed that making the mental switch from writing code to committing it costs quite of bit of time throughout a day of development. A more intuitive interface would remove the need to make the mental switch. This interface feels much more intuitive to me -- great job.
My dad did the same thing. Thinking back, the first thing I remember doing on a computer is writing a calculator in BASIC. Before games or anything. To this day I still choose coding over games (ok, most of the time).
