alamb commented on issue #268: URL: https://github.com/apache/arrow-rs-object-store/issues/268#issuecomment-4373249236
> I would love to figure this out. As @trungda said, there are a bunch of useful things that a lot of us are having to write over and over again. IMO, it's important for the success of this project to offer such features. This topic is related to https://github.com/apache/arrow-rs-object-store/issues/14. I agree that common patterns (e.g. rancing reads, coalscing requests, local caching, retry policies, deterministic LocalFileSystem, etc) are all valuable and I encourage anyone with the capacity to make a public library and open source it -- I think you would find many users. > LLMs are pretty good at impl ObjectStore now. I like to believe this is also related to our keeping the ObjectStore crate relatively focused and not letting it expand out of control in terms of features and functionality. This crate sets the APIs and enough implementation to get you started. Its design also allows easily extending the capabilities when you need something more advanced > Man, it's a sad world but I guess this is an industry wide question. I can get LLM implement this pretty fast too. Yes for sure it is an open question. The question is will we need a new model to maintain LLM generated software -- I think well be discovering this over the next year or two -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
