|
So you average over 1.4 languages a year, minus the dabbled ones, if we went that route - could more more than 1 a year, I don't know. 
|
|
|
|
|
Full: C, C++, C#, C++CLI, Perl, F#, Javascript/Typescript, Java, SQL/TSQL
Scripting: HTML, CSS, mIRC-script, Lua, Batch/Powershell
Other: TLA+
Those are the ones I'd be comfortable writing code in right now. I've dabbled in other things like BASIC/VB and Elm. And there are still languages I'd like to play with at some point like Ruby and Go. A new language every 1-2 years isn't really all that bad. Usefulness is arguable but I enjoy it.
|
|
|
|
|
I learn something new (call it a new "language" or a new "software" or whatever), when I need to do it (professionally) or when it really wakes up my interest (private)
If not... I prefer to keep my focus in methodologies, algorithms and things like that (more abstract). The concrete syntax to do something is usually in the last place.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
You echoed my sentiments verbatim.
/ravi
|
|
|
|
|
When you know Java and do your first JavaScript project, is that a new language then?
If you know C# and have to do a bit low level C code... new language?
We have some archetypes of languages, some general concepts (strong typed, dynamic), some execution methods (interpreted, JIT, compiled), but where is the border? How many different commands make up a "new language"?
be it "foreach (x in y)" or "for (x : y)" ... is that really a different language?
It's just about a bit more or less syntactic sugar, some concepts differ a bit, but honestly it's not that hard divided these days than it has been in the 90's.
|
|
|
|
|
Mike Barthold wrote: When you know Java and do your first JavaScript
Completely different languages that happen to share a name and syntax.
We're talking OOP vs. prototype, typed vs. untyped, compiled vs. interpreted, static vs. dynamic, rich and full vs. missing basic functions (although it's getting better)...
The worst JavaScript code I've seen is from C# developers who thought JavaScript is just untyped C#... 
If you think Java and JavaScript are alike you need to step up your "learned languages per year" game 
|
|
|
|
|
I don't think that 
I don't think anything about javascript except "try to avoid it as long as you can"
What I meant, was, as I wrote (and you repeated much of it), that it's more a question of concept and approach, and not the "language" itself. that's just a bit of vocabulary.
What a dev really needs to understand is the how-to for each of those syntax-bits.
How to do it "right".
|
|
|
|
|
To me, a language is everything about that language.
The syntax is a small part of that.
Other aspects are the libraries, best practices, environment, etc.
If you're talking syntax then I agree, C, C++, Java, C# and even JavaScript all look alike.
However, you can't say you (almost) speak Dutch just because we have the same alphabet as the English
If you take in everything else then I guess only Java and C# look alike, the others have close to nothing in common with the others.
|
|
|
|
|
Well put Sander.
As for new languages, I explore and dabble quite frequently but that's a far cry from knowing them!
Kevin
|
|
|
|
|
I take your point but maybe not your examples. C and C# are oceans apart form each other even if they do share a few flow control statements.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
Oh yes they are, you are absolutely right. OO vs proc -- So yes, those two qualify as "different" languages, maybe more than many others
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
