Hi Nice Robot,
Once again thanks for your honest opinion.
As per my response to your previous comment https://medium.com/@elye.project/hi-nice-robot-8f1a2ce9311f, which has pointed out that
- You provided a link that clearly states Kotlin public interfaces are public, but you wrongly wrote them as for being private by default
- You misunderstood my intent of not having to explicitly state something as default, to thinking me advocating one should have public interfaces by default.
I couldn’t blame you for misjudging me as naive. I sincerely appreciate your simple thinking and transparency in sharing your thought.
I have coded C++ professionally in the past, and hold on to those standard practices, and provide feedback on code review, challenge on why the rules existed. I transition into Java, which inherits lots of C++ attributes. And now I’m into Kotlin and Swift, which has evolved and taken more modern language convention.
My initial transition into modern programming languages, I struggle to comprehend why the new way, while we have some existing practices which is good. But now, after a while, I start to see much clearer why and how it is the way it is.
I have been in both camps, and hence I comment based on my experience on them. I found many who find it hard to comprehend the newer approach are those who still working on the more conventional languages.
My recommendation is that, do explore and learn some new modern languages, and mingle with the experienced developers of those fields. Once you get acquainted with the modern languages, then you’ll get a better sight of both worlds.
