I’ve mostly come to the conclusion that my implementation of an ORM wrapper is completely and fundamentally broken — it has turned into an amorphous unmaintainable mess of code and overcomplicated the build process while adding very little value to anything.

I also think the Routing subsystem is a little broken as well — the abortion of a Yaml parser is a terrible, unextensible hack. It would be really nice to have something which can serve as a generic configuration tool for not only routes, but schemas (if a reasonable ORM layer ever appears) and general configuration as well. The part of the Routing system which sits on that (effectively just a state machine to parse the request URI) is fine.

In light of this, I’m going to read over the Data.Data papers, which will (hopefully) supply a means to automatically marshall SQL result sets to output formats (through HStringTemplate or a JSON encoder).

In the meanwhile, I guess I should think about a useful project which I can actually apply this crap to so it isn’t just pointless learning exercises. Bleh.