On Sep 3, 10:15 pm, Reinier Zwitserloot <[email protected]> wrote: > That's what makes lombok so different, and that's perhaps why the > lombok discussion group already has more posts in it inside of a month > than kijaro's in its 2 years. You can actually use it, right now, on > your day to day projects, without having to completely change your > development environment (including IDE, build scripts, etcetera).
Really a great idea - I took a short look at Lombok and for instance this feature here: http://projectlombok.org/features/Cleanup.html One question: Whoever really developing in Java for a longer time (longer than a month) is still coding something like the sample given at the link above? - The very first thing I have written is a wrapper method for such cases and I never ever need again to write such a shitty code portion - yes, that close operations themselves can cause errors again is shitty, but I even understand the idea behind it and I accept it as ok! - But this does not mean that I cannot wrap this into a one-liner! Another sample: http://projectlombok.org/features/Data.html Sorry, but building hashcodes is always not necessarily built again and again the same way. For a bunch of such annoyances I have built a library containing a lot of such helpful static methods that solve a lot of those according to my personal favor. I am really annoyed of such critics of the language because with a few minutes of work such things get a one-liner for your future use, so why bother? In all more than 10 programming languages used so far in my life I found annoyances everywhere and I am quite sure that Scala have it's own which I discover when working for about a month with it. I am sure that programming languages have still potential to be improved but there are also things that are just decisions between pro and contra. Look at GWT and Wicket. Both make sense and have different approaches with advantages and disadvantages. On framework or library level you can easily choose that what fits your needs but when it comes to core languages you can't make everything a matter of choice. You must decide whether to implement it that or another way. Java somehow also wants to keep the core simply with not too many possible variants of how something could be written. I think it is important to keep the core language simple so that it can be easily learned by the younger people growing up and learning. If you make a programming language too complex you will have in a 20 years only a very few people left who really know the language. Please don't get me wrong I am also happy about language improvements - as for instance using strings in switch statements - although this also can be workarounded by using enums. To have such enhancements as libraries that you can include then it is awesome - because everybody who wants to use it, can use it - and for those projects where it makes sense. Lombok offers this as far as I have noticed which is cool! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
