> > I think it's difficult nowadays to have wide consensus on this. An > annotation is a first-class construct and it's Java's way to be enhanced. > > In Scala events are pretty elegant when I look at Akka, but as I > understand they are not baked into the language; they are implemented on > the top of DSL-like flexibility that Scala offers (including operator > overloading). To me it's precisely what Java does, even though it's a > rougher (?) approach of course. >
Indeed, we've seen annotations as a facilitator for many things by now, many of which are characterized by the JLS and luminaries as being misuses. Don't get me wrong, I absolutely love runtime pluggability (Java's SPI is particular elegant and one of the few examples where it shines over C#), but annotations are used for far too much now. I still get shivers when I think about certain large complex applications which has IoC and AOP annotations sprinkles all over... horrible. > To me in the end the important part is that syntax is clear, semantics are > > precise and I don't have to do something strange to have it working. > Putting a jar in the classpath it's not strange. > Yeah but what happens when my module X has to be integrated with your module Y, through module Z? A lack of standards is far worse than an lackluster standard in the long run. Software is build for the long run. Anyway, we're digressing. I honestly have very little hope for Java to continue staying relevant given its history over the last decade and if I don't expect it, at least I won't get disappointed. :) -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/fHiHe95rrkcJ. 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.
