30 ms·
Take a step up the enlightenment ladder and put a type dynamic language on top of java. Lombok is silly and makes your object’s serialization capabilities a di
by humbleMouse 5y ago
Take a step up the enlightenment ladder and put a type dynamic language on top of java. Lombok is silly and makes your object’s serialization capabilities a dice roll. Keep annotations to a minimum and bring in a type dynamic language (groovy, kotlin, etc)
- AtlasBarfed 5y agoYes, groovy + @CompileStatic is comprehensively better than java with little to no performance loss.
- deleted 5y ago[deleted]
- humbleMouse 5y agoExactly.... all the benefits of dynamic, with all the benefits of static compilation.
- kaba0 5y agoI have no problem whatsoever with groovy, but I heard “all the parts Java programmers hate about JavaScript with all the part JavaScript developers hate about Java”, and I had to reread your reply to realize you are not writing something like this :D
- spicybright 5y agoI find static languages much easier for large code bases. Also, can you code dynamic features with java's reflection API? https://docs.oracle.com/javase/tutorial/reflect/index.html https://docs.oracle.com/javase/tutorial/reflect/index.html
- dunefox 5y agoKotlin is statically typed. It has full type inference, though (AFAIK).
- yawaramin 5y agoKotlin is statically typed. Perhaps you mean Clojure.
- dunefox 5y agoLike this? https://common-lisp.net/project/armedbear/ https://common-lisp.net/project/armedbear/
- wtetzner 5y agoI've used plenty of dynamic languages before, but I don't see how that would help in this case. The point is that I wanted statically typed records, which a dynamic language won't give me. Java has added syntax for defining records now, which is great, but I'm not (yet) able to use the latest version. > makes your object’s serialization capabilities a dice roll Not sure how? The effect of @Value is documented.