"The departures meant that executives with intimate knowledge of JPMorgan’s systems..."
Working most of my life in financial services, executives dont have intimate knowledge unless the systems in place happen to be the same ones they helped build 10-15 years ago (which is true in some cases).
I still consider myself hands on, although not cutting code on a daily basis, and I dont have intimate knowledge of those systems. They will still phone me at 2am despite that.
And what difference has the lack of lambda's really made?
I cant stand these "my language is better than your language" debates. Use whatever one makes sense for the job (or, in the case of the enterprise, you can hire enough of).
The difference is readability and developer efficiency. the non-lambda version in the example is four times the size of the lambda version. I don't know about you, but I can only fit about thirty lines of source code in my brain at once.
Virtually every other modern programming language has a lambda, it's good to see Java catch up. This isn't about Java versus any particular language.
When it comes to how much code you can keep in your head, do you really keep the boilerplate there? Whenever I've used Java and had to attach an ActionListener or whatever, I don't think of it as being an anonymous class with a single method, I think of it as just the logic in the method when I'm reasoning about the program.
It is a pain to write if you don't like having to let the IDE do everything for you, though.
If Bill wants to give away billions to good causes and as a side effect he gets charitable tax-exempt status then I'm more than happy with that. His money is being far better spent than his tax dollars.
