Hell yes. It will be really great to experience some consistency around aws api calls with a single cli experience. I love the boto project, but both the class structure and sporadic cli tools in the project take inputs in a non-uniform way that can be quite frustrating at times.
I'm really glad they went with Python on this one with the Apache license. This will definitely encourage a lot of active community contributions.
One thing I never liked about the current cli tools is that their output was not easily passed into other cli commands. Quite annoying to get a screen full of tabulated text and multli-line fields, when all you need a list of instance ids.
I'd be glad to see the old CLI tools die, because the damn things had to boot up a JVM for every invocation. Among other things, that made CloudWatch very hard to use from a t1.micro or m1.small instance: each call to PutMetricData used enough CPU to start the instance being throttled. (On a t1.micro I couldn't even post to CloudWatch once per minute: the throttled calls would take longer than a minute and start to overlap, exhausting the available RAM.)
Here's hoping that they add support for S3 soon. It's a shame that it's so difficult to leverage IAM Roles to bootstrap an instance. The very latest boto is the only tool I know of that supports S3 fetching using the STS credentials that you get from a Role.
I'm really glad they went with Python on this one with the Apache license. This will definitely encourage a lot of active community contributions.