Re:400 reasons to not use Microsoft Azure
by notpushkin on Friday February 28, 2025 @09:49PM
(#43215171)
I think this happened a few times, but given there are many S3 clients, they can’t keep doing thiat or there will be a backlash.
Although perhaps it’s about time we made a proper standard based on S3, yeah.
Re:400 reasons to not use Microsoft Azure
by immibis on Saturday March 01, 2025 @09:32AM
(#43219559)
It has, but that's not exactly on S3 is it?
The S3 system is proprietary to Amazon, and it's your fault if you're not using Amazon but you're relying on Amazon to not change it anyway, because they have no obligation to you.
The concept of object storage is not proprietary. You should be able to change your code to use a different object storage provider.
Re:400 reasons to not use Microsoft Azure
by darknavi on Saturday March 01, 2025 @09:05PM
(#43226399)
I didn't mean to throw any shade at S3. It certainly isn't their fault that people use their private protocol on other projects.
I was trying to point out that S3's protocol is "proprietary" so if you're using it you're still (somewhat) using "proprietary bullshit" in your stack!
Re:400 reasons to not use Microsoft Azure
by notpushkin on Sunday March 02, 2025 @12:14AM
(#43227607)
I mean yeah, it isn’t really open – but it’s the informal “standard” that everyone is using nowadays. You can’t really expect every cloud provider and every app to just switch to WebDAV or something (though we can push for a gradual change here somehow!)
> S3
Hasn't this recently been an issue where Amazon arbitrarily changes the S3 contract and all software following it as a spec has to play catch-up?