Agree with this wholeheartedly. I started learning C++ back in 1997 with "Learn C++ in 21 days" and other books. I quickly got burned out with building simple print out programs and over the past 16 years have started different languages in fits and starts.
There are so few one language projects that are worth using, that the single language approach seems really outdated.
To me a much better approach would be to have learning structured around a specific project type. In general projects fall into only a handful of categories so I don't think it would be terribly hard to structure. For example "Web commerce" (Javascript, CSS, HTML5, mySQL), "Machine learning" (Python, Java) etc... You wouldn't learn all the details of a language up front but you would get to your goal more quickly and have a framework/template for future projects.
There are so few one language projects that are worth using, that the single language approach seems really outdated.
To me a much better approach would be to have learning structured around a specific project type. In general projects fall into only a handful of categories so I don't think it would be terribly hard to structure. For example "Web commerce" (Javascript, CSS, HTML5, mySQL), "Machine learning" (Python, Java) etc... You wouldn't learn all the details of a language up front but you would get to your goal more quickly and have a framework/template for future projects.