What are these "incidental complexities" and "type system inconsistencies" the author speaks of as keeping Java from becoming second nature? There are probably

What are these "incidental complexities" and "type system inconsistencies" the author speaks of as keeping Java from becoming second nature? There are probably literally a million Java developers who have reached a point on the learning curve where it feels second nature, makes sense in the larger context, stays out of the way (except for a thing or two), and lets them focus on the problem at hand. The latest argument I've heard for Scala is that its complexity and difficult to read code is a plus, because only really smart and dedicated programmers can handle it. It's a "filter". I like that one. It soothes egoes while simultaneously allowing results-oriented businesses to dismiss it.