Problem with static elements in my S3 Bucket in AWS

Well, I'm still in the process of learning how to make a media source driver.

In any case, I'll still have to figure out how to get around the local filesystem limitation of static elements and static resources. I can't figure out what they were thinking when they made that check using is_file() before saving it - or at all, for that matter. Just because the file is checked before the element is saved doesn't mean that it doesn't get deleted or moved later. It kind of looks like static elements and media sources weren't really integrated very well. Of course, static resources and media sources weren't integrated at all. I think static resources were added before media sources, and they just never got hooked in.

A perhaps slightly related question to the work Susan is doing.

In looking for a way of supporting hooking into multiple cloud-based storage systems, I stumbled across Flysystem ("many filesystems, one API") and its set of connectors / adapters. I believe the development in question is targeted to the Laravel framework. Is anything similar in the works for ModX? Or perhaps more to the point, are there any known (or suspected) issues / gotchas that someone trying to make use of this code within a ModX project should be aware of?