I've been using a simple Fabric script from http://ericholscher.com/blog/2010/nov/8/building-django-app-... to automate Chef deploys. Blueprint tried to install a lot of nonsense on my box, and I decided that learning Chef proper would be a much better investment of my time.
DevStructure co-founder here, sorry to hear about your experience. Not sure when you installed blueprint, but we've recently open-sourced it and it's been ported to python. Should require minimal "stuff" to use it. Let us know if you have any questions or problems and again my apologies.
It was not a reflection on your product. FWIW, I tried it out about 3 weeks ago, using the setup.sh script. I'm not even in a position to critique Blueprint, as I was only migrating one single Linode instance to another, and not even anything complex.
Thanks for the clarification. We did open-source it last week (so you had an older version) and accounts are no longer required, you can download/build/run it. A lot easier to use should you choose to try again. If you need any help with the migration, we're always around the chatroom.
There are plenty of cases where deployment script language matters. Usually they revolve around having lots of tools/objects/etc already written in a language, and want to incorporate them into your automation system. This is how I found fabric to begin with.
If you are interested to learn chef-solo/vagrant, please see http://news.ycombinator.org/item?id=2292140 (which I just posted). I'm planning to write an e-book on the topic.
Lately I want to experiment with Chef using blueprint [1]. What do you think?
[1]: http://devstructure.com/