Content pfp
Content
@
0 reply
0 recast
2 reactions

Stephan pfp
Stephan
@stephancill
Vendor-specific API built into a runtime feels really strange https://x.com/bunjavascript/status/1873234802675204106
9 replies
11 recasts
74 reactions

Stephan pfp
Stephan
@stephancill
Even weirder than vendor specific APIs built into low level SDKs :p
2 replies
3 recasts
22 reactions

Haardik pfp
Haardik
@haardikkk
Tbf most s3 alternatives follow an s3 compatible API
3 replies
0 recast
7 reactions

Kevin pfp
Kevin
@typedarray.eth
Not too strange imo, the S3 API is the de facto standard for cloud object storage. Bun comms could perhaps be more neutral tho. S3 is a (rare) positive example of a standard coming into clarity after many years of production usage, steered by a competent designer (aws). Contrast with the standard ethereum RPC.
1 reply
0 recast
2 reactions

Harris pfp
Harris
@harris-
don't they also have built-in sqlite support?
1 reply
0 recast
1 reaction

Tony D’Addeo  pfp
Tony D’Addeo
@deodad
https://x.com/bunjavascript/status/1873284653974778367?s=46
0 reply
0 recast
0 reaction

downshift - μ/acc pfp
downshift - μ/acc
@downshift.eth
this is a bad design decision and even worse precedent 🤦‍♂️
0 reply
0 recast
0 reaction

Arti Villa pfp
Arti Villa
@artivilla.eth
everyone needs storage. just because aws invented it doesn’t mean they own s3. it’s just storage.
0 reply
0 recast
0 reaction

Hoot 🎩 pfp
Hoot 🎩
@owl
The question is obvious: How much did AWS pay?
1 reply
0 recast
2 reactions

ns pfp
ns
@nickysap
more and more cases of this.
0 reply
0 recast
0 reaction