@tipsy I’m not sure of what is the best way.
The thing that kotlin uses properties instead of class attributes is very cool, but I think there was a reason if older languages made the choice of “private by default”.
So yes, it’s very cool because we don’t have to loose time at typing public a lot of times, and generating getters/setters (one lined for most of them), but I think that’s still a good practice to set to private what should be.
Maybe someone from JetBrains could tell us why they made this choice, and why Java (for example) made another ?