From hearing the details it seems that there is no real limitation to what you can execute as long as it runs on the instance. I get the feeling that if you zipped up all of the parts of python or ruby you need to ru you could execute a script using either of them as long as you initiated it from your node script. The key word here is probably "support" and that may be more of an issue if you want to edit your scripts with their web IDE.
we are considering open sourcing the segmenter tool (3rd). As you can imagine it's very much tailored for our pipeline and as the internal tool built in ffmpeg matures, we think our solution will become of marginal value. I keep debating myself if/when to bite the bullet and try out the ffmpeg one.
The first tool is quite similar to the one that mau posted (https://github.com/danielgtaylor/qtfaststart). Given that we forked quite some time back, I'd suggest to start from that one since it has probably bug fixes on top of our version.
It is also worth pointing out that you can fly to DC and NYC in under 2 hours from Louisville. You can fly to Chicago and get there before you took off thanks to the time change. So you have access to pretty much any of the "best" of those things listed here in about 3 hours including the time it takes you to drive to the airport, get through security and board.
I will second this. At the bottom of this article there is a reference the article I wrote a while ago when Amazon released this feature. I was planing on doing multipart uploading at that time using the FileReader but there was a bug in the way S3 did CORS so I didn't want to continue until that was fixed. They fixed it and I never came back to it. Maybe be a good time to try it again. Resuming a partial upload seemed like a good win to me.
They got a free thumper from Sun through the "try and buy" program, loaded it up with customers, and ... failed to operate it properly. IIRC, it wasn't just a service outage - some data was irrevocably lost.
ZFS on Solaris was a non-beta, prime time product at that time, so it's not fair to blame it on "a ZFS thing". Deploying customers on loaner hardware is scrappy and admirable, in a way, but Sun wasn't giving those away two by two - there was no redundancy.
The joyent blog, in those days, alternated between enterprise cloud bullshit-bingo posts and facebook game development. I thought it was a clown operation back then and I suspect it still is.
ZFS was officially a non-beta, prime time product. In practice, apparently anyone who tested its robustness thoroughly before deploying it found that it tended to crash and burn at the first hint of trouble exactly like it did for them.