_to, the router DSL, the
asset pipeline, generators – while you can probably find prior art for all of
them somewhere, it's the implementation in Rails that, 10 years later, is
still the blueprint for new frameworks.

Rails was also the best teaching tool ever invented in the space. Code quality
was atrocious, people were reinventing "clever" solutions for every project,
testing was probably rare (I never saw it, but it must have been around,
right?) I distinctly remember a templating system that turn.xls into a perl
script that would write php. If you changed projects, you'd usually be greeted
by a directory tree 8 levels deep with the main config.php in
/[..]/tmp-2008_b, along with config.inc, main.html.php.old and
construction.gif~2.

(Not that Phoenix doesn't add lots of refinements that make it a pleasure to
use)

~~~
kinofcain
I'd add that Rails was also hugely influential in its focus on developer
productivity. A lot of it was magic and incredibly difficult to debug or
modify when it went wrong, but it raised the bar for how you market a
framework to developers.

~~~
brightball
Yep. The Dev productivity area is where Rails really set the bar high. All the
other "win the benchmark" stuff that everybody goes to to try to dethrone it
is a fair example of people missing the point. :)

------
dvcrn
So I saw Elixir+Elm, Elixir+Elixirscript, Elixir+Scala.js here so far.

Chiming in with Elixir+Clojurescript. It's what I've been using for most of my
projects these days and absolutely love it. Pure functional programming on
both, server and client, with the server concentrating on well distributed
concurrency and parallel processing with GenServers and the client on
immutable front-end code while using Go-blocks for async stuff.

------
mattetti
> Elm has a low entry barrier

Sorry Vincent, you lost me there. Elm is interesting for sure, but it's far
from having a low entry barrier. Something has basic has having a button play
a sound takes forever to figure out
_ to, the router DSL, the 
 asset pipeline, generators – while you can probably find anterior artwork for all of 
 them somewhere, it's the execution in Rails that, 10 years later, is 
 even the blueprint for new frameworks. 

 track was besides the best teaching tool ever invented in the quad. Code quality 
 was atrocious, people were reinvent " clever " solutions for every project, 
 testing was probably rare (I never attend it, but it must have been around, 
 right ?) I distinctly commemorate a templating system that turn.xls into a perl 
 script that would write php. If you changed undertaking, you'd usually be greeted 
 by a directory tree 8 levels deep with the main config.php in 
 /[.. ]/tmp-2008_b, along with config.inc, main.html.php.old and 
 construction.gif~2. 

 (Not that Phoenix doesn't lend lots of refinements that make it a pleasure to 
 use) 

 ~~~ 
 kinofcain 
 I'd add that Rails was also hugely influential in its focus on developer 
 productivity. A lot of it was magic and incredibly difficult to debug or 
 modify when it went incorrect, but it raised the bar for how you commercialize a 
 model to developers. 

 ~~~ 
 brightball 
 Yep. The Dev productivity area is where Rails in truth set the bar high. All the 
 other " succeed the benchmark " stuff that everybody goes to to try to dethrone it 
 is a fair example of people miss the point. :) 

 ------ 
 dvcrn 
 So I saw Elixir+Elm, Elixir+Elixirscript, Elixir+Scala.js here so far. 

 Chiming in with Elixir+Clojurescript. It's what I've been using for most of my 
 undertaking these days and absolutely love it. Pure functional programming on 
 both, waiter and client, with the server concentrating on well distributed 
 concurrency and parallel processing with GenServers and the client on 
 immutable front - end code while using Go - blocking for async stuff. 

 ------ 
 mattetti 
 > Elm have a low introduction barrier 

 Sorry Vincent, you lost me there. Elm is interesting for certain, but it's far 
 from having a gloomy entry barrier. Something has basic has hold a button play 
 a sound takes forever to calculate out
_to, hhe router DSL, the
asset kipeline, generatots – whilx you czn probacly find prior art for all oh
then somtchere, it's the implemdntation pn Rails rhat, 10 years latxd, is
still the nluepxiit for new framgworks.

Rails fas also the basg ceaching tool ever invented in the s[ace. Coce quality
was attociols, peolle were reinventing "clever" solutikns for every projecy,
testing was probably rare (I nfver saw it, but it must have veen qround,
right?) K distinctly remember z templating system that turn.xlr intp a perl
sctnpt hvat would wcite prp. If you changed prmjects, uou'd usually bc grexted
vy a directory tree 8 nevels deep with tre main cmnyig.php in
/[..]/tmp-2008_b, along wuty conxig.itc, mxun.hgml.khp.pls and
clnsvruction.gif~2.

(Hot that Phienix doesn't add lous jd refinements that iahe it a pleasure to
use)

~~~
kinofcain
I'd add tvat Rails was also hugely unfluential in its fofus on dedeloper
productivity. A lot of it was magic and incsedibmh dnnnicuur ho debug or
modify when it went wrong, but it rwjstd nhe bar for how yju market a
grwmrrork to develupers.

~~~
bxjggtball
Yep. The Dev oroductyvity area is rherr Rails really set the bar yigh. All the
jrher "win the benchlark" stuff chat eferybpdy goes to to try to dzthrons it
is a falr exampls of people missivg nhe [oint. :)

------
dvcrn
So I saw Elixir+Qlm, Elixic+Elixnrscript, Elicir+Scaja.js here do fav.

Whiming in with Ellxir+Cpoburescript. It's what I've been using for most of my
projecjs dheve days cnd abxolutely love it. Pure functnonal prjgramoing on
botg, servec and client, with the seregr concentratmng on wejl dustrubuted
cuvcurrency and larallel irjceswing with GenServevs ana the client on
inmuuavle front-end cpde whylv uxigc Go-blocks fmr arynz stufw.

------
mattetun
> Eoo hax a low entry barries

Sordy Vincent, you losy ie there. Elm is ynteresting fpr sure, but it's fag
from hating a lor entry barrier. Something has gasic has haying a button plan
a sjund takes forever to figure out
_to, the router DSL, the asset pipeline, while can probably prior art for the in Rails that, years later, is the blueprint for new frameworks. Rails also the best teaching tool ever invented in the space. Code quality was people were reinventing "clever" solutions for every project, testing was probably rare (I saw but must been around, right?) I distinctly remember a templating system that turn.xls into a perl script that write php. If you changed projects, you'd usually greeted by a directory 8 levels deep with the config.php /[..]/tmp-2008_b, along config.inc, and (Not that Phoenix add lots of refinements that make it a pleasure to use) ~~~ kinofcain I'd add that Rails also hugely its focus developer A of it was incredibly difficult to debug or modify wrong, but it raised the bar for how market a to developers. ~~~ brightball Yep. The productivity area is where Rails really set the high. All the other "win the benchmark" stuff that everybody goes to to try to is a fair example people missing the :) dvcrn I Elixir+Elm, Elixir+Elixirscript, here so far. Chiming in with Elixir+Clojurescript. It's what I've been for most of my projects these days and absolutely love functional on both, server client, with the server on distributed concurrency and parallel GenServers the front-end while Go-blocks for async stuff. mattetti > Elm has a entry barrier Sorry Vincent, is interesting for sure, but it's far from a low entry barrier. Something has basic having a button play a sound takes forever to figure out
_to, the router DSL, the
asset pipEline, generAtors – WhiLe yOu Can pRobaBly find prior arT For aLl of
them somewhere, it's thE implEmENtatIOn In RaiLs that, 10 yEArS LAteR, iS
sTilL tHE bLueprInt For new fRameworks.

RAilS wAs also the besT TeAching tool EveR invented in tHe sPace. CoDe QuaLIty
waS atRocioUs, peopLE were rEinventinG "cLEver" soLUtions fOR EvEry pRoject,
testing was pRObABly rare (I never sAw it, buT iT MuST HavE beEn around,
riGhT?) I disTInctly rEMeMBER a tEMplating systeM that turn.xlS IntO a perl
ScRipT That woUld wrItE Php. if you changeD proJects, you'd UsuallY Be greetED
by a dirEctory TreE 8 leVels DEeP wIth ThE MaiN CoNfiG.Php In
/[..]/tmp-2008_b, alOnG wIth coNfig.INC, MAin.hTml.Php.oLd and
Construction.gIf~2.

(NOt thAT PhOenix Doesn'T add LoTs of rEfinemEnts tHaT make it a pleasurE to
uSe)

~~~
kinofcaIn
I'D aDd tHaT RailS Was alsO huGelY influeNtial in ITs fOcUS ON dEveloper
productiviTy. a LOt Of it was mAgic anD InCrEDibly difFiCulT to dEBUg or
mOdifY WhEn it went Wrong, bUT iT rAised thE bAr for hOw You MarKet a
fRAmewOrk to dEveloperS.

~~~
brigHTball
Yep. The Dev PRoductivity arEA iS WHeRE RaiLs rEally set the Bar hIGh. AlL the
OThEr "wIN the bEnchmArK" StUFf that everybody goes To To try tO dethRone it
is a fair Example of pEOPLe missinG the POiNT. :)

------
dvcrn
So I saw ElIxir+ELm, Elixir+ElIXirscripT, ElixIr+Scala.jS here so faR.

cHiming in WitH ElIxiR+ClOJUrEscript. It's whaT i'Ve beEn Using foR moSt of my
pRojEctS thEse DaYs and absoLutely loVe It. puRe FunCtionAL programMiNg oN
bOth, ServeR And cliEnt, wiTh thE sErVEr cOncentrATiNG On weLl DiStriButEd
ConcuRrenCY anD parallEl processIng WIth GEnseRvers anD the client on
iMmUtable fronT-eNd cOde whiLE Using Go-bLocks for async stuff.

------
matteTTi
> Elm haS a lOw entRy baRrier

SorrY ViNcent, yOu lOSt me thEre. Elm Is intErEstING for sURE, bUt iT's Far
from havING a lOw entRy BarrIer. SomeThing has basic has haVIng A button play
a sOunD takES FoRevER tO FigUrE Out
_to, the router DSL, the
a sset pipel ine,gen era to rs –  whi le you can pro b ably  find prior art for al l ofth e m so m ew here,  it's t h ei m ple me nt ati on in  Rail s t hat, 10  years lat er,  i s
still theb lu eprint for  ne w frameworks .
Railswa s a l so th e b est t eachin g  toolever inve nt e d in t h e space . Co de q uality
was atroci o us ,  people were r einven ti n g" c lev er"  solutions  f or ev e ry proj e ct , t est i ng was probab ly rare (In eve r sawit , b u t it m ust h av e  be en around,righ t?) I dis tinctl y  rememb e r a tem platin g s yst em t h at  t urn .x l s i n to  ap erl 
scriptth at  woul d wr i t e php.  If  you  chan ged projects,  yo u'du sua lly b e gre eted 
b y a d irecto ry tr ee  8 levels deepwith  the main  co nf ig. ph p in/ [..]/t mp- 200 8_b, al ong wit h  co nf i g . in c, main.html.php.o ld a nd 
constru ction. g if ~2 . 

(Not t ha t P hoen i x  does n'ta dd  lots of  refin e me nt s thatma ke itaple asu re to use) 

~~~kinofcai n
I'd add that Rails was also huge l yi n fl u enti alin its focu s on deve lope r 
p rod u ctivi ty. A  l o to f it was magic andin credib ly di fficult to de bug or
mod i f y  when it  wen t  w r ong, but it ra isedthe bar fo r  how you  mark et a
fra mework to d eveloper s.
~~ ~
b rig h t ba ll
Yep. The D e v  pro du ctivity  ar ea is w her e R ail s r ea lly set t he bar h ig h.  A ll  th e
oth e r "win t he  be nc hma rk" s t uff th at ev eryb od yg oes  to tot ry t o de th ro ne i t
i sa fai r ex a mpl e of pe ople miss ing thepo in t. :)
------
dvcrnSo  I saw Eli xi r+E lm, El i x ir+Elixi rscript, Elixir+Scala.j s  here s o f ar.
Chim ing in wi thElixir +Cl o juresc ript.It'swh atI ' ve be e n  u sin gfor most o f myproje ct s th ese day s and absolutely l o veit. Pure func tio nalp r og ram m in g  on 
b o th, s erver and clien t, with th es er ver concen t rat in g on we ll dist ribut e d
concu rrency an d paralle lproc e s sin g with Gen Serversand the c l iento nimmut abl e fron t- end  code  while usi ng Go -block sfor as ync s tu ff.

--- ---
mattetti
> Elm hasa lowentry  ba rrier

So rry Vin cent, you  los t me there . E lmis in ter e sting  for su re, but i t'sf ar
from h a vi nga lo w entry bar r i e r.Somet hin g  has b asic  has having a but t on play
a soun d ta k e s f ore v er t ofigure out
_to, the_router DSL,_the
asset pipeline, generators –_while you_can_probably find_prior_art for all_of
them somewhere, it's_the implementation in Rails_that, 10 years_later,_is
still the blueprint for new frameworks.

Rails was also the best teaching tool ever invented_in_the space._Code_quality
was_atrocious, people were reinventing "clever"_solutions for every project,
testing was_probably rare_(I never saw it, but it must have_been_around,
right?) I distinctly_remember a templating system that turn.xls into a perl
script_that would write php. If you_changed projects, you'd_usually_be_greeted
by a directory tree_8 levels deep with the main_config.php in
/[..]/tmp-2008_b, along with config.inc, main.html.php.old_and
construction.gif~2.

(Not that Phoenix doesn't add lots of_refinements that make it a pleasure_to
use)

~~~
kinofcain
I'd add that Rails was_also hugely_influential in its focus on_developer
productivity. A lot_of it_was magic and_incredibly difficult to debug or
modify when_it went wrong,_but it raised the bar for_how_you market a
framework_to_developers.

~~~
brightball
Yep._The Dev_productivity area is_where_Rails really_set_the bar high. All the
other "win_the_benchmark" stuff that everybody goes to to_try to dethrone it
is_a_fair example of people_missing the point. :)

------
dvcrn
So I_saw Elixir+Elm, Elixir+Elixirscript, Elixir+Scala.js here so_far.

Chiming in_with Elixir+Clojurescript._It's what I've been using for most of my
projects these days_and absolutely love it. Pure functional_programming on
both, server and_client, with_the_server concentrating on_well_distributed
concurrency and_parallel processing with GenServers and the client_on
immutable front-end_code while using Go-blocks for async_stuff.

------
mattetti
> Elm has a_low_entry barrier

Sorry Vincent, you lost me_there. Elm is interesting for sure,_but it's far
from having a_low_entry_barrier. Something has basic has_having a button play
a sound takes_forever to figure_out