[paxys]

> MinIO as an S3-compatible object store is already feature-complete. It’s finished software.

I don't see how these two lines can be written together.

The goal is either to remain S3-compatible or to freeze the current interface of the service forever.

As it stands this fork's compatibility with S3, and with the official MinIO itself, will break as soon as one of them pushes an API update. Which works fine for existing users, maybe, but over time as the projects drift further apart no new ones will be able to onboard.

[chatmasta]

The S3 API is quite stable and most new features are opt-in (e.g. ApplyIfModified) or auxiliary (e.g. S3Tables). It’s highly unlikely that S3 proper will break backwards compatibility for clients with any future API change. So if all you need is basic object storage that works with existing S3 clients, then MinIO is enough. The fork just needs to keep CVEs patched and maintain community hygiene (accept new PRs for small bug fixes, etc.). And as the author points out, this is much easier in the age of AI than it might have been previously.

[teeray]

> The S3 API is quite stable

With so many things offering S3 compatibility, I’d say it’s de-facto standardized.