I’ve been having very good luck with requirehaml. I had been looking around at various templates, but none of them seemed to support compiling before delivery to the client. This script does that and compiles them into easily verifiable javascript files, packaged up to be included with my existing require.js AMD build.
So far, I haven’t actually had that much HTML to include, but hopefully that will change as my project takes shape and grows.
Now I just need to find something to do the same for SASS.
Now that require.js has reached 1.0, it’s probably time to start shouting its praises from every rooftop so that javascript library authors include support for it. Require.js is an implementation of the AMD draft specification which adds simple module support for javascript in the browser. This means no more namespace pollution (if you use it properly).
Unfortunately, we’re talking about web developers who don’t seem to understand basic principals like avoiding namespace pollution. I mean, how can you even have a conversation with someone with such a misconception of good practices?
I was really hoping that someone with such a worthy track record would have seen the light by now. Luckily the require.js guy himself is pushing for AMD support in Underscore with a new pull request. Once that is pulled in, it looks like Backbone is next on the list.
Since the next version of jQuery will have AMD support, I imagine that the rest of the libraries will follow since they seem to look up to jQuery for best practices.
It’s good to see that someone has taken up the GitX mantle, since the original hasn’t been updated since September, 2009. There have been a bunch of forks, notably brotherbard’s fork.
That’s about it. I’m still looking into how to setup the RVM equivalent for python, but it seems that community is still figuring out their tools and a clear solution hasn’t emerged yet.
It’s ten hours before the doctor induces my wife into labor. It’s only 9pm, but I’m bored and want to start a project. I also know that I shouldn’t since the next week will be very busy.
I used to have another blog at Penguin Sounds. I had this idea that I would put personal posts on taybin.com, and programming/professional posts at penguinsounds.org. But in the end it just split the effort on both blogs and confused friends and family.
So I’ve now imported the rest of the penguinsounds archives to this site and redirected the URL. The only downside is that I had one post with over a hundred comments from a couple years ago from when iMovie ‘08 was released to mass-disapproval.
There isn’t much documentation for using the two in combination, so I’m pretty much on my own here. As a result, the design and layout of this site will probably change as I learn more.
Managing Humans really needed a better editor. Maybe I’m not in the manager mindframe enough to understand it, but it jerked around and contradicted itself.
I’m hoping the Haskell book isn’t as disappointing. I’ve been wanting to understand functional programming for a long time, but never got around to picking up a book that explained how to model real programs that rely on input from the outside world.
There’s a new autoconf out, autoconf-2.63. It continues autoconf’s fine tradition of having the suckiest release schedule and quality of the GNU toolkit. You would think that they would increment the major number whenever they release a non-backwards compatible release, but they don’t for shear preversity. I guess 2.63 just rolls off the tongue, and I can’t blame them. The ridiculousness of having to test for different versions of your platform configuration tool boggles me. I’m at a loss for words at how much the autoconf maintainers have failed their core mission.
I’m not even going to go into their choice of m4 as the file format. That probably made sense at the time. But that the thing is implemented in sh is just stupid.
Really, what the autoconf maintainers should do is what the make maintainers never had the guts to do. Realize that their software is making the world a worse place, pick a worthy successor, and never update their project again. In my perfect world, autoconf is allowed to commit hari-kari. Meanwhile, automake is lined up against a wall and shot at dawn.
On the plus side, this might be the chance for everyone to finally move to a sane build tool like waf or cmake.
I’m so glad I’m not an Apple Release Engineer today. Four major releases today. iPhone 3G, iPhone Firmware 2.0, MobileMe, and iTunes 7.7.
It’s a huge task to synchronize all those releases and it eats up company resources like crazy. You have to have enough people to focus on each task separately.
MobileMe still isn’t working right. They’ve been extending the maintenance downtime further and further.