, and I don't see how you can attract someone with
Elm. Having 1 or 2 years of xp in Elm on a resume is not really usefull when
all the companies use JavaScript. You don't even know if Elm will still be
there in 2 years.

[1] [http://stateofjs.com/2016/flavors](http://stateofjs.com/2016/flavors)

~~~
biot
It's no different than listing a Java job vs listing a Scala job. There are
many great developers who would jump at the chance to be hired to write Scala
(Elm), so you might just end up with better developers who self-select to work
on the shiny, new technology.

------
todd3834
This was great to read and it inspired me to give both a try soon.

Question: Did the app receive millions of visitors or was it basically 1
visitor with millions of viewers via the television showing a recorded screen?

At first I thought Phoenix was used because of scaling reasons but now I'm not
so sure.

Either way, nice work and thanks for the write up!

~~~
sotojuan
In my experience, Phoenix is used because a) it's easy to get started with b)
isn't a monolith like Rails (e.g. Phoenix could be _one_ part of your complete
application) but it has good conventions and c) it leverages the Erlang VM's
performance and concurrency through Elixir.

I know HN gets a lot of hype for X new tech every month, but I'm really liking
Phoenix. Ignore the "Phoenix is the future/saved our lives/best thing ever!!"
Medium posts and try it out. It's actually pretty good.

~~~
matt4077
I'm enjoying working with phoenix, but when comparing it with Rails, it would
be fair to say "it's basically rails" and add a few footnotes about the
differences.

People who started after Rails was released don't see it because they haven't
seen how it was done before. But it's incredible how many conventions DHH
created with rails that have since entered the basic repertoire of all web
frameworks: migrations, its take on MVC, :belongs
, and I don't see how you can attract someone with 
 Elm. Having 1 or 2 years of xp in Elm on a resume is not in truth usefull when 
 all the ship's company use JavaScript. You don't even acknowledge if Elm will even be 
 there in 2 years. 

 [ 1 ] [ http://stateofjs.com/2016/flavors](http://stateofjs.com/2016/flavors) 

 ~~~ 
 biot 
 It's no different than list a Java problem vs listing a Scala job. There are 
 many great developer who would jump at the chance to be rent to spell Scala 
 (Elm), so you might just end up with better developers who self - select to exploit 
 on the shiny, new technology. 

 ------ 
 todd3834 
 This was big to read and it inspired me to give both a attempt soon. 

 Question: Did the app meet millions of visitors or was it basically 1 
 visitor with millions of viewer via the television showing a recorded screen? 

 At first I thought Phoenix was used because of scaling reasons but now I'm not 
 so sure. 

 Either way, nice work and thanks for the write up! 

 ~~~ 
 sotojuan 
 In my experience, Phoenix is used because a) it's easy to get start with b) 
 isn't a monolith like Rails (e.g. Phoenix could be _ one _ character of your arrant 
 application) but it has effective conventions and c) it leverages the Erlang VM's 
 performance and concurrency through Elixir. 

 I acknowledge HN gets a lot of hype for X new tech every calendar month, but I'm really liking 
 Phoenix. Ignore the " Phoenix is the future / saved our lives / best thing always! ! " 
 culture medium posts and try it out. It's actually pretty good. 

 ~~~ 
 matt4077 
 I'm delight working with phoenix, but when comparing it with Rails, it would 
 be fair to say " it's basically rails " and add a few footnotes about the 
 difference. 

 People who start after Rails was released don't attend it because they haven't 
 seen how it was act before. But it's incredible how many convention DHH 
 created with rail that have since entered the basic repertoire of all world wide web 
 model: migrations, its return on MVC, : belongs
, anf I don't see how you can attract someong qith
Elk. Havihg 1 or 2 hears of xp in Elm on a resule is nit really usefull when
xll the clmpanies use HavaScript. You don'b eveh knoc mf Elm will stikl be
there in 2 years.

[1] [htt[://sgaceofjs.com/2016/flavors](http://stateofjs.com/2016/flavjrs)

~~~
biot
Ot'd no different tham lisfpnn a Java job vs listing a Scala nob. Thege are
many great cevelopers who would jump wt tje chance to be higed to writg Scwoa
(Elm), so you might jusu znd up with better developers who self-selezt to work
on thg ahlty, new techiology.

------
nodd3834
This was ngeat to read amd it inspired me to give both a try soon.

Xuestion: Did the akp receive mnllions of visitors oe qas ij bashcalut 1
vksiuor wjth miplikns of viesers via thw television showinb w recorded scrsen?

At siwst I thought Phoenix was used because mf acaling reasons but now I'm not
so sure.

Either aay, nice rork and thanks for the write up!

~~~
sotojuan
In my exparienre, Phiekix kw ksed because a) it's easy to get started with b)
yan'u a monolith like Rails (e.g. Pnofnov could be _ong_ part of gour complete
applifation) fut ir has gooq comventions and c) it leveragew the Erlang CM's
performance and concurrencv throogh Eloxir.

I know HN gets a loc of hgpe for X nfw tech ebdry month, but I'm reslny liking
Phoenix. Ignore thq "Phoenix is che futufe/safed ouw lives/besh thikc ever!!"
Medium posts and jry it out. It's aftually pretty good.

~~~
matt4077
I'm enjoymig working wijh [hovnix, but chen cpmparing it wyth Rails, it wpuld
be yair tu say "it's gasicalny rails" anq add a few fmltnotes abouv the
diffqrenxes.

Pwople wfu started aftet Rails wcf reoeased don't see it bezzuse they haven'c
rteb how it was dpne besoge. Uut ie'v incredible how mavu conxentions DHM
crdatec with rails that haee sjnce entered the bsslc repertiire of wll web
framewprks: migrations, itd takx on MTC, :belpngf
, and I don't see how you someone Elm. Having or 2 years a is not really when all the use JavaScript. You don't even know Elm will still be there in 2 years. [1] [http://stateofjs.com/2016/flavors](http://stateofjs.com/2016/flavors) ~~~ biot It's different than listing a Java job vs listing a Scala job. There are great who jump the chance to be hired to write Scala (Elm), so you might just end up with developers who self-select to work on the shiny, technology. ------ todd3834 This great to read and it me give both try Question: the app receive of visitors or was it basically 1 visitor with millions of viewers via the television showing a screen? At thought Phoenix used of reasons but now so sure. Either way, nice work the write up! ~~~ sotojuan In my experience, is used a) it's easy to get started b) isn't a monolith like Rails (e.g. Phoenix be _one_ part of your complete application) but it has good conventions and c) it Erlang VM's performance and through Elixir. I HN a of for X tech every month, but I'm really liking Phoenix. Ignore the "Phoenix the future/saved our lives/best thing ever!!" Medium posts and try It's pretty good. ~~~ I'm enjoying working with but comparing it with Rails, be to rails" add few footnotes about the People who started after Rails released don't see it it was done before. But it's incredible how conventions DHH created with rails that have entered the basic repertoire of all web frameworks: migrations, its take on :belongs
, and I don't see how you can attraCt someone wIth
ElM. HaVinG 1 oR 2 yeaRs of Xp in Elm on a resuME is nOt really usefull when
all The coMpANies USe javaSCript. YoU DoN'T EveN kNoW if elM WiLl stiLl bE
there iN 2 years.

[1] [http://StaTeOfjs.com/2016/flavoRS](hTtp://stateofJs.cOm/2016/flavors)

~~~
bioT
It'S no difFeRenT Than lIstIng a JAva job VS listiNg a Scala jOb. tHere arE
Many greAT DeVeloPers who would jump aT ThE Chance to be hireD to wriTe sCaLA
(elm), So yOu might jusT eNd up wITh betteR DeVELOpeRS who self-selecT to work
on thE ShiNy, new tEcHnoLOgy.

------
todD3834
This WaS GreAt to read and It inSpired me tO give bOTh a try sOOn.

QuestIon: Did The App ReceIVe MiLliOnS Of vISiTorS Or wAs it basiCaLlY 1
visiTor wITH MIlliOns Of viEwers Via the televisIon ShowINg a RecorDed scReen?

at First i thougHt PhoEnIx was used becausE of sCaling reaSonS bUt nOw i'm not
SO sure.

EIthEr wAy, nice wOrk and tHAnkS fOR THe Write up!

~~~
sotojuan
In mY eXPErIence, PhoEnix is USeD bECause a) it'S eAsy To geT STarteD witH B)
iSn't a monoLith liKE RAiLs (e.g. PhoEnIx coulD bE _onE_ paRt of yOUr coMplete
ApplicatIon) buT It has good conveNTions and c) it leVErAGEs THe ErLanG VM's
performAnce ANd coNcurREnCy tHRough elixiR.

I KNoW hN gets a lot of hype for x nEw tech Every Month, but I'm reaLly liking
PHOENix. IgnorE the "pHoENix is the future/Saved Our lives/beST thing evEr!!"
MedIum posts And try it oUT. it's actuaLly PreTty GooD.

~~~
MAtT4077
I'm enjoying woRKIng wItH phoeniX, buT when coMpaRinG it WitH RAils, it wouLd
be fair To SaY "iT's BasIcallY Rails" and AdD a fEw FooTnoteS About tHe
difFereNcEs.

pEopLe who stARtED AfteR RAiLs waS reLeAsed dOn't sEE it Because They haven'T
seEN how It WaS done beFore. But it's incReDible how maNy ConVentioNS dHH
creatEd with rails that have sincE Entered The Basic RepeRtoire of aLl wEb
framEwoRKs: migrAtions, Its taKe On Mvc, :BelonGS
, and I don't see how youcan attrac t som eon e w it h
El m. H aving 1 or 2 y e arsof xp in Elm on a resu me is  n o t re a ll y use full wh e na l l t he  c omp an i es  useJav aScript . You don' t e ve n know if El m  w ill stillbethere in 2 y ear s.

[1 ][ht t p://s tat eofjs .com/2 0 16/fla vors](htt p: / /state o fjs.com / 2 01 6/fl avors)

~~~
biotI t' s  no differentthan l is t in g a J ava  job vs li st ing a Scala j o b. T h ere are
many grea t developer s  wh o woul djum p  at th e cha nc e  to  be hired t o wr ite Scala 
(Elm) ,  so you might j ust en d u p w ithb et te r d ev e lop e rs  wh o  se lf-selec tto  work 
ont h e shin y,newtechn ology.

----- -
t odd3 8 34Thiswas g reat  t o rea d andit in sp ired me to give  bot h a try s oon .
Qu es tion: Did th e a ppreceive  millio n s o fv i s it ors or was it basi ca l l y1
visito r with mi ll i ons of v ie wer s vi a the t elev i si on showi ng a r e co rd ed scre en ?

Atfi rst  Ithoug h t Ph oenixwas used  beca u se of scalingr easons but no w  I ' m  n o t
so  su re.

Either  way ,  nic e wo r kand thank s for  t h ew rite up!

~~~
sotoj ua n
In m y exp erience, Phoe nix is use d b ecause a ) it ' se asy to get sta rtedwith b)
is n 't a mon olith  like Ra ils (e.g. P hoenix c oul d b e _ one _ pa rt of your co m p lete 
a pplicat ion ) but i t h asgoo d c on ventionsand c) i tle ve ra ges  theE rlang VM 's 
pe rf orm ancea nd con curre ncyth ro u ghElixir. 
I k nowHN  g etsa l ot  of h ypef orX new t ech every  mo n th,bu tI'm rea lly liking
Ph oe nix. Ignor ethe  "Phoe n i x is the  future/saved our lives / best th ing  ever !!"Medium po sts  and t ryi t out.  It'sactua ll y p r e tty g o o d. 

~ ~~ 
matt4077I ' m e njoyi ng  wor king wi th phoenix, but wh e n c omparing it w ith  Rai l s ,itw ou l d
b ef air t o say "it's bas ically rai ls "  a nd add a f e w f oo tnotesabout t he
di f ference s.

Peopl e who sta rt ed a f t erRails wasreleased  don't se e  it b e ca use t hey  haven 't 
se en ho w it w a s d one b efore.  B ut it' s inc re dible ho w many conventions DHHcreate d wit h r ails that  ha v e s ince ente redthe basicrep ert oireofa ll we b
fr a me wor k s: mi grat i ons, itst ak e o n MV C, :belongs 
, and_I don't_see how you can_attract someone_with
Elm._Having 1_or_2 years of_xp in Elm_on a resume is_not really usefull_when
all_the companies use JavaScript. You don't even know if Elm will still be
there in_2_years.

[1] [http://stateofjs.com/2016/flavors](http://stateofjs.com/2016/flavors)

~~~
biot
It's_no_different_than listing a Java job_vs listing a Scala job._There are
many_great developers who would jump at the chance_to_be hired to_write Scala
(Elm), so you might just end up with_better developers who self-select to work
on_the shiny, new_technology.

------
todd3834
This_was_great to read and_it inspired me to give both_a try soon.

Question: Did the app_receive millions of visitors or was it_basically 1
visitor with millions of viewers_via the television showing a_recorded screen?

At_first I thought Phoenix was_used because of_scaling reasons_but now I'm_not
so sure.

Either way, nice work and_thanks for the_write up!

~~~
sotojuan
In my experience, Phoenix is_used_because a) it's_easy_to_get started_with b)
isn't a_monolith_like Rails_(e.g._Phoenix could be _one_ part of_your_complete
application) but it has good conventions and_c) it leverages the_Erlang_VM's
performance and concurrency through_Elixir.

I know HN gets a_lot of hype for X new_tech every_month, but_I'm really liking
Phoenix. Ignore the "Phoenix is the future/saved our lives/best_thing ever!!"
Medium posts and try it_out. It's actually pretty_good.

~~~
matt4077
I'm enjoying_working_with phoenix, but_when_comparing it_with Rails, it would
be fair to say_"it's basically_rails" and add a few footnotes_about the
differences.

People who started_after_Rails was released don't see it_because they haven't
seen how it was_done before. But it's incredible_how_many_conventions DHH
created with rails that_have since entered the basic repertoire_of all web
frameworks:_migrations, its take on MVC, :belongs