5 ms·

As a non-Java dev, Lombok seems like the kind of thing that could only be tolerated by Stockholm syndrome java devs :/ I mean, it's a clever solution and the s

by s4vi0r 9y ago

As a non-Java dev, Lombok seems like the kind of thing that could only be tolerated by Stockholm syndrome java devs :/ I mean, it's a clever solution and the site/documentation is great. But tossing around annotations everywhere feels hacky as hell, not to mention that it only works with IDEs. I'm sure the combination you mentioned approaches Kotlin in terms of features and QoL improvements, but it's just so much nicer to have these things built into the language. Plus, Lombok is mostly constrained to boilerplate reduction - Kotlin may not be as "crazy" as Scala, but it still has some really nice modern features that java doesn't have/can't have/won't have for a long time.

mschulze 9y ago
> ...not to mention that it only works with IDEs. That's not true. Lombok is an annotation preprocessor. That means it is running with javac which is independent of any build tools or IDEs. As long as it is on the classpath when compiling (-cp flag of javac) it works. Of course for code completion you need an editor that is aware of Lombok / uses the compiled bytecode for that.
59nadir 9y ago
I think this is the case with most JVM languages, to be honest. As someone who has done some Java but would never do it willingly as part of a hobby project or the like I think Kotlin and pretty much every other JVM language is a huge step up from Java. When you're already knee deep in it I suppose you're bound to have a less enticing reason to use the other languages. That being said, I don't see how you can look at the feature list of Kotlin and play around with it without seeing how it's obviously a much better language.
stickfigure 9y ago
As a polyglot, I don't understand your problem with annotations. These really aren't different: @Getter @Setter String foo; attr_accessor :foo It's unfortunate that Java chose the silly capitalization convention for properties instead of something more structured like C#'s get/set, but that's really an aesthetic complaint.

by s4vi0r 9y ago

mschulze 9y ago

> ...not to mention that it only works with IDEs. That's not true. Lombok is an annotation preprocessor. That means it is running with javac which is independent of any build tools or IDEs. As long as it is on the classpath when compiling (-cp flag of javac) it works. Of course for code completion you need an editor that is aware of Lombok / uses the compiled bytecode for that.

59nadir 9y ago

I think this is the case with most JVM languages, to be honest. As someone who has done some Java but would never do it willingly as part of a hobby project or the like I think Kotlin and pretty much every other JVM language is a huge step up from Java. When you're already knee deep in it I suppose you're bound to have a less enticing reason to use the other languages. That being said, I don't see how you can look at the feature list of Kotlin and play around with it without seeing how it's obviously a much better language.

stickfigure 9y ago

As a polyglot, I don't understand your problem with annotations. These really aren't different: @Getter @Setter String foo; attr_accessor :foo It's unfortunate that Java chose the silly capitalization convention for properties instead of something more structured like C#'s get/set, but that's really an aesthetic complaint.