Thanks for the post. Can we data drive the page object design pattern? I tried Hybrid frame work with page objects. It work fine for single set of data and the same fails for group of data.

My framework is little different. All my test statements are in one excel file and test data in another excel file. Can you give me any mail id (I do not have any of the 3 accounts given below)so that i can send the sample project,

In the end, I think you’re right; there’s not a lot of evidence supporting the move from well established languages, beyond the critical mass of discontent that seems to be sweeping the developer community. As you yourself said in the post, Java just plain feels *old* at this point, and simply tacking on new features is not a way to fix it. What it’s missing, I think, is a set of principles to drive it’s progress.

This, I think, is the value I see in languages like Clojure, Haskell, and Scala. Scala is, in many ways, very complicated, but it is usually easy to see how the various complexities trace back to it’s two core goals: to unify functional and OO programming, and to provide all of the tools needed to scale from small to large scale applications. Java is, in many ways, an 80% language. The type system is good enough to model basic type hierarchies, but struggles with higher-order types. Generics are for the most part good enough, but are limited in terms of runtime information and bounds. That’s not to say that every successful language needs to have all (or even any) of these features, but the language must treat these topics consistently, and the motivation for their design should be clear. I think this is what Java has been lacking in the last few years, and why there’s been such a strong interest in alternative languages.

I don’t actually disagree with the core of the article, I do want to make a point of contention here though.

These two are not mutually exclusive. There’s plenty of companies who solve difficult problems in “hipster” languages.

But I don’t think people who want to work for companies that support their language of preference is retarded. If I got an offer from a primarily Chinese company with little to no support for English speakers, I might consider it if the pay and benefits compensated for having to learn Chinese, but I’d rightly have a preference for an English speaking company because my ability to express myself, solve problems, and interact with people is best in English.
A programming language is no different in this respect.

You even bring up this point yourself, that this retraining is a major expense in time and productivity for the employer, but ALSO the employee.

So I think this is a symptom of people simply wanting to receive a return on the investment of the precious free-time they spent learning the skill(whether they should have is an entirely different argument).

If they turn down a really well paying position that’s like 2x their “hipster” language then yeah…that’s probably dumb. But if the offers are comparable then they can do their best work with their hipster language.

public String getComplexFunctionResult(int x){
return OverallResult(someOtherFunction(AndAnother(AndOneMore(x))));
}

which is usually a sign of great function decomposition and is as readable as your method naming skills in Java

So yeah, after thinking about, nested methods in Java would actually be good, because if they were being abused bugs would be easier to notice, because they’re just plain old methods.