Here's what I don't like about Kotlin. It's huge. This makes it hard to learn, and harder to maintain. One of the things I love about Java is that it's a small language, and it's very consistent in how things get done. They deliberately left out features like operator overloading, which C++ users found to be a huge pain in the buns, a source of bugs, and a maintenance headache. C++ is huge, and tried to be an "everything but the kitchen sink" (EBTKS) language, which is why a lot of C++ developers moved to Java. Now Kotlin is trying to be EBTKS, too, and it will cause headaches and will one day inspire people to move to some newer but not-yet-invented language.
The software world could really use a strongly-typed, rigorous language that was far less verbose and could lead to rapid development without giving up error-catching features (like strong typing). Dynamically typed languages have shown the demand for a good rapid-development language, but in my experience with them, version one goes very quickly, and version two is a huge headache, especially when it's done by a new team. I was hoping Kotlin would be that rapid-development, safe language that led to maintainable code, but I've grown very discouraged.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Here's what I don't like about Kotlin. It's huge. This makes it hard to learn, and harder to maintain. One of the things I love about Java is that it's a small language, and it's very consistent in how things get done. They deliberately left out features like operator overloading, which C++ users found to be a huge pain in the buns, a source of bugs, and a maintenance headache. C++ is huge, and tried to be an "everything but the kitchen sink" (EBTKS) language, which is why a lot of C++ developers moved to Java. Now Kotlin is trying to be EBTKS, too, and it will cause headaches and will one day inspire people to move to some newer but not-yet-invented language.
The software world could really use a strongly-typed, rigorous language that was far less verbose and could lead to rapid development without giving up error-catching features (like strong typing). Dynamically typed languages have shown the demand for a good rapid-development language, but in my experience with them, version one goes very quickly, and version two is a huge headache, especially when it's done by a new team. I was hoping Kotlin would be that rapid-development, safe language that led to maintainable code, but I've grown very discouraged.