Python has only one way of saying 'there is nothing here': None. Java has the keyword 'void' and the value 'null', kotlin has Unit, Nothing and null. What is the actual difference in meaning for all of these? Python None Kotlin Unit, null and Nothing Java void and null The concept of 'Nullable' Null Safety… Continue reading Nullable, null, None, Unit, Nothing and void: the many faces of nothing
This page will serve as repository of limitations found when attempting to move kotlin code to python code. Some limitations are a natural consequence of moving to static types, others are effectively inherited from Java. The list here is based on placing those I find most significant at the top, and the further down the… Continue reading Kotlin Limitations vs Python
There is common belief that after an initial very agile development period, "grown up projects should switch to a static typed language". This also raises the question, "are type-safe languages less suitable for early stage development?" This page considers the evidence for these beliefs, plus considers if there is a benefit to starting dynamic and… Continue reading When will your project ‘grow up’ and require typesafe code?
Topics for this section: Class Level Objects & Companion Objects: Key Terminology. the simplest case - one object type Python - an additional object type requires precise terminology Kotlin: the companion object equates to the Python class object Class & Companion Variables and Methods vs instance methods and variables Terminology for Clarity: Class Level Object,… Continue reading Class Level Objects, Companion Objects & Instances
Any software team who is considering moving to kotlin, must by definition, be currently using at least one alternative language. To change languages, and ecosystems, is a big step. One of the key features of kotlin is how easily and seamlessly a project can migrate from java. Currently, that same ease of migration is far… Continue reading Implementation: what is a practical approach?