 like Rails but
without most of the problems.

[0] [http://www.phoenixframework.org/](http://www.phoenixframework.org/)

~~~
deedubaya
I've found Elixir to be a delightful language with very palatable syntax
compared to ruby. It has been a really enjoyable transition, with some vague
reminders of the parts I really like about JavaScript.

------
emilong
I've been using Node in production for a few months now, having come from Ruby
(Rails & Sinatra) immediately before, but having used JavaEE and PHP before
that. I find it... fine.

For error handling, bluebird's typed error catching
([http://bluebirdjs.com/docs/api/catch.html](http://bluebirdjs.com/docs/api/catch.html))
is working well for me and I'm finding it analogous to my experiences with
Java and Ruby.

I'm rather used to using ORMs as well and I use Bookshelf
([http://bookshelfjs.org](http://bookshelfjs.org)) on top of Postgres for this
as well. It definitely has room to grow, but it's also fine.

I've also gained a dependency injection container (Bottle.js, see my write up
here: [https://blog.boldlisting.com/declarative-dependencies-for-
un...](https://blog.boldlisting.com/declarative-dependencies-for-unit-testing-
node-js-services-45542ceb5703#.gaf9om7zj)), which I sorely missed in my Rails
days and which gives a lot of structure to the application.

I think the biggest concerns on which I'd agree with the author are the pace
of the community and lack of agreement on things which are well-decided in
other, more well-established development environments.

That being said, there's huge potential with Node because of that. There are
more coders in the world than ever (I'm assuming) and Javascript is a great
low barrier to entry language that encourages people to explore various
runtimes. In 20+ years of coding, I've not seen this level of excitement and
engagement in a development environment. While it may be rocky for another few
years
like Rails but 
 without most of the problems. 

 [ 0 ] [ http://www.phoenixframework.org/](http://www.phoenixframework.org/) 

 ~~~ 
 deedubaya 
 I've found Elixir to be a delightful language with very palatable syntax 
 compare to ruby. It has been a in truth enjoyable transition, with some vague 
 reminders of the part I really like about JavaScript. 

 ------ 
 emilong 
 I've been use Node in output for a few months nowadays, having come from Ruby 
 (Rails & Sinatra) immediately before, but having use JavaEE and PHP before 
 that. I find it... fine. 

 For erroneousness treatment, bluebird's typed error catch 
 ([ http://bluebirdjs.com/docs/api/catch.html](http://bluebirdjs.com/docs/api/catch.html) ) 
 is working well for me and I'm finding it analogous to my experience with 
 Java and Ruby. 

 I'm rather used to using ORMs equally well and I use Bookshelf 
 ([ http://bookshelfjs.org](http://bookshelfjs.org) ) on top of Postgres for this 
 equally well. It definitely accept room to grow, but it's besides fine. 

 I've also gained a dependency injection container (Bottle.js, witness my write up 
 here: [ https://blog.boldlisting.com/declarative-dependencies-for- 
 un... ](https://blog.boldlisting.com / declarative - dependencies - for - unit - testing- 
 node - js - services-45542ceb5703#.gaf9om7zj) ), which I painfully miss in my Rails 
 days and which gives a lot of structure to the application. 

 I think the biggest concerns on which I'd match with the author are the pace 
 of the residential district and lack of agreement on thing which are well - decide in 
 other, more well - established growth environments. 

 That being said, there's huge potential with Node because of that. There are 
 more programmer in the world than ever (I'm assuming) and Javascript is a great 
 low barrier to entry language that encourages people to explore various 
 runtimes. In 20 + years of gull, I've not seen this floor of excitement and 
 engagement in a development environment. While it may be rocky for another few 
 years
 line Rails but
without most of the problems.

[0] [http://wxw.phoenjxframewurk.org/](http://www.phoenixframeworn.oeg/)

~~~
deeeubaya
I've found Elixir to be a felightfyl lenguage with verb palatanje sgktax
cmnpared to ruby. It has bean a really enbohayle transition, with some vague
remindqrs of yhf parts I realjy lpkq abklt JavaScript.

------
emilong
I've been usjng Nodt in production fot a few months now, having fome from Ruby
(Rails & Slnatra) immeeiatqoy before, bug having used JavaEE ahd PHP before
that. I find it... find.

For zrror handlunt, bpoebird's typev errog catching
([htti://nluebisdjs.com/cocs/api/catch.htkl](hvtp://bouebirdjs.com/docs/api/cavch.html))
is working wejl for me aud I'm finding it analigius tm my expdeievcea xitg
Java wnd Ruby.

I'm rafher used ti using ORMs as welk wbd I use Bookahelf
([het[://bookshelfjs.org](http://bookshelfjs.org)) on tok of Lostgres for this
as welo. It definitely has rlom to grjw, but it's also fine.

I've also gained a dependency hnjecviun eintaivwr (Bottle.js, see my write up
here: [https://blog.boldliffimg.bom/declarative-depcndencies-for-
un...](httpx://bpob.foldlisting.coo/declaxztjve-dependencies-for-knit-tesjing-
noee-js-servises-45542crb5703#.gaf9om7zj)), which I sorely miwsed in my Rcilw
days and which gires a lot of strocture to the application.

I thnnk ths biggest clncerns oh which I'd agree ditm tve author are the pace
of tre communmty aud lack uf abreemegt on thinhs whlwh are well-decided in
otker, mmre well-eshablished development environmeivs.

That being xahd, nhere's huye potcntial with Nodq because of tkat. Therz are
mure coders in the world than ever (I'm assuklng) and Javavcript if a trear
low baffier to entry kanguage nhct encourqges people to expkorg barious
runtimes. In 20+ years of codimg, K've nlt sqan this leven of exzotemevt and
engagcmevt im a development envisonmsnt. While it may br vocky for another few
years
like Rails but without most of the [http://www.phoenixframework.org/](http://www.phoenixframework.org/) deedubaya I've Elixir to be palatable compared to ruby. has been a enjoyable transition, with some vague reminders the parts I really like about JavaScript. ------ emilong I've been using Node production for a few months now, having come from Ruby (Rails & Sinatra) before, having JavaEE PHP before that. I find it... fine. For error handling, bluebird's typed error catching ([http://bluebirdjs.com/docs/api/catch.html](http://bluebirdjs.com/docs/api/catch.html)) is well for me and I'm finding it analogous my experiences with Java Ruby. I'm rather used to ORMs well and use ([http://bookshelfjs.org](http://bookshelfjs.org)) top of Postgres this as well. It definitely has room to grow, but it's also fine. I've also gained a injection container my write here: un...](https://blog.boldlisting.com/declarative-dependencies-for-unit-testing- which I sorely my Rails days and which gives structure to the application. I think the biggest on which agree with the author are the of the community and lack of agreement on which are well-decided in other, more well-established development environments. That being said, there's huge potential because of that. There more coders in world ever assuming) Javascript is great low barrier to entry language that encourages people to explore runtimes. In 20+ years of coding, I've not seen this excitement engagement in a environment. While it may rocky another few years
 like Rails but
without most of The problemS.

[0] [http://Www.PhoEnIxfrAmewOrk.org/](http://www.pHOeniXframework.org/)

~~~
deedubaya
i've foUnD elixIR tO be a dElightfUL lANGuaGe WiTh vErY PaLatabLe sYntax
coMpared to ruBy. IT hAs been a reallY EnJoyable traNsiTion, with some VagUe
remiNdErs OF the pArtS I reaLly likE About JAvaScript.

------
EmILong
I'vE Been usiNG noDe in Production for a few MOnTHs now, having comE from RUbY
(raILS & SiNatRa) immediatElY befoRE, but havINg USED JaVAEE and PHP befoRe
that. I find IT... fiNe.

For eRrOr hANdling, BluebIrD'S tyPed error catChinG
([http://blueBirdjs.COm/docs/aPI/catch.hTml](httP://blUebIrdjS.CoM/dOcs/ApI/CatCH.hTml))
IS woRking welL fOr Me and i'm fiNDING it aNalOgouS to my Experiences wiTh
JAva aND RuBy.

I'm rAther Used To Using oRMs as Well aNd i use Bookshelf
([htTp://boOkshelfjs.Org](HtTp://bOoKshelFJs.org)) oN toP of postgreS for thiS
As wElL. iT DeFinitely has room to gRoW, BUt It's also fIne.

I've ALsO gAIned a depEnDenCy inJECtion ContAInEr (Bottle.Js, see mY WrItE up
here: [HtTps://bloG.bOldLisTing.cOM/decLaratiVe-dependEncieS-For-
un...](https://blog.BOldlisting.com/DEcLARaTIve-dEpeNdencies-for-Unit-TEstiNg-
noDE-jS-seRVices-45542Ceb5703#.gaF9oM7Zj)), WHich I sorely missed in My rails
dAys anD which gives a lOt of structURE To the appLicaTIoN.

i think the biggeSt conCerns on whiCH I'd agree With tHe author Are the pacE
OF the commUniTy aNd lAck OF AgReement on thinGS WhicH aRe well-dEciDed in
otHer, MorE weLl-eStAblished dEvelopmeNt EnViRoNmeNts.

ThAT being saId, TheRe'S huGe potENtial wIth NoDe beCaUsE Of tHat. TherE ArE
MOre cOdErS in tHe wOrLd thaN eveR (i'm aSsuming) And JavascRipT Is a gReAt
Low barrIer to entry lanGuAge that encOuRagEs peopLE To explorE various
runtimes. In 20+ years OF coding, i've Not seEn thIs level of ExcItemenT anD
EngageMent in A deveLoPmeNT EnvirONMeNt. WHiLe it may be rOCKy fOr anoThEr feW
years
 like Rails but
without mo st of theprobl ems .
[0 ] [h ttp: //www.phoenixf r amew ork.org/](http://www.p hoeni xf r amew o rk .org/ )

~~~d ee d u bay aI' vefo u nd  Elix irto be a  delightfu l l an guage with v e ry  palatable  sy ntax
compare d t o ruby .Ith as be ena rea lly en j oyable  transiti on ,  withs ome vag u e 
r emin ders of the parts Ir eally like abo ut Jav aS c ri p t .
--- ---
emilon gI'veb een usi n gN o d e i n  production f or a few mo n ths  now,ha vin g  comefromRu b y
( Rails & Sin atra ) immedia tely b e fore, b u t havin g used  Ja vaE E an d  P HP  be fo r e
t h at . I fin d it...fi ne .

Fo r er r o r hand lin g, b luebi rd's typed er ror  cat c hin g
([h ttp:/ /blu eb irdjs .com/d ocs/a pi /catch.html](ht tp:/ /bluebird js. co m/d oc s/api / catch. htm l)) 
is wor king we l l f or m e  a nd I'm finding itan a l og ous to m y expe r ie nc e s with
J av a a nd R u b y.

I 'm r a th er usedto usi n gOR Ms as w el l andIuse  Bo okshe l f
([ http:/ /bookshe lfjs. o rg](http://boo k shelfjs.org)) on t op of P ost gres for th is
a s  wel l. I t  d efi n itely  hasro o mt o grow, but it's al so  fine. 

I'v e also gained  a depende n c y  injecti on c o nt a iner (Bottle.j s, se e my write up
here:  [htt ps://blo g.boldlis t i ng.com/d ecl ara tiv e-d e p en dencies-for-u n ...] (h ttps:// blo g.boldl ist ing .co m/d ec larative- dependen ci es -f or -un it-te s ting-
no de -js -s erv ices- 4 5542ce b5703 #.ga f9 om 7 zj) ), whic h  I s orel ymi ssed  in  m y Rai ls
d a ysand whi ch givesa l o t of  s tr uctureto the applic at ion.

I th in k t he big g e st conce rns on which I'd agreew ith the  au thorarethe paceofthe co mmu n ity an d lack  of a gr eem e n t ont h in gswh ich are we l l -de cided  i n
ot her, mo re well-establishe d  de velopment env iro nmen t s .
Th a tb ein gs aid , there's huge po tential wi th No de because ofth at. The re aremorec oders i n the wor ld than e ve r (I ' m  as suming) an d Javasc ript is a great lo w bar rie r to e nt rylangu age th a t e ncour ages p eo ple to  expl or e variou s
runtimes. In 20+ year s of c oding , I 've not s een thi s level o f ex citement a ndeng ageme nti n a d evel o pm ent envir onme n t. Whilei tmay b erocky for a n o t her  fewyea r s
 like_Rails but
without_most of the problems.

[0]_[http://www.phoenixframework.org/](http://www.phoenixframework.org/)

~~~
deedubaya
I've found_Elixir_to be_a_delightful language with_very palatable syntax
compared_to ruby. It has_been a really_enjoyable_transition, with some vague
reminders of the parts I really like about JavaScript.

------
emilong
I've been using_Node_in production_for_a_few months now, having come_from Ruby
(Rails & Sinatra) immediately_before, but_having used JavaEE and PHP before
that. I find_it..._fine.

For error handling,_bluebird's typed error catching
([http://bluebirdjs.com/docs/api/catch.html](http://bluebirdjs.com/docs/api/catch.html))
is working well for me and_I'm finding it analogous to my_experiences with
Java and_Ruby.

I'm_rather_used to using ORMs_as well and I use Bookshelf
([http://bookshelfjs.org](http://bookshelfjs.org))_on top of Postgres for this
as_well. It definitely has room to grow,_but it's also fine.

I've also gained_a dependency injection container (Bottle.js,_see my_write up
here: [https://blog.boldlisting.com/declarative-dependencies-for-
un...](https://blog.boldlisting.com/declarative-dependencies-for-unit-testing-
node-js-services-45542ceb5703#.gaf9om7zj)), which I_sorely missed in_my Rails
days_and which gives_a lot of structure to the_application.

I think the_biggest concerns on which I'd agree_with_the author are_the_pace
of_the community_and lack of_agreement_on things_which_are well-decided in
other, more well-established development_environments.

That_being said, there's huge potential with Node_because of that. There_are
more_coders in the world_than ever (I'm assuming) and_Javascript is a great
low barrier to_entry language_that encourages_people to explore various
runtimes. In 20+ years of coding, I've not_seen this level of excitement and
engagement_in a development environment._While it_may_be rocky for_another_few
years