garnaat

FWIW, Xerox shipped an all-Python product in 1997 called DocuShare. It is still being sold but was re-written in Java a few years later because they felt their customers wanted it to be more enterprisey. Today the use of Python would not be controversial at all so we have come a long way.

With boto, I battled for years trying to avoid any dependencies. But that has a lot of negative side effects, too. One of the great things about Python is the amazing variety and quality of libraries available. We decided to embrace that with AWS CLI. We have 10 direct dependencies. Four of those are our own packages that we decided to split to allow maximum reuse. Then there are fundamental things like requests, six, docutils. The rest are things that, we think, improve the experience. Virtualenv is an awesome way to manage this. I highly recommend it.

The rsync command uses a combination of file modtimes and file sizes as it's default algorithm. It's very fast and efficient. I agree, though, that like rsync, it would be good to add a --checksum option to the s3 sync command in AWS CLI. Feel free to create an issue on our github site https://github.com/aws/aws-cli so we can track that.

I still think the Amazon S3 API is really nice.

It's a chicken/egg problem in that developers are saying I'm not porting because no one is using Python 3.x and users are saying I'm not moving to Python 3.x because none of my packages are available.

I can't just move to Python 3.x and abandon 2.x. And I have not been able to find a way to have boto support both with the same code base. So, then it becomes a matter of maintaining multiple versions of boto. Just shoot me now. If the barriers weren't so high, more packages would be running in Python3.x.

"Wall of Shame"? Really?

As someone who's project appears on this list (and in the WRONG color) all I can say is that I don't think anyone is trying to dis Python 3.x. Support will come when a critical mass of developers are using 3.x. I know it's kind of a chicken and egg problem but this seems to be saying that it's the package developer's fault and I don't really think that's fair or true.

If you are interested in REST API's, the best I've ever read is "RESTful Web Services" by Richardson & Ruby.

Actually, I'm wrong. It's eleven 9's. http://bit.ly/ageV9D

I suppose it's possible but S3 is designed for nine 9's wrt to durability. There are > 100 billion objects and I'm not aware of any being lost due to AWS fault.

There was a pretty lively exchange on twitter last night regarding this. I strongly disagree with the AWS forum poster. EBS does not suck. In fact, EBS and other services from AWS and Rackspace provide the building blocks to allow you to construct incredibly scalable, available systems.

However, you have to accept that when you use IaaS you are taking on some of the operational responsibility and you have to know what you are doing or find someone who does. If this user had been snapshotting regularly to S3, the worst thing they would have experienced is a couple of hours of downtime. All of their data would have been safe and easily recovered.

They didn't do that and the worst case scenario that AWS clearly describes in it's docs (failure of MULTIPLE devices) happened. And it will happen again, someday. Accept that and accept that failure is a feature when systems are designed properly.

Variety is good but pushups are a fantastic core exercise. They really workout much more than your arms and you can do them anywhere. Plus, these workouts do build up a certain amount of aerobic value because they involve multiple sets with shorts rests in between.

I'm up to 75! But best to also do some squats, some situps/crunches, etc.

I have never seen a documented case of S3 losing data. Please provide references.

I have recommended to some customers that they back up S3 data to the S3 service running in another region. The new export service also provides a way to get physical copies of your data but, depending on how much data you have, it might not be practical.

The new planes like this Airbus do actually transmit real-time maintenance data. So, there were something like 10 transmissions from the plane that apparently include large amounts of data regarding the systems that were failing and when.