1 - Machines use a Unix filesystem model even cruder than the Multics model it was derived from
2 - Network services and especially micro services essentially use an object model (mostly JSON)
3 - And with phones, sandboxes, containers and security concerns, applications are reverting to file silos (where a given app's data won't interoperate with other applications). This happens at a macro level too where the FBs of the world understandably want to rope you into their "walled silo".
Is it even possible to embrace a more flexible and powerful model at this point or are we stuck?
For the majority of people, the benefits of Facebook's walled garden approach are cheap, immediate and easy to understand. The disadvantages are only problems for a minority. What's more, Facebook can afford to hire a whole marketing team to promote its approach.
Until someone can show concrete benefits for the masses, we will continue in the current direction.
I believe that as long as these issues remain discussable, even if only in obscure academic and eccentric circles, at some point some ambitious person will find a solution. This might take 5, 20 years, 50 years, 2000 years I don't know. But I believe in the long-term.
1 - Machines use a Unix filesystem model even cruder than the Multics model it was derived from
2 - Network services and especially micro services essentially use an object model (mostly JSON)
3 - And with phones, sandboxes, containers and security concerns, applications are reverting to file silos (where a given app's data won't interoperate with other applications). This happens at a macro level too where the FBs of the world understandably want to rope you into their "walled silo".
Is it even possible to embrace a more flexible and powerful model at this point or are we stuck?