|
(I have no experience having to fulfill wishes of clients by choosing language of their choice as I always worked in product environment).
A language must be inherently good. Our community has been mesmerized by the smoke and mirrors in the form of tooling, IDE, frameworks etc for far too long and its about time we come out of that. These bells and whistles are external to the language and can be built for even the worst of the lot. Further, the idea of productivity has been transformed into struggling with tooling and choosing one of the several identical frameworks, from being able to create things with the language efficiently and correctly. Remember, HLL were created to make us more productive than having to use assembly level languages. It seems these days the designers are all too happy to dish out a mediocre and stale HLL because they know that by adding the gimmick of tooling and getting a megacorp to promote it (because every one of these needs to play the "friend of the dev community" card), it can get attention of the herds. Sheesh.
Now, frameworks and tooling are useful to have to make development more productive, but relying on these factors alone and using them as a yardstick to measure the quality and utility of a language is unfortunate and foolish. Its like judging a candidate by the references he provides; I mean, would anyone list people who wouldn't be all praises? Its like a movie with gimmicky narrative such as non linearity etc instead of having substance in story, script and characters that gets accolades. Its like...you get the point.
|
|
|
|
|
None of the choices given could convince me. I prefer a good framework like the .Net framework to write code against.
And a great IDE, of course.
While the framework behind Java is also good, there is no good IDE for it ("Eclipse"? oh no).
And other languages are typically lacking both framework and IDE.
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
If the job/project is interesting enough to get my attention then learning the language comes with it.
In the same job/project the language changes if there are benefits, i.e. porting from VB6 to C++ or C#.
Adding to the repertoire for the sake of it? Either it does really get my attention (any flavor of Assembler usually does) or it's not worth it, languages and frameworks shine and die in timespans that are way shorter than the change of jobs/projects.
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
|
Except Ruby and any flavor of BASIC.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
finally our team has to discuss and switch to Swift because the feeling to be left behind hit us in the manner that new hirees dont like the good old objective C. The point is that I am the oldest in team, but the only one who demanded it earlier and now cheering a bit about it. Really strange that the old man is the front runner. 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
Ultimately, most of us need to earn a living through coding, and if we can't earn our crust with our favourite language are likely to jump ship to something else. The point at which we decide to do that depends on how much we need the money, the financial benefits of a new language/tool (in terms of market rates + availability), and the complexity / costs / pain of learning. Typically if a language is a doddle to learn but pays well, that won't last long because the market will flood and rates will come down quickly. But if a client has specifically requested it, and is prepared to pay / wait for us to get up to speed, that can be the incentive to expand our skill set.
|
|
|
|
|
DerekTP123 wrote:
Typically if a language is a doddle to learn but pays well, that won't last long because the market will flood and rates will come down quickly.
Interesting perspective. I suppose that subconsciously I had assumed some unwritten rule that "Easier Language => Harder/More Interesting Work" which just don't ever actually pan out in the real world...
Pete Lomax
|
|
|
|
|
...has led me to learn Android Studio, Android Development, revisit Java and learn Kotlin ... in a few days ...
|
|
|
|
|
As long as Microsoft is still doing well, why would I change languages?
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Sounds like you should choose:
"Other - If Microsoft tell me to"
|
|
|
|
|
musefan wrote: If Microsoft tell me to
They only way they could tell me to stop developing on their platform is if the world stopped using them. Why would it be any different?
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
You could move to a new language within their platform. Or more likely add a new language. E.g., if you only use C# you could add F#.
Kevin
|
|
|
|
|
Kevin McFarlane wrote: you could add F#.
If I ever had a need to, sure.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
At this point in my career, and considering the good gig I have now, only an offer for considerably more money would make me move to a new language. Or if the company forced a change upon me. Or if I was terminated and my best option of employment involved learning a new language.
|
|
|
|
|
011111100010 wrote: As long as Microsoft is still doing well, why would I change languages?
so just curious what do you do when they aren't doing well? last I checked there are several areas where they have either lost or just straight given up.
|
|
|
|
|
Whenever .Net is dead.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
011111100010 wrote: Whenever .Net is dead
last time I checked .Net is a framework and not a language. So which language using the .Net framework are we to assume you are referring to?
In general I am of the belief that computer languages never really die regardless of how hard everyone tries to make it so.
I don't see the .Net framework dying only because MFC for C++ is still active. Even those Afx...() functions which predate MFC are still around and being maintained apparently.
|
|
|
|
|
Dennis E White wrote: So which language using the .Net framework are we to assume you are referring to?
c#
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Ooh eee ooh ah ah.
Ting tang walla-walla bing-bang
Ooh eee ooh ah ah,
Ting tang walla-walla bang-bang.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
1) Work / Projects with the new language (but not just "my boss tells I have to" as listed)
2) Curiosity / Personal interest.
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.
|
|
|
|
|
Mostly curiosity. That usually leads me to explore rather than use properly. It also sometimes helps me to think differently about my main language(s).
But also interest in certain types of problems or domains forces you to look at other languages. E.g., AI and machine learning almost mandate some interest in Python and R. But most Microsoft-centric development roles don't require it.
Kevin
|
|
|
|
|
(in the world of DSLs) for the "other" I selected:
I missed the option "Higher Abstraction/Higher Productivity"
|
|
|
|
|
The fact that it has been out for a long(ish) time and that people like it and give it good reviews... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
Been out for a long time.
regularly worked on and improved.
Each release does not destroy backwards compatibility. Some breaking okay.
Previous language(s) announced as end of life (Silverlight -> 90% native JS with some lingering jQuery)
or bought over by some company and becoming and always been a headache of updates (Java -> C#)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
