Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the author is not aware that most modern apps don’t interface with traditional files. Many modern apps rather use S3 with presigned urls.


Maybe, but the end user of a browser based application (what this post feels like it references) deals with regular files served over HTTP still. Its source may be S3 in the end, but ultimately it's webservers and files, be they self hosted or one of the major content distribution networks' servers.

And that's absolutely fine, it's simple, highly optimized, standardized, etc. S3 blobs aren't and except for very specific use cases I wouldn't use it for serving files to end users.


I think you've thrown around the words 'most' and 'many' a little too freely.


Not everyone moves all their applications, files, kitchen sinks and glasses to cloud. There are still tons of traditional systems out there, and there's a small requirement for many of these organizations to have local, object storage systems.


... in corps hn crowds hang; in companies we consult at (very large to very small), things are very different. From nfs, nas/san to just the filesystem. S3/etc is still rare I would say for where we go.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: