4 ms·
I was a little bit confused when the speaker kept referring to "yava" until I realized he meant "java". Neat tool, but I really don't see this being that much
by brown9-2 17y ago
I was a little bit confused when the speaker kept referring to "yava" until I realized he meant "java".
Neat tool, but I really don't see this being that much of a time-saver over the built-in tools that Eclipse or Idea has for this.
In addition, using annotations to generate things like "cleanup" blocks around a stream seems dangerous in the long run to me - I don't like having any part of the flow of my code being handled by "magic".
- ShabbyDoo 17y ago>I really don't see this being that much of a time-saver I don't either, but I do agree with his argument that it will make code more readable. And, w.r.t. the auto-finally block thingy, badly implemented exception handling is a common cause of error in "maintenance mode" codebases. [Yes, code reviews SHOULD happen, etc.]
- brown9-2 17y agoI think I feel the opposite - that this might make the code a little less readable, unless you know exactly what @Closeable (or whatever it's name was) does. But, to each his own...
- gchpaco 17y agoThe way the Java annotations are defined, it is almost always necessary to understand all annotations before modifying the code. It doesn't have to be this way, but the annotation processor has sufficient power to force it to be this way in practice.
- adammarkey 17y agoPronouncing "Java" like "Yava" is definitely a Dutch thing - I was building a Java based financial system for a bank in the Netherlands and it took a while to get used to the way they pronounce it too :)