Kanbaru 🌟 (one hikari of too many)

deleted the iOS/Android file management thread because it’s too complex a topic to do justice in like four tweets

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

‪both iOS and modern Android’s file management are aggressively sandboxed, but somehow modern iOS manages to do it in a more comprehensible way, and they have made things easier for app developers rather than harder‬

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

the thing I’m actually annoyed at is Android trying to kill the traditional filesystem API (POSIX etc). this is extremely annoying if you are writing a cross-platform app, especially since Android used to let you do useful things with those.

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

meanwhile hell has frozen over and now iOS lets the user just… move files in and out of apps’ sandboxes. they can just open the Files app and move… files… around. and the app can simply access those files with POSIX APIs.

if only iOS allowed side-loading, I’d make apps for it

1 replies →
1 replies

Saagar Jha

(replying to Kanbaru 🌟 (one hikari of too many))
@hikari If you use the POSIX APIs bad thingsâ„¢ happen

Saagar Jha

(replying to Saagar Jha)
@hikari (notably without file coordination you may have the file yanked out under you or get a stale copy)

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

in general I think Android is designed to antagonise anyone whose favourite programming language isn’t Java, which incidentally includes almost all game developers.

1 replies →
1 replies

Saagar Jha

(replying to Kanbaru 🌟 (one hikari of too many))
@hikari Android is definitely designed to antagonize Java users

Kanbaru 🌟 (one hikari of too many)

(replying to Kanbaru 🌟 (one hikari of too many))

s/Java/JVM-based/