...and they have mostly left it in this case. Fine; but lets not pretend open-source GPL projects are significant to the world at large; they are backroom projects with no future.
Upvoted, as I agree with you philosophically, that the GPL is not exactly a corporate developer's best friend.
However, neither Solaris nor Apple are typical corporations in terms of using licensed 3rd party code; given the terms the GPL poses, wouldn't you expect to see more smaller companies, or companies that operate primarily on the web to adopt GPL'd projects?
No, UncleOxidant, it is definitely not "especially true for C++". There are plenty of powerful languages out there, many with more subtleties than C++, and longer roads to mastery.
No one disputes that C++ has a long road to mastery, but there are plenty of other languages for which that is true. So, C++ is not special in that way.
Haskell probably has a long road to mastery. That said I think it might still be shorter than that for C++. it is hard to think of a language that takes longer than c++ to master. Interesting!
Fair enough. I found haskell easier than c++ to grok. It may have helped that I had a good grasp on type theory before I learned Haskell (worked through TAPL a few years ago). Subjectively, I found the various components of Haskell almost always fit together in very logical fashion with a very clean syntax, while C++ felt arbitrary, (with exceptions to every rule and exceptions to those exceptions and exceptions to those). I share your intent of not starting a language war. Just expressing my experience.
Of course, there can be no objective measure easily made, and I do not want to engage in language wars.
That said, I am a C++ expert, but contend that each of Lisp, Haskell, and Scala are far deeper languages, with more involved in their mastery than C++.
kailoa makes a good point: removing keywords from the job posting risks not appearing in a potential employee's search.
I think that the trick is to have "just the right" keywords, and no more. The particular example that I give in the article has too many. So, fewer is better, in that case.
Cool idea, but I agree that the implementation needs work. The score for my office is 68, but it is really not walkable at all. Whereas the score for my home is only a 62, but I never need to use a car at home.