Portable Kotlin vs "non-portable" Kotlin?
Which should I be using for versioned settings: portable Kotlin vs "non-portable" Kotlin? I couldn't really find any decision making guidelines in the documentation but I don't really intend to leverage the "portability" ever (I'll only ever have one server). It seems Portable Kotlin is what is being pushed by Jetbrains but it seems limited due the "portable" nature. By that I mean IDs aren't specified, changes from the UI show up as patches, etc. I'm not concerned with the differences in using portable vs non-portable but I just want to know what I should be using.
Please sign in to leave a comment.
If you would like to reuse the same files into multiple projects or multiple servers, you should be using portable. If you are keeping projects/configs small and/or separate in different roots, portable is still better.
If you are only going to have a single server and are going to be managing all projects within a single settings, you are probably better off using non-portable.
The difference isn't large, non-portable is more comfortable for some people as it provides a file/folder structure beforehand to follow, while the portable starts of as a single file that contains everything. It will require a larger effort to develop into a larger environment, as well as imposing some other requirements that don't really make sense on a more static environment.