Comment by hsbauauvhabzb 6 days ago
I found the words used to describe this jarring - to me it makes sense to have an s3 client on my computer, but less so client side on a webapp. On further reading, it makes sense, but highlighting what problem this package solves in the first few lines of the readme would be valuable for people like me at least
I think if you asked the average IT person what those buzzwords mean, you’ll find the answer unclear…
I was responding to this:
> to me it makes sense to have an s3 client on my computer, but less so client side on a webapp
The relevant audience in this situation is not the average IT person, but a person who might mistake this for client-side web app functionality.
If you think that something might run in the browser, then “no browser support!” is not complicated jargon that you won’t understand.
I have a good suspicion this has been written with help from an LLM. The heavy use of emojis and strong hyper confident language is the giveaway. Proof: my own repos look like this after they’ve had the touch of cursor / windsurf etc. still doesn’t take away if the code is useful or good.
> to me it makes sense to have an s3 client on my computer, but less so client side on a webapp
What do you mean with a webapp?
I think “for node and edge platforms” and “No browser support!” makes this pretty clear? Those are in the title and first paragraph.