It's been awhile since I worked on a personal project.   I have an idea for a simple to-do list, just like everyone else's.  But mine will be better!  I promise!  It will!  Or, at least, it'll be mine.  Basically what it comes down to is that I hate every to-do list.  There are a few that are wonderful, but they're not portable.  There are a few that are portable, but none of them are wonderful.

After a few preliminary sketches, stealing from all the best, I created a new directory and installed grunt, gruntc (a bash front-end to grunt that will look for a file first, and use it instead of grunt.js; it uses a shadow .grunt.js file).  I've created a package.json file and a banner file (used by Grunt), called _Omnipotence**.  **_I've also created src and app directories, and installed Twitter Bootstrap as a vendor file. As I'm putting this project together, from the beginning, I start to feel a little overwhelmed.  Now, instead of require.js, there's this thing called "components" that TJ has put out.  It's designed to replace all of the ad-hoc construction we do with Javascript and make it systematic, but I barely know where to start.

I kinda want to use bacon.js in my project, but I wouldn't know where to start. I loathe grunt.js's opacity.   But Brunch's tersness hurts just as hard.  Makefiles were fairly explicit, but they don't handle the recursive issue of a standard build project.   Grunt-HAML is just broken; it doesn't seem to work with Grunt 0.3 at all, and with Grunt 0.4 it mangles and underscore code you may have wanted to deploy client-side.

Still, something resembling progress is being made.