81–90 of 90 posts
Earlier quoted context omitted.
There are one-stack programmers that use only Java/C# with an ORM and all the SAP ABAP developers. Some seem to prefer such jobs, I am not one of them, but to each his own.
I wish I could just use C#, but unfortunately there is no way to avoid JavaScript these days.
Earlier quoted context omitted.
I wish I could just use C#, but unfortunately there is no way to avoid JavaScript these days.
Scriptsharp allows you to write in C# and compile to JS
Shouldn't programmers be polyglot by default . It's like saying there is a conference for golfers who play with more than one club!
Only if you think of programming languages as an individual golf-club. Put it this way: Is there a conference for professional basketball, baseball AND ice hockey players? I'm not even aware of anyone who managed to go pro in two of those, not to mention all three. Most programmers have a preferred domain and language. Once you scale past a pet project and have a decently sized team, specializations start to occur, e…
Programming languages are different. For one, they all run on the same hardware. For another, the basics of logic and such are the same. And for the coup de grace, we have the well-known acecdata that learning a language of a significantly different paradigm than your "main" language generally improves your ability to program in your "main" language, to the point where I and others routinely recommend to people that they learn (or implement!) other language paradigms as a routine, expected part of their programming career. Learning Haskell to the point you can effectively use it can and will improve your PHP.
In the programming field, I don't think you can be a master programmer without being a fairly effective polyglot, as a bare minimum requirement. That is, if someone claims to be a master but they only have fluency in one language, even if that language is C++ or something, I would not consider them a "programming" master, only a C++ master.
Earlier quoted context omitted.
> In that case it comes down to economics, It doesn't come down to it : it was about economics all along. All these philosophies -- polyglot, more monoglot, etc. -- have costs. You can choose to ignore it sometimes by staunchly recommending one approach over another in generic settings. But the underlying costs are still there.
Absolutely! Its economics all along. Anyone who advocates pure monoglot or always using the best tool is not being pragmatic. Decisions should be driven by cost/benefit and not religion.
Shouldn't programmers be polyglot by default . It's like saying there is a conference for golfers who play with more than one club!
Earlier quoted context omitted.
Polyglot approach involves picking the 'best' language for each micro-task and then trying to get them all to interact and play nicely to each other. The more 'normal' approach is to pick 1-3 languages that are "good enough" at all the necessary tasks.
But then wouldn't this require a bigger team with vast expertise or a lot of time compared to a more normal approach, and it will only result in marginal performance improvement, which might not be important in most of the regular projects?
Earlier quoted context omitted.
Polyglot approach involves picking the 'best' language for each micro-task and then trying to get them all to interact and play nicely to each other. The more 'normal' approach is to pick 1-3 languages that are "good enough" at all the necessary tasks.
But then wouldn't this require a bigger team with vast expertise or a lot of time compared to a more normal approach, and it will only result in marginal performance improvement, which might not be important in most of the regular projects?
Did anybody else read through the (English language) conference website for the (presumably English language) conference, and wonder to themselves, "Why ... Poland?" I'm not knocking Poland, but it seems strange to have an English-language conference there and not offer anything in the way of explanation for the choice. I mean, I'm sure there is a reasonable explanation (central location, picturesque setting, low cos…
Did anybody else read through the (English language) conference website for the (presumably English language) conference, and wonder to themselves, "Why ... Poland?" I'm not knocking Poland, but it seems strange to have an English-language conference there and not offer anything in the way of explanation for the choice. I mean, I'm sure there is a reasonable explanation (central location, picturesque setting, low cos…
You know, it would be very boring if all conferences were held in English-spoken cities, eg. New York or London. You should come to PolyConf and check one Poznan, one of the most beautiful cities in Poland. :)
What Poznan does have going for it is that it is the economic motor of a very large part of Poland.