Curious to know how other #android (or #kotlin) libraries handle Android process death. Or do they?
I have an SDK that requires a suspended initialisation before being allowed to access other functions for that library. This is because a data set needs to be loaded. On process death the usual initialisation seems to be skipped causing users of my SDK issues.
I'm convinced this isn't something the SDK should be aware of but want to cover all bases thoroughly.
I'm very happy that I figured out how to place the icons in columns (responsive) and the names under the thumbnails. I find aligning things in Swing even harder than in CSS.
Demystifying GenAI and ChatGPT
-- harness the practical and pragmatic parts of AI
-- you don't have to run your own models and LLMs
-- call out to OpenAI straight from your Kotlin/Java SpringBoot codebase
-- the real magic is finding a good use-case
-- most of what you hear and see out there today isn't a good use for LLMs in the first place
In case you want to try an alternative JSON (de)serialization library for #Kotlin, Kondor https://github.com/uberto/kondor-json by @ramtop is great. No annotation magic, just functions explicitly defining the mapping. No external dependencies. As fast as Jackson.
TIL: 1. Kotlin Multiplatform takes advantage of Kotlin's ability to compile for several platforms, resulting in native libraries that may be used by native apps.
Kotlin's native approach allows for efficient execution at runtime, as it doesn't require an additional layer to communicate with device hardware and compiles to native binaries for faster execution.
++ Kotlin has an extremely clear codebase. React N. yoü have a worthy rival.
constants are weird in Kotlin. every language has one or two things that should be simple but are weird. I still love kotlin but still struggle with constants, and how copy/pasting files will drop them in IntelliJ every time because they are top-level and semi-classless