4 ms·
Let me revise my previous comment. While many might categorize Python, Javascript and Ruby as blue-collar languages, they do encourage all sorts of metaprogram
by pron 13y ago
Let me revise my previous comment. While many might categorize Python, Javascript and Ruby as blue-collar languages, they do encourage all sorts of metaprogramming tricks, while Java, C# and Go absolutely don't. I think this is a big philosophical distinction, because the second group favors readability and the ability to share code in a large team over language power, and this is what makes Go much closer to Java/C# in its philosophy than to Python et al.
- NateDad 13y agoBlue collar worker just usually means "one who is uneducated and unskilled". Putting that onto languages is sort of demeaning... it sounds like that's not really what you meant, though, and that's cool, just my misunderstanding of your meaning.
- pron 13y agoThat's just how James Gosling described Java when he explained the philosophy behind it in 1997[1]. He wrote, "Java is a blue collar language. It’s not PhD thesis material but a language for a job. Java feels very familiar to many different programmers because I had a very strong tendency to prefer things that had been used a lot over things that just sounded like a good idea." He most certainly didn't intend the term to be demeaning, but more to contrast it with research languages that include features that are untried and unproven. The term has since been used as shorthand for Java's (and languages like it) goals and philosophy. [1]: http://dfjug.org/thefeelofjava.pdf http://dfjug.org/thefeelofjava.pdf
- bradleyjg 13y agoUneducated I'll give you, though probably it should be qualified by something like formally educated, but blue collar certainly does not mean unskilled. The paradigmatic blue collar job to my mind is not taking orders at McDonalds, it's welding.
- NateDad 13y agoI knew I should have qualified that more. You're right, McDonald's is not blue collar, but working in a manufacturing plant riveting part A to part B is. It also encompasses stuff like mechanics and welders that do require skill and even some education and certification. But regardless, most of the time it's still used to mean something lesser.
- gruseom 13y agothe second group favors readability and the ability to share code in a large team over language power Not to pick on you, but people say this all the time, as in it's probably the thing people say most often on this subject, and I wonder: do we have any evidence for it? That is, do we have any evidence that the mid-tier languages which eschew more powerful abstractions (Java and its peers) lead to either more readable or more shareable code? Or is it one of those things that everybody "knows" but ain't so?
- pron 13y agoWell, I can't claim that that's the case, only that those languages' designers think it is. There are some things we do know, if only anecdotally (maybe there's been some research on the subject – I don't know). We do know that C++ was a real boon when it first garnered wide appeal, but that very quickly large teams began to curtail the use of some of its more advanced features because of that reason. We also know that people have been writing much larger projects in Java (and possibly C#) than in any other language in history, certainly relative to the effort invested (there might have been larger C++ projects). Some of it just seems intuitive (though may not be the actual case). The problem is that it's hard to gather data because the languages adopting this view are the ones that are most popular, which helps them get selected for large projects to begin with. But we might have more data soon. I think JavaScript is the first "magic encouraged" language that will be used in multi MLOC projects. Ruby is more "magical" but doesn't seem to be favored by large teams working on large projects. So we might know more soon. Personally, though, I think that's the wrong issue. Whatever extra productivity is gained by language magic, we're not talking orders of magnitude here. Usually it's mostly about developer enjoyment, lack of annoying boilerplate etc.. These are annoying issues, but not critical ones. I think the most crucial issue is state management, which can have an order-of-magnitude difference for some projects, as well as a significant effect on performance and scaling.
- gruseom 13y agoMost everything you're talking about is explicable by popularity effects. That's why more objective study would be interesting. Alas, I doubt it will happen: serious research on software engineering, as opposed to the thin broth we have now, would require at least an order of magnitude more funding, and no one's likely to provide that. I'm not sure I like your distinction between developer enjoyment, lack of boilerplate, and state management. To me those things all have to do with good design.