A modern programming language that makes developers happier.

kotlinlang

Looking to migrate (with KMP in mind) from using <http://java.io|java.io>.* in my Android app to using either <http://kotlinx.io|kotlinx.io> or okio. I noticed <http://kotlinx.io|kotlinx.io> doesn’t support much in the way of system file operations (like delete). However, with ktor recently switching from okio to <http://kotlinx.io|kotlinx.io> should I consider okio as a no-go and instead place my bets on <http://kotlinx.io|kotlinx.io> with anticipation of upcoming expanded functionality. I’m not in any huge rush.

I burned my fingers with <http://kotlinx.io|kotlinx.io> and partly had to switch back to Okio. Conceptually they are very similar but at the moment Okio still provides a lot more functionality. I’d recommend to start with Okio and later switch to <http://kotlinx.io|kotlinx.io> if they are more feature-complete. If, however, you only have very basic IO requirements, you could go with <http://kotlinx.io|kotlinx.io> right away. (<http://kotlinx.io|kotlinx.io> does provide a function to delete a file though: <https://github.com/Kotlin/kotlinx-io/blob/master/core/common/src/files/FileSystem.kt>)

Thanks, yes I see it supports a lot more than chat gpt originally implied. I do find myself writing a lot of extension functions though. e.g. `Path.delete()`

So do I :wink:.
```fun kotlinx.io.files.Path.toOkioPath(): okio.Path = this.toString().toPath()

fun kotlinx.io.files.Path.writeString(content: String) = SystemFileSystem.sink(this).buffered().use { it.writeString(content) }
fun kotlinx.io.files.Path.writeBytes(content: ByteArray) = SystemFileSystem.sink(this).buffered().use { it.write(content) }

fun kotlinx.io.files.Path.readString(): String = SystemFileSystem.source(this).buffered().use { return it.readString() }
fun kotlinx.io.files.Path.readBytes(): ByteArray = SystemFileSystem.source(this).buffered().use { return it.readByteArray() }```


Are these valid? Just curious if I might be missing something in the null case.
```fun Path.isDirectory(): Boolean = SystemFileSystem.metadataOrNull(this)?.isDirectory == true

fun Path.isFile(): Boolean = SystemFileSystem.metadataOrNull(this)?.isRegularFile == true```

It probably works but I prefer this variant:
```fun Path.isDirectory(): Boolean = SystemFileSystem.metadataOrNull(this)?.isDirectory ?: false
fun Path.isFile(): Boolean = SystemFileSystem.metadataOrNull(this)?.isRegularFile ?: false```
