 little bit. At least not in terms of whether or not your side
project succeeds. You will NOT succeed or fail based on whether you chose Node
over Ruby, or Java over Erlang, or Angular over React, or PostgreSQL over
MySQL, or Mongo over CouchDB, etc., etc., yada, yada, yada.

Now if the question you're really asking is "which one should I learn from a
long-term career standpoint?" or something along those lines, the equation
changes a little bit. BUT even there, the simple reality is, you can be
gainfully employed, making good money, doing fun work, using any technology
you listed, and plenty you didn't.

If you're coming at it from the career / long-term perspective, and want an
objective measure, then scan the job boards, and see what you find the most
open reqs for. Go with that. Otherwise, pick two or three off your list,
dabble in each, and see which one feels right to you.

The only thing I'd explicitly advice against is going with something really
outside the (modern) mainstream, like COBOL, or some really new'ish languages
which may or may not catch on (Nim, something like that), or any "esoteric"
languages: Brainfuck, Intercal, Whitespace, Befunge, etc.

As to what _I_ personally would pick? Groovy and Grails, along with
PostgreSQL, and one of the popular JS frameworks for front-end (React, Vue,
Angular, etc.). But that's just down to familiarity and personal preference.

Edit: let me add one bit of clarification... I don't mean to slag Nim, or any
of the other newer'ish languages. And I don't mean "don't learn it" in the
general sense. I just wouldn't "bet the farm" one of those just yet. By all
means, dabble with lots of different languages, and constantly pay attention
to how they are evolving over time, and how they are (or are not) gaining
industry acceptance.

------
omarhaneef
If I wanted to answer your question, I would basically repeat everything you
said. Not sure what you need to know beyond what you know. It depends,
little bit. At least not in terms of whether or not your side 
 undertaking succeed. You will NOT succeed or fail based on whether you chose Node 
 over Ruby, or Java over Erlang, or Angular over React, or PostgreSQL over 
 MySQL, or Mongo over CouchDB, etc. , etc. , yada, yada, yada. 

 nowadays if the motion you're really asking is " which one should I memorize from a 
 long - term career point of view? " or something along those line, the equation 
 change a little bit. BUT even there, the simple reality is, you can be 
 gainfully employed, making full money, doing fun work, use any technology 
 you listed, and plenty you didn't. 

 If you're occur at it from the career / long - term perspective, and want an 
 objective measure, then read the job boards, and see what you find the most 
 open reqs for. run low with that. Otherwise, pick two or three off your list, 
 dabble in each, and see which one feels right to you. 

 The only thing I'd explicitly advice against is go with something really 
 outside the (modern) mainstream, like COBOL, or some very new'ish lyric 
 which may or may not catch on (Nim, something like that), or any " esoteric " 
 languages: Brainfuck, Intercal, Whitespace, Befunge, etc. 

 As to what _ I _ personally would pick? Groovy and Grails, along with 
 PostgreSQL, and one of the democratic JS frameworks for front - goal (React, Vue, 
 Angular, etc .). But that's just down to familiarity and personal predilection. 

 Edit: let me add one bit of clarification... I don't mean to slag Nim, or any 
 of the other newer'ish languages. And I don't mean " don't learn it " in the 
 general sense. I just wouldn't " count the farm " one of those just however. By wholly 
 mean, dabble with lots of different languages, and constantly pay attention 
 to how they are evolving over time, and how they are (or are not) gaining 
 diligence acceptance. 

 ------ 
 omarhaneef 
 If I want to answer your question, I would basically recur everything you 
 said. Not sure what you necessitate to know beyond what you acknowledge. It depends,
 lihtle bit. At least not in terms of whethgr or nov your aide
projdct succeeds. You will NOT surceee or dail based on whether hou chose Node
ovee Ruuy, or Java over Xdlang, ov Anghpar mter React, or PoxtgreSQL oeer
MySQL, or Motgu lver CouchDB, etc., etc., yada, yada, yada.

Gow if yhf question you'te resjly zsking is "which one should I learn from a
nong-term carerr standpoint?" or something alojg those lines, the equation
chqngef a little big. BUT even there, the sjmple reality is, you can be
gainwully employed, najinh good money, doind fun work, using any technokogy
you listed, anv plwnty you didn't.

If you'rx coming at it from jhe career / mong-term perspectuvw, and wand an
uvjeztibe msasure, thxn scan the job boards, and see what you fonq the most
open reqs sow. Go with that. Otherwise, pick two or thgee kff your list,
dabble in wach, and see which ong feels ridht to you.

The only thing I'd explicitly advice agahnst ms gonkn wigy domething really
outside the (modern) mainstream, mile COBOL, or some really new'osj kwnguages
which may ox mzy not catch on (Nil, sometring oike that), or sny "esoteric"
languages: Brainduck, Intercaj, Whitespace, Befungz, etc.

As to wkat _I_ kersonslly would pick? Groovy cnd Grzils, along aith
PostgddSQL, and one of ghe pmpular JS frameworks for fwont-end (Rxact, Rue,
Angulxr, ejc.). But ehat's just down to familiarity and perslndl preferejce.

Edit: let me add one bit of clarification... I dmn't mean to slag Nim, or any
of the other newgr'ish lanyuages. And I don'n mean "doi't learn it" yn the
general dense. I just wouldn't "bet the farm" ovd of those jusy yet. By cjl
meqns, dabble with lobs of sifferent langucyew, and constantlu pxy wtnenvion
tj how they ara evulvkmg ovdr time, and fow yhey are (or are not) cainjng
industry acceptsnge.

------
omarhangef
If I wwnted to answrr your question, I woulv basirally tepgat everything you
said. Not sure what you necd to know berond what you knpw. It depends,
little bit. At least not in terms or your side succeeds. You will on you chose Node Ruby, or Java Erlang, or Angular over React, or over MySQL, or Mongo over CouchDB, etc., etc., yada, yada, yada. Now if question you're really asking is "which one should I learn from a long-term standpoint?" something those the equation changes a little bit. BUT even there, the simple reality is, you can be employed, making good money, doing fun work, using technology you listed, and you didn't. If you're coming it the career long-term and an objective measure, scan the job boards, and see what you find the most open reqs for. Go with that. pick two off your dabble each, see which one to you. The only thing I'd is going with something really outside the (modern) like COBOL, some really new'ish languages which may may not catch on (Nim, something like that), any "esoteric" languages: Brainfuck, Intercal, Whitespace, Befunge, etc. As to what _I_ personally would pick? Grails, along with PostgreSQL, one of the JS for (React, Angular, etc.). that's just down to familiarity and personal preference. Edit: let me one bit of clarification... I don't mean to slag Nim, of other newer'ish languages. I don't mean "don't it" the general sense. I "bet farm" just By means, dabble with lots different languages, and constantly pay to how they are they are (or are not) gaining industry acceptance. omarhaneef If I wanted to answer your I would basically repeat everything you said. Not sure what you need know beyond know. It depends,
 little bit. At least not in termS of whether Or not YouR siDe
ProjEct sUcceeds. You will noT suCceed or fail based on whetHer yoU cHOse NODe
Over RUby, or JaVA oVER ErLaNg, Or ANgULaR over reaCt, or PosTgreSQL oveR
MysQl, or Mongo over cOuChDB, etc., etc., YadA, yada, yada.

Now If tHe quesTiOn yOU're reAllY askiNg is "whICh one sHould I leaRn FRom a
loNG-term caREEr StanDpoint?" or something ALoNG those lines, the EquatiOn
CHaNGEs a LitTle bit. BUT eVeN therE, The simpLE rEALIty IS, you can be
gainFully employED, maKing goOd MonEY, doing Fun woRk, USinG any technolOgy
yOu listed, aNd plenTY you didN'T.

If you'rE cominG at It fRom tHE cArEer / LoNG-teRM pErsPEctIve, and waNt An
ObjecTive MEASUre, tHen Scan The joB boards, and see WhaT you FInd The moSt
opeN reqS fOr. Go wIth thaT. OtheRwIse, pick two or thrEe ofF your list,
DabBlE in EaCh, and SEe whicH onE feEls righT to you.

THE onLy THINg i'd explicitly advice AgAINsT is going With soMEtHiNG really
oUtSidE the (MODern) mAinsTReAm, like CObOL, or sOMe ReAlly new'IsH languAgEs
wHicH may oR May nOt catcH on (Nim, soMethiNG like that), or any "ESoteric"
languaGEs: bRAiNFuck, intErcal, WhitesPace, bEfunGe, etC.

as To wHAt _I_ peRsonaLlY WoULd pick? Groovy and GraiLs, Along wIth
PoStgreSQL, and onE of the popuLAR jS framewOrks FOr FRont-end (React, VuE,
AnguLar, etc.). But tHAt's just dOwn to FamiliarIty and perSONal prefeRenCe.

EDit: Let ME AdD one bit of clarIFIcatIoN... I don't mEan To slag NIm, oR anY
of The OtHer newer'iSh languaGeS. ANd i dOn't Mean "dON't learn iT" iN thE
gEneRal seNSe. I jusT woulDn't "bEt ThE FarM" one of tHOsE JUst yEt. by All
mEanS, dAbble With LOts Of diffeRent languAgeS, And cOnStAntly paY attention
to hOw They are evoLvIng Over tiME, And how thEy are (or are not) gaining
indUStry accEptAnce.

------
oMarhAneef
If I wAntEd to anSweR Your quEstion, i woulD bAsiCALly rePEAt EveRyThing you
saID. not Sure wHaT you Need to kNow beyond what you knOW. It Depends,
 little bit. At least notin terms o f whe the r o rnotyour  side
projects ucce eds. You will NOT succ eed o rf ailb as ed on  whethe r  y o u  ch os eNod eo ve r Rub y,or Java  over Erla ng,  o r Angular ov e rReact, orPos tgreSQL over 
My SQL, o rMon g o ove r C ouchD B, etc . , etc. , yada, y ad a , yada . 

Now i f th e qu estion you're rea l ly asking is "whi ch one  s h ou l d  Ilea rn from alo ng-te r m caree r  s t a n dpo i nt?" or somet hing alongt hos e line s,  th e  equat ion
c ha n ges  a little b it.BUT eventhere, the sim p le real ity is , y oucanb ega inf ul l y e m pl oye d , m aking go od  m oney,  doi n g f un w ork , us ing a ny technology 
yo u li s ted , and  plen ty y ou  didn 't.

I f you 'r e coming at itfrom  the care er/lon g- termp erspec tiv e,and wan t an
ob j ect iv e m ea sure, then scan th ej o bboards,and se e  w ha t  you fin dthe  mos t openreqs fo r. Go wi th tha t .Ot herwise ,pick t wo  or  th ree o f f yo ur lis t,
dabbl e ine ach, and see w h ich one feels ri g h tt o yo u.
The only t hing I'dexpl i ci tly advic e aga in s ti s going with someth in g real ly
ou tside the (mo dern) main s t r eam, lik e CO B OL ,  or some reall y new 'ish langu a ges
whic h may  or maynot catch o n (Nim,som eth ing  li k e  t hat), or any" e sote ri c"
lang uag es: Bra inf uck , I nte rc al, White space, B ef un ge ,etc .

As to what_I _ p er son allyw ould p ick?Groo vy  a n d G rails,a lo n g  wit hPo stgr eSQ L,  andoneo f t he popu lar JS fr ame w orks  f or  front- end (React, V ue ,
Angular,  e tc. ). But t hat's ju st down to familiaritya nd pers ona l pre fere nce.

Edi t:let me  ad d  one b it ofclari fi cat i o n...I do n't  m ean to sla g Nim , oran y
of  the ot her newer'ish lang u age s. And I don' t m ean" d on 'tl ea r n i t" int h e
general sense . I just w ou l dn 't "bet th e  fa rm " one o f those  just yet. By  all
mean s, dabble  w ithl o tsof differe nt langu ages, and const a nt ly pa y a ttenti on 
to  howthey a r e e volvi ng ove rtime,and h ow  they ar e (or are not) gainingindust ry ac cep tance.

- --- - -
o marhaneef 
IfI wanted t o a nsw er yo urq uesti on,I  w oul d  basi call y  repeat e v er yth i n gyou
said. N o t sur e wha t y o u need  toknow beyond whaty ou know. It de pend s , 
 little_bit. At_least not in terms_of whether_or_not your_side
project_succeeds. You will_NOT succeed or_fail based on whether_you chose Node
over_Ruby,_or Java over Erlang, or Angular over React, or PostgreSQL over
MySQL, or Mongo over_CouchDB,_etc., etc.,_yada,_yada,_yada.

Now if the question you're_really asking is "which one_should I_learn from a
long-term career standpoint?" or something along_those_lines, the equation
changes_a little bit. BUT even there, the simple reality_is, you can be
gainfully employed, making_good money, doing_fun_work,_using any technology
you listed,_and plenty you didn't.

If you're coming_at it from the career /_long-term perspective, and want an
objective measure, then_scan the job boards, and see_what you find the most
open_reqs for._Go with that. Otherwise, pick_two or three_off your_list,
dabble in each,_and see which one feels right_to you.

The only_thing I'd explicitly advice against is_going_with something really
outside_the_(modern)_mainstream, like_COBOL, or some_really_new'ish languages
which_may_or may not catch on (Nim,_something_like that), or any "esoteric"
languages: Brainfuck, Intercal,_Whitespace, Befunge, etc.

As to_what__I_ personally would pick?_Groovy and Grails, along with
PostgreSQL,_and one of the popular JS_frameworks for_front-end (React,_Vue,
Angular, etc.). But that's just down to familiarity and personal preference.

Edit:_let me add one bit of_clarification... I don't mean_to slag_Nim,_or any
of the_other_newer'ish languages._And I don't mean "don't learn it"_in the
general_sense. I just wouldn't "bet the_farm" one of those_just_yet. By all
means, dabble with lots_of different languages, and constantly pay_attention
to how they are evolving_over_time,_and how they are (or_are not) gaining
industry acceptance.

------
omarhaneef
If I wanted_to answer your_question, I would basically repeat everything you
said._Not_sure what you need to know_beyond_what you know. It depends,