Live data from Hacker News

Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

github.com

51–60 of 105 posts

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#52
You know what would be really awesome? Making a fuse-based drop-in replacement for mapping a folder to a bucket, like goofys. Maybe a node.js process can watch files for instance and backup, or even better it can back the folder and not actually take up space on the local machine (except for a cache).

https://github.com/kahing/goofys

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#54
post #40

for Node. These are nice projects. I had a few rounds with Rust S3 libraries and having a simple low or no dep client is much needed. The problem is that you start to support certain features (async, http2, etc.) and your nice nodep project is starting to grow.

for JS > It runs on Node, Bun, Cloudflare Workers, and other edge platforms

But not in the browser… because it depends on node.js apis.

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#55
post #52

You know what would be really awesome? Making a fuse-based drop-in replacement for mapping a folder to a bucket, like goofys. Maybe a node.js process can watch files for instance and backup, or even better it can back the folder and not actually take up space on the local machine (except for a cache). https://github.com/kahing/goofys

This seem completely unrelated to the goal of OP's library ?

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#56
post #11

Earlier quoted context omitted.

checksumming does make sense because it ensures that the file you've transferred is complete and what was expected. if the checksum of the file you've downloaded differs from the server gave you, you should not process the file further and throw an error (worst case would probably be a man in the middle attack, not so worse cases being packet loss i guess)

You need the checksum only if the file is big and you're downloading it to disk, or if you're paranoid that some malware with root access might be altering the contents of your memory.

I mean if a malware is root and altering your memory it's not like you're in a position where this check is meaningful haha

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#57
post #54
post #40

Earlier quoted context omitted.

for JS > It runs on Node, Bun, Cloudflare Workers, and other edge platforms

But not in the browser… because it depends on node.js apis.

Cloudflare Workers don't use any Node apis afaik

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#59
post #39

Earlier quoted context omitted.

Proividing built APIs to not rely on NPM is one of the most interesting aspects of Bun IMO.

Can someone explain the advantage of this? If I want S3 access, I can just use NPM If I don't want S3 access, I don't want it integrated into my runtime

Would you rather use an officially maintained solution or some random package by a random author who might abandon the project (or worse)?

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#60

> https://raw.githubusercontent.com/good-lly/s3mini/dev/perfor... It gets slower as the instance gets faster? I'm looking at ops/sec and time/op. How am I misreading this?

I read that as the size of file it's transferring so each operation would be bigger and therefore slower
Post reply on HN