The 36% number comes from the Guarantees of Origin scam. It's an economic system which disconnects the production and consumption of energy from the buying and selling of it. It basically allows renewable energy to produce double the amount of clean conscience, for the same amount of clean energy:
Also, I suspect that the "67.5% of gross final consumption" includes stuff like gas for vehicles, wood for heating, etc, not just electricity, which makes it meaningless in this discussion.
Event worse, in Europe the Bolt will we sold as "Opel Ampera-e". Yuck! I still want the car though. 300km+ on a single charge!
"traditional" Java web stuff.
I just threw up in my mouth a little bit.
I think you'll still find that most libraries retain java 7 compatibility. Luckily that does not generally prevent you from utilizing java 8 features in application code, even when interfacing with those libraries. E.g. libraries accepting references to single-method interfaces for callbacks will happily accept a lambda expression instead. To the JVM they're indistinguishable after all.
One example that comes to mind is Spark framework (http://sparkjava.com/) which I like for its almost naive simplicity. Great for throwing together a microservice on short notice.
It's not about the language. It's the APIs that matter. Rust couldn't be less relevant.
And frankly J2EE doesn't matter that much either. I haven't seen a purebred J2EE application inn ages. There may exist EJB2 monstrosities deep in the server catacombs of large banks, but nowadays when people say enterprise java, they really just mean java code serving http-requests and running batch-jobs, with a gazillion of 3rd party libraries throw in.
I make a decent living off writing Java code, and after Java 8 came out I started liking it, not just tolerating it. Lambdas and method references, which I thought would be a nice-to-have, has turned it into a completely new language, streams are great, the multi-threading support is not too shabby and the new time API was loooong overdue.
When reading the linked list (no pun) of new features though, all I can say is "meh"...
Stuff like HTTP/2, TIFF and JSON support should be external, upgradable, libraries. Its a common theme that the standard java libraries fall into disuse after a while, because external library writers do a much better job of implementing the same concepts. JDBC, Date/Calendar, XML processing, HTTP are just a few examples.
My key takeaway from this is that I'm a bit tempted to start using _ as an identifier name, just to fuck over any future maintainers of my code.
In English, every word can be verbed. Would that it were so in our programming languages.