There's been a few blog postings about adding property support to the Java language properly. Here's a synopsis. The goal is to make it easier to access object properties, using property names, rather than method names.
I'm amazed at some people's ability to Not Get It.
The proposal is too add a special operator, ->, for this purpose.
This means that you have to be aware that something is a property before you know how to access it.
Properties in other languages are powerful because they are accessed just like fields. You see this in Ruby especially. You can change your mind and switch from simple public instance variables to getter/setter methods at any time, without breaking any existing code. Ruby will even generate the getter and setter for you. Braindead simple.
So, Mr. Danny Coward, here's a proposal for you. I would like the property access operator to be ..
Let me make that more clear: .
You know, the exact operator used in other languages, the exact operator that anyone would expect.
Let the compiler do the work. The -> operator is an approach to make the compiler do less work and the developer do more. That is ass-backwards. I'm slaying dragons over here in Tapestry 5 land, to make the environment bend over backwards to adapt to the user, easily and seamlessly. It would be nice if the overlords in charge of the Java language would take that as their lesson. Complexity is not solved by adding more complexity. Complexity is solved by removing complexity ... even if it requires a bit more work behind the scenes to support that simplicity.
Of course, this may all be a distraction from their main attemmpt to screw the pooch: super modules. More on that soon.