3 ms·
It wouldn't be an AWS announcement without a whopper of a caveat, it's like the Amazon equivalent of Google canceling things.
by jjoonathan 4y ago
It wouldn't be an AWS announcement without a whopper of a caveat, it's like the Amazon equivalent of Google canceling things.
- quickthrower2 4y agoTo be fair it sounds like this isn’t for that use case.
- kjuulh 4y agoAWS really does have its own quirks as a company. - The tools feel fragmented, not aligned and often don't compose well - Always sharp corners (Billing, ops, you name it) - Products in various state of usability / maturity, sometimes a product is launched by barely usable. I've never worked for Amazon, but if what is said about amazon is true, then the culture is reflected in their products, teams siloed owning their own services, then it does make sense that their services have those quirks.
- sudhirj 4y agoThat comparison seems unfair... AWS has a habit of launching early and iterating, and they almost never shut stuff down. In this case it's a filesystem implementation of a HTTP API, so the capabilities reflect the main API. Deciding to build and launch reads before writes isn't really a bad decision, it helps those who have the read use case try this out and give feedback immediately.
- ochoseis 4y ago> In this case it's a filesystem implementation of a HTTP API When you put it like that, it makes me wonder why they don't support WebDAV.
- sudhirj 4y agoI think there’s a bunch of gateways available already. The example use case for this seems to be mounting a 10 petabyte “hard drive” with CSVs to a reporting machine.
- deleted 4y ago[deleted]