<@U3W8YSSSV> The problem with Lombok is also that ...
# getting-started
r
@tipsy The problem with Lombok is also that it is a dirty hack using non-public, undocumented API of the Java compiler / the eclipse IDE - which I'd say is a pretty big reason why having this integrated into the language is the far superior way. I recently gave a talk to my department about Kotlin. We are already using different languages here, but only Java on the JVM so far, which some people are not willing to leave easily. I structured my talk to highlight the language features while making sure I always made the others imagine how they would go about doing the equivalent in Java. I also put a lot of emphasis on the seamless interop and the tooling support - seeing a huge Java class from our codebase be converted to a concise Kotlin file and being able to inspect the bytecode and decompiled Java equivalent created some real "Wow" moments for my colleagues. We are still not going to use Kotlin in production code right away, but I've gathered enough interest from the others that it will be used for some internal projects for further evaluation now.
👍 2