52
Beginning with Kotlin and it's...
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Jan 2024
52 points (88.2% liked)
Programmer Humor
32380 readers
990 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Kotlin is the wave of the future. I still use Java, but I'm transitioning into using Kotlin for backend services. The devs are my work have been moving the app codebase to Kotlin for a couple of years (over a million lines) and it's pretty nice. You reduce a lot of boilerplate and the code can be a bit more dense.
Ok, so if it's the new standard then I should go with Kotlin. By boilerplate, do you mean a part of the code that makes java a little too heavy?
I don't know if this is the proper definition but I think of boilerplate as the code that's not directly related to business logic. An example I can think of in Java that's a lot nicer in Kotlin is setting all the instance variables in the constructor.
The names and types of the variables are important and useful for understanding the business logic but the actual constructor definition doesn't tell you anything if it's just assigning the constructor parameters.