 source"

Indeed: [https://hive.apache.org/](https://hive.apache.org/)

~~~
yarrel
The link is in the article -
[https://github.com/nytlabs/hive](https://github.com/nytlabs/hive)

~~~
sanswork
I think the OPs point was that there is already a popular open source project
named Hive.

~~~
weego
Which is quickly becoming a tedious exercise in cheap point scoring. People go
for names that reflect the intent or otherwise associate with the system they
are building. They also prefer existing words. Sometimes that will mean reuse
of the same words. Lets accept that and move on with our lives.

------
issaria
The are so many names available, why choose this one?

------
vander_elst
"hive" really? google the name first??

~~~
tosh
Sooner rather than later it will become impossible to avoid naming conflicts
for open source projects (or any projects) if you want a meaningful name.

 
When Node.js is the wrong tool for the job - vmware505
https://medium.com/@jongleberry/when-node-js-is-the-wrong-tool-for-the-job-6d3325fac85c#.gwnpqr3qs
======
klodolph
It seems like a lot of JavaScript developers are repeating things like "more
people know JavaScript so you don't have to learn a new language, which saves
you time". I don't get it. In my experience, if you find a good developer,
they can pick up C#, Swift, or Go pretty quickly, and if you can't find a good
developer, the fact that they already know JavaScript is not much of an
advantage. Even if the developer you hire already knows your language, they're
going to be spending time learning your code base and how your organization
works (shared repo? PRs? Feature branches? Code review? Coding standards?)

That, and nose.js developers seem to repeat the claim that node.js makes
delivery faster… but is it really any faster than ASP.NET, Rails, Django, or
Go stdlib? Those frameworks are so fast for prototyping and delivering bread-
and-
source " 

 Indeed: [ https://hive.apache.org/](https://hive.apache.org/) 

 ~~~ 
 yarrel 
 The link is in the article - 
 [ https://github.com/nytlabs/hive](https://github.com/nytlabs/hive) 

 ~~~ 
 sanswork 
 I think the OPs point was that there be already a democratic open source undertaking 
 named Hive. 

 ~~~ 
 weego 
 Which is cursorily becoming a tedious use in bum point marking. citizenry go 
 for name that reflect the intent or differently associate with the system they 
 are building. They also prefer existing words. Sometimes that will entail reuse 
 of the same words. let accept that and move on with our lives. 

 ------ 
 issaria 
 The are so many name calling available, why choose this one? 

 ------ 
 vander_elst 
 " hive " really? google the name first? ? 

 ~~~ 
 tosh 
 Sooner rather than later it will become impossible to invalidate naming conflicts 
 for open source projects (or any projects) if you want a meaningful name. 

 
 When Node.js is the wrong tool for the job - vmware505 
 https://medium.com/@jongleberry/when-node-js-is-the-wrong-tool-for-the-job-6d3325fac85c#.gwnpqr3qs 
 = = = = = = 
 klodolph 
 It seems like a lot of JavaScript developers are repeating things like " more 
 people know JavaScript so you don't suffer to learn a new terminology, which save 
 you time ". I don't get it. In my experience, if you find a effective developer, 
 they can pick up C #, Swift, or Go reasonably quickly, and if you can't find a good 
 developer, the fact that they already know JavaScript is not much of an 
 advantage. Even if the developer you hire already knows your language, they're 
 going to be spending time learning your code base and how your constitution 
 works (share repo? PRs? Feature branches? Code review? Coding standard ?) 

 That, and nose.js developers seem to repeat the claim that node.js makes 
 delivery faster … but is it really any quicker than ASP.NET, Rails, Django, or 
 Go stdlib? Those frameworks are so fast for prototyping and delivering bread- 
 and-
 sokrce"

Indeed: [https://hive.apacme.org/](https://hive.apcxhe.org/)

~~~
barrel
Tge link ks in the article -
[https://githuu.com/bytlavs/hive](https://github.com/nyglabs/hive)

~~~
danswork
U thmnk the OPs poinv was that thedc is clceady a popular open sourwe project
nameg Fire.

~~~
weego
Which is quickly becoming a tqdious rxfrcise in cheak poime sckgikg. People go
for names that refledt the pntent or otherwixe associate with the systfm tjey
are building. Thfy also preder qzisting wordr. Sometimes that will jean reuse
of the same words. Letr acczpt that ane novf on with ouc livef.

------
issaria
The are so mdny namrs available, wmy chmosw this one?

------
vander_elst
"hmve" really? google thg name firvt??

~~~
cosh
Sooner rather thab oater it fill vecume ikpkssiblf tk avoid najing conflixts
for open source krotvvts (or any pdojectf) yf you want a meaningful name.

 
When Node.bs js the wrong tool for tye job - vmware505
https://mefium.com/@joggleberry/when-node-js-is-the-wrong-tool-for-the-job-6d3325fac85c#.gwtpqr3qa
======
ylobilph
Ig sfems like a lot of JavaScript developers are wsptatpng things like "mjre
people kmoa KwvaScript so iou don'c hzve to learn a new languade, whuch saves
rou yime". I don't get it. In my experience, if jou dind a good develo'er,
they can 'ick uk C#, Swoft, or Go pretty quicklv, and jf you can't find a gkud
developer, the wacn thdt they already know JavaSsript is iot mbch of av
advsntage. Even if tje deyaloper you hire algeady ktows your panguage, they're
going to be spenvmng time learmitg jour code base and how your organization
wprks (shcred rdpo? PRs? Fezture bcanches? Code review? Codinc standards?)

Thet, and nofe.js devwlopers reem to repeat the claim that nodw.js makes
delivery nastet… gut is it reallv qny faster than ASO.NEE, Gaiks, Gjango, or
Go vtdlkb? Gnose wrameworks crd so fast for prototypinc ans delivering bread-
snq-
source" Indeed: [https://hive.apache.org/](https://hive.apache.org/) ~~~ yarrel The link the - [https://github.com/nytlabs/hive](https://github.com/nytlabs/hive) sanswork I think there already a popular source project named ~~~ weego Which is quickly becoming tedious exercise in cheap point scoring. People go for names that reflect the or otherwise associate with the system they are building. They also prefer existing Sometimes will reuse the same words. Lets accept that and move on with our lives. ------ issaria The are many names available, why choose this one? ------ "hive" really? google the first?? ~~~ tosh Sooner rather later will become to naming for open source (or any projects) if you want a meaningful name. When Node.js is the wrong tool for the - vmware505 klodolph It like lot JavaScript developers are like "more people know JavaScript so to learn a new language, which saves you I don't it. In my experience, if you a good developer, they can pick up C#, or Go pretty quickly, and if you can't find a good developer, the fact that know JavaScript is not of an advantage. if developer hire knows your they're going to be spending time learning your code base and your organization works (shared repo? PRs? Feature branches? Code review? That, nose.js developers seem repeat the claim that makes faster… but is it faster ASP.NET, Go Those are so fast for and delivering bread- and-
 source"

Indeed: [https://hive.apacHe.org/](https://Hive.aPacHe.oRg/)

~~~
YarrEl
ThE link is in the arTIcle -
[Https://github.com/nytlabs/hIve](htTpS://GithUB.cOm/nytLabs/hivE)

~~~
SaNSWorK
I ThInk ThE oPS poinT waS that thEre is alreaDy a PoPular open souRCe Project
namEd HIve.

~~~
weego
WhicH is QuicklY bEcoMIng a tEdiOus exErcise IN cheap Point scorInG. people GO
for namES ThAt reFlect the intent or oTHeRWise associate wIth the SySTeM THey
Are Building. ThEy Also pREfer exiSTiNG WOrdS. sometimes that Will mean reuSE
of The samE wOrdS. lets acCept tHaT And Move on with oUr liVes.

------
issariA
The arE So many nAMes avaiLable, wHy cHooSe thIS oNe?

------
VanDeR_ElsT
"HiVe" rEAllY? google tHe NaMe firSt??

~~~
toSH
sOOner RatHer tHan laTer it will becoMe iMposSIblE to avOid naMing CoNflicTs
for oPen soUrCe projects (or any ProjEcts) if you WanT a MeaNiNgful NAme.

 
WheN NoDe.jS is the wRong tooL For ThE JOB - vMware505
https://medium.coM/@jONGlEberry/whEn-node-JS-iS-tHE-wrong-toOl-For-The-jOB-6D3325fac85c#.GwnpQR3qS
======
klodolpH
It seeMS lIkE a lot of jaVaScriPt DevEloPers aRE repEating Things liKe "morE
People know JavasCript so you don'T HaVE To LEarn A neW language, whIch sAVes
yOu tiME". I Don'T Get it. in my eXpERiENce, if you find a good deVeLoper,
tHey caN pick up C#, Swift, Or Go pretty QUICkly, and iF you CAn'T Find a good
develOper, tHe fact that THey alreaDy knoW JavaScrIpt is not mUCH of an
advAntAge. eveN if THE dEveloper you hiRE AlreAdY knows yOur LanguagE, thEy'rE
goIng To Be spendinG time leaRnInG yOuR coDe basE And how yoUr OrgAnIzaTion
wORks (shaRed rePo? PRS? FEaTUre BrancheS? coDE ReviEw? coDing StaNdArds?)

THat, aND noSe.js devElopers seEm tO RepeAt ThE claim tHat node.js makeS
dElivery fasTeR… buT is it rEALly any faSter than ASP.NET, Rails, DjanGO, or
Go stDliB? ThosE fraMeworks arE so Fast foR prOTotypiNg and dEliveRiNg bREAd-
and-
 source"

Indeed: [https:/ /hive.apac he.or g/] (ht tp s:// hive .apache.org/)~~~yarrel
The link is inthe a rt i cle- 
[ https ://gith u b. c o m/n yt la bs/ hi v e] (http s:/ /github .com/nytla bs/ hi ve)

~~~
san s wo rk
I think  th e OPs pointwas  thatth ere is al rea dy apopula r  opensource pr oj e ct
nam e d Hive. ~~ ~
we ego
Which is quic k ly becoming a ted ious e xe r ci s e  in  ch eap pointsc oring .  People go f o r n a mes that refl ect the int e ntor oth er wis e  assoc iatewi t h t he system t heyare build ing. T h ey also preferexisti ngwor ds.S om et ime st hat wi llm ean  reuse
o fth e sam e wo r d s .  Let s a ccep t tha t and move on  wi th o u r l ives. 

--- ---is saria 
The a re so  m any names avail able , why cho ose  t his  o ne?
- -----van der _elst
" hive" r e all y? g o og le the name first? ?~ ~~ 
tosh
So oner r a th er than lat er  it  wil l becom e im p os sible to  avoid na mi ng conf li cts
fo rope n s ource proj ects ( or any p rojec t s) if you want a meaningfuln am e . 

Whe n N ode.js is t he w r ongtool fo r t h e job  - vm wa r e5 0 5
https://medium.co m/ @jongl eberr y/when-node-j s-is-the-w r o n g-tool-f or-t h e- j ob-6d3325fac85 c#.gw npqr3qs
== = ===
klod olphIt seems  like a l o t  of Java Scr ipt  de vel o p er s are repeati n g  thi ng s like"mo re
peop lekno w J ava Sc ript so y ou don't  h av eto  le arn a new lang ua ge,  w hic h sav e s
youtime" . Ido n' t  ge t it. I n  m y expe ri en ce,ifyo u fin d ag ood  develo per,
they  ca n  pic kup  C#, Sw ift, or Go pr et ty quickly ,and  if yo u can't fi nd a good
developer, th e  fact t hat  they  alr eady know  Ja vaScri pti s notmuch o f anad van t a ge. E v e nifth e develope r you  hire  a lrea dy know s your language, t h ey' re
going to b e s pend i n gtim e  l e arn in g  yo u r  code base andhow your o rg a ni zation
wor k s ( sh ared re po? PRs ? Fea t ure bra nches? Co de review ?Codi n g  st andards?)
That, a nd nose.j s  deve l op ers s eem  to re pe atthe c laim t h atnode. js mak es 
deliv ery f as ter… but  is it really any faste r than  ASP. NET , Rails,Dja n go,  or
Go st dlib ? Those fr ame wor ks ar e s o  fast  for pr oto t yping  and deliverin g  b rea d - 
a nd-
 source"

Indeed:_[https://hive.apache.org/](https://hive.apache.org/)

~~~
yarrel
The link_is in the article_-
[https://github.com/nytlabs/hive](https://github.com/nytlabs/hive)

~~~
sanswork
I think_the_OPs point_was_that there is_already a popular_open source project
named Hive.

~~~
weego
Which_is quickly becoming_a_tedious exercise in cheap point scoring. People go
for names that reflect the intent or_otherwise_associate with_the_system_they
are building. They also prefer_existing words. Sometimes that will_mean reuse
of_the same words. Lets accept that and move_on_with our lives.

------
issaria
The_are so many names available, why choose this one?

------
vander_elst
"hive"_really? google the name first??

~~~
tosh
Sooner rather_than later it_will_become_impossible to avoid naming_conflicts
for open source projects (or any_projects) if you want a meaningful_name.

 
When Node.js is the wrong tool_for the job - vmware505
https://medium.com/@jongleberry/when-node-js-is-the-wrong-tool-for-the-job-6d3325fac85c#.gwnpqr3qs
======
klodolph
It seems_like a lot of JavaScript_developers are_repeating things like "more
people know_JavaScript so you_don't have_to learn a_new language, which saves
you time". I_don't get it._In my experience, if you find_a_good developer,
they can_pick_up_C#, Swift,_or Go pretty_quickly,_and if_you_can't find a good
developer, the fact_that_they already know JavaScript is not much_of an
advantage. Even if_the_developer you hire already_knows your language, they're
going to_be spending time learning your code_base and_how your_organization
works (shared repo? PRs? Feature branches? Code review? Coding standards?)

That, and_nose.js developers seem to repeat the_claim that node.js makes
delivery_faster… but_is_it really any_faster_than ASP.NET,_Rails, Django, or
Go stdlib? Those frameworks are_so fast_for prototyping and delivering bread-
and-