Live data from Hacker News

Amazon S3 Path Deprecation Plan – The Rest of the Story

aws.amazon.com

61–70 of 146 posts

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#61
post #50

Kind of tangential, but is Bezos a programmer type? I thought he came from banking or the big 4. I’m curious if the “malloc for the internet” bit is verbatim.

I don't think Jeff is a programmer, but I think he is very smart and his success shows that he can understand and create businesses around lots of different types of concepts and ideas. I imagine in reality there is some amount of collaboration that happens before Bezos spouts off something like "create a malloc for the internet", but in any case, it's very strong for his brand of leadership that the lore states it c…

He's literally an EE/CS Major. He's a programmer at heart. His technical depth is key to a lot of Amazon's biggest successes.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#62
post #44

This is interesting for a few reasons. IMHO, the original deprecation plan was reasonable. Not generous, but reasonable. Especially compared to what other cloud providers (eg. Google Cloud) have done. It did seem like a diversion from their normal practice of obsessively supporting old stuff for as long as possible, but it really wasn't too bad. Responding to feedback, publicly, and explaining what they were trying t…

How was the original plan “reasonable”? S3’s FAQ talks about durability in terms of tens of thousands of years https://aws.amazon.com/s3/faqs/ . To honor that claim, AWS has the burden to support v1 URLs until the end of the internet.

Storage durability has nothing to do with this. Changing how you access data saved in storage is a reasonable change to keep up with the evolution of networking technologies.

The change here was deprecating an access pattern, not destroying data or anything remotely similar.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#63
post #44

This is interesting for a few reasons. IMHO, the original deprecation plan was reasonable. Not generous, but reasonable. Especially compared to what other cloud providers (eg. Google Cloud) have done. It did seem like a diversion from their normal practice of obsessively supporting old stuff for as long as possible, but it really wasn't too bad. Responding to feedback, publicly, and explaining what they were trying t…

How was the original plan “reasonable”? S3’s FAQ talks about durability in terms of tens of thousands of years https://aws.amazon.com/s3/faqs/ . To honor that claim, AWS has the burden to support v1 URLs until the end of the internet.

It's pedantic, but durability has little to do how the object is routed. The object is still there.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#64
post #47

Earlier quoted context omitted.

There's a book out there that points to my website. I wish they had just mirrored it. My website has been dead for a few months, and some O'Reilly book has a dead link.

I just now realised that if the web required two-way links there would be no way to put them into books! Some context: Back when the www was first released the most common criticism was the lack of back links. This is such a stupid and obvious deficiency that it really wasn't worth even looking into a system that was an obvious stillbirth. It wasn't just the "experts" saying this, but so many of them did because it w…

It is a shame that OSI didn't happen though and instead we have an ad-hoc mess of layered cake without clear boundaries as demonstrated by OSI Model.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#65

Earlier quoted context omitted.

How was the original plan “reasonable”? S3’s FAQ talks about durability in terms of tens of thousands of years https://aws.amazon.com/s3/faqs/ . To honor that claim, AWS has the burden to support v1 URLs until the end of the internet.

Storage durability has nothing to do with this. Changing how you access data saved in storage is a reasonable change to keep up with the evolution of networking technologies. The change here was deprecating an access pattern, not destroying data or anything remotely similar.

The distinction is academic if you don't have the ability to change the URL.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#66
post #60
post #50

Earlier quoted context omitted.

I don't think Jeff is a programmer, but I think he is very smart and his success shows that he can understand and create businesses around lots of different types of concepts and ideas. I imagine in reality there is some amount of collaboration that happens before Bezos spouts off something like "create a malloc for the internet", but in any case, it's very strong for his brand of leadership that the lore states it c…

1.) He graduated from CS at Princeton. 2.) Only an actual programmer would know what malloc is and how it works (he knows what it is exactly since he has the idea "malloc for the web")

Point taken, I didn’t know Bezos had an engineering background! Amazing.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#67
post #61
post #50

Earlier quoted context omitted.

I don't think Jeff is a programmer, but I think he is very smart and his success shows that he can understand and create businesses around lots of different types of concepts and ideas. I imagine in reality there is some amount of collaboration that happens before Bezos spouts off something like "create a malloc for the internet", but in any case, it's very strong for his brand of leadership that the lore states it c…

He's literally an EE/CS Major. He's a programmer at heart. His technical depth is key to a lot of Amazon's biggest successes.

Wow! News to me. Thanks for letting me know.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#68
post #34

Earlier quoted context omitted.

> It actually helps tremendously, since at the very least now there can be a "black market" for legacy (pre-Sept-2020) buckets Err, no, countries will just block the legacy bucket URL style and say that only the bad guys would still be using it.

That would mean they are blocking all S3 buckets indiscriminately.

Couldn't they just middle-man the traffic and block specific URLs?

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#69
post #64
post #47

Earlier quoted context omitted.

I just now realised that if the web required two-way links there would be no way to put them into books! Some context: Back when the www was first released the most common criticism was the lack of back links. This is such a stupid and obvious deficiency that it really wasn't worth even looking into a system that was an obvious stillbirth. It wasn't just the "experts" saying this, but so many of them did because it w…

It is a shame that OSI didn't happen though and instead we have an ad-hoc mess of layered cake without clear boundaries as demonstrated by OSI Model.

If you want low performance, that’s one way to get it.

Re: Amazon S3 Path Deprecation Plan – The Rest of the Story

#70
post #64
post #47

Earlier quoted context omitted.

I just now realised that if the web required two-way links there would be no way to put them into books! Some context: Back when the www was first released the most common criticism was the lack of back links. This is such a stupid and obvious deficiency that it really wasn't worth even looking into a system that was an obvious stillbirth. It wasn't just the "experts" saying this, but so many of them did because it w…

It is a shame that OSI didn't happen though and instead we have an ad-hoc mess of layered cake without clear boundaries as demonstrated by OSI Model.

I don't agree: the OSI protocols were the classic camel-is-a-horse-designed-by-committee: heavyweight and looked like a pain to use. Looked like, as I never saw a working stack.

The IETF/RFC/Working Code/Interop(RIP) approach has given V4 incredibly long legs. At least the OSI model itself kinda survived.

Post reply on HN