Qt should have a QIo like what KIO is. But much much better

We all know that Alexander Larsson won the battle of the virtual file systems. Today GLib's Gio with GVfs is massively better than KDE's KIO with its kio-slaves.

Any further discussion after about 15 years of debacle is more or less pointless: everybody and everything uses Gio with GVfs. Almost nothing uses KIO (except KDE's software titles). And KIO is completely unmaintained and its code is rotting.

Meanwhile almost everybody wants a virtual file system API from Qt.

I think its implementation should follow Gio's,  which unlike KIO's include a rich support for streaming.

I think the API should utilise the QPromise and QFuture  advancements that Qt finally has been making in its 6.x series.

And I think it's time to do it.

Perhaps firstly by wrapping GLib's Gio. And by that I mean to rid ourselves of Qt ideologies and allowing a GLib/Gio dependency. Until somebody makes a implementation that is pure to C++ without GLib (yes, whatever).

The problem, I think, with the whole silly debate is that for decades now: we are not making good abstractions that just work for the end-users of the Qt framework.

This end-user really doesn't care about this ideology, or lack of ideology. This end-user just wants a way to address a virtual file system.

I think the end-user is right to expect this in goddamn 2022.