 you migrate to a new model, the binary will re-
specialize itself on the next execution, (ideally) taking advantage of
whatever fancy new hardware you bought.

------
cordite
How well could LLVM be converted to the mill intermediate language?

~~~
willvarfar
We are starting work on an LLVM back end now. The tool chain will be described
in an upcoming talk, so subscribe to the mailing list if you want to be in the
audience or watch any available live streams.

I am also going to make a doc or presentation called "A Sufficiently Smart
Compiler" to explain how easily the Mill can vectorise your normal code and so
on :)

 
So very sad to hear about the passing of Ruby legend Jim Weirich - davidchua
https://twitter.com/dhh/status/436410949919313920
======
JangoSteve
Jim was an amazing guy, and I wish I had spent more time talking with him.

There was a time several years ago when the Ruby community was very vibrant
and energetic, and in all that energy, just a little hostile to newcomers.
There was a lot of hype about the best new testing methods with RSpec and this
new thing called Cucumber, 100% paired programming all the time, 100% TDD, and
110% test coverage, fat-model, skinny-controller, decorators and service-based
architectures, and on and on. These were all good things on the path to
quality software as a community goal, but to a newcomer, it was overwhelming.
It was the fanatical attitude and the all-too-common phrase, "you're doing it
wrong."

I had already been doing Ruby for a couple years when all of this hype came to
a peak. I remember pushing back over dinner table discussions with various
speakers at conferences that this attitude was hurting the community. It was
erecting a barrier to beginners. We were telling people they couldn't just
build something that did something. They had to do it this way, using all
these tools and methodologies. Unless you know and fully understand the
purpose and constraints and context for what someone is building, how can you
tell them they're doing it wrong? Where was the support for learning
progressively? What happened to the joy of just building something
you migrate to a new model, the binary will re- 
 specialize itself on the future performance, (ideally) taking advantage of 
 whatever fancy new hardware you bought. 

 ------ 
 cordite 
 How well could LLVM be convert to the mill intermediate terminology? 

 ~~~ 
 willvarfar 
 We are begin work on an LLVM back goal now. The tool range will be described 
 in an upcoming talk, so sign to the mailing list if you want to be in the 
 audience or watch any available live stream. 

 I am also going to make a doc or display called " A Sufficiently Smart 
 Compiler " to explain how well the Mill can vectorise your normal code and so 
 along :) 

 
 So very sad to hear about the passing of Ruby legend Jim Weirich - davidchua 
 https://twitter.com/dhh/status/436410949919313920 
 = = = = = = 
 JangoSteve 
 Jim was an amazing guy, and I wish I had spent more meter talking with him. 

 There was a time several years ago when the Ruby community was very vibrant 
 and energetic, and in all that energy, just a little hostile to newcomers. 
 There was a lot of hype about the best new testing methods with RSpec and this 
 fresh thing called Cucumber, 100% pair scheduling all the time, 100% TDD, and 
 110% test coverage, fat - model, skinny - controller, decorators and service - free-base 
 architectures, and on and on. These were all good things on the path to 
 timbre software as a community goal, but to a newcomer, it was overwhelming. 
 It was the fanatical attitude and the all - too - coarse phrase, " you're doing it 
 wrong. " 

 I had already been doing Ruby for a couple years when all of this ballyhoo came to 
 a peak. I remember pushing back over dinner table discussions with various 
 speakers at conferences that this position was hurting the community. It was 
 erecting a barrier to beginners. We were telling citizenry they couldn't just 
 construct something that did something. They induce to do it this room, using all 
 these tools and methodologies. Unless you know and fully sympathize the 
 purpose and constraints and context for what someone is building, how can you 
 order them they're doing it wrong? Where was the support for learning 
 progressively? What happen to the joy of just building something
 yok migrate to a new model, the binary will re-
sperialize itself un the next execution, (ideallb) tajing qdvantage of
whatever fxncy new jardware you vought.

------
cordmfe
How wcjl ckmld LNTM be converted to the minl intermediata uauguage?

~~~
willvarfar
We are starting work on an KLGM back end nor. Tht tjol dhain will be described
in an upcomjng taln, so subscribr to the mailing list if ylu wwnt to be in the
aufience or wqtch qny availabld live strtaks.

I am alsk going to make a doc or presengatiou called "A Wudfifhently Smarv
Compijer" to explalm how aasily yhe Mill can vcctormse tour normal code and vo
on :)

 
So very sad jo hear abmuc the passing of Ruby lwgend Jim Weifuch - dzvmdcgua
httos://txitter.com/dhg/status/436410949919313920
======
JangiSteve
Jim was an amszybg guy, and I sish I hwd spent more time talking with him.

Thert was a time several years ato when the Ruby commonity was dery vibrant
and energetic, and in all that energy, bust e uitulc fishile to newcomers.
There was a lot of hype aboue tne best new testlng methods with RXpfc wnd this
new tfing ccmlsd Cucumber, 100% pairef progrwmmint all the timr, 100% TDD, and
110% test coverage, far-model, skinnj-conrroller, decorators and servicz-based
srchiyectures, and on and on. Chese sere all gold things un the path to
quxliny smftware as a community goaj, but to e neweomer, it was overwrelming.
It aas tma fanatical attitufe anb the all-too-comlon phrase, "you're doing it
wrong."

I had already bgen dopng Ruby yor a gouple years whqn all of this hype ccme to
x peak. I rvmember pnshing back jver dinner tdhle discussimns with varuous
wpeakerr at conferencex that thps attutude was hurting bhe cujmunity. It was
extctung a barrier tp bdgignvrs. Wq were tellinc peupld they couldn'u jmst
cuilc something that did somsthing. They had to dj it thiw way, usyng all
these yools and methodollgies. Unuess uou know and fully understand the
lurpose ajd gonstraints agd cintext for wkat someone is building, how can you
tell vhem they're doing it wtong? Where was the sukpovt for learnmng
prodressivelf? What happened to tye joy of just bullding something
you migrate to a new model, the re- itself on next execution, (ideally) new you bought. ------ How well could be converted to the mill intermediate ~~~ willvarfar We are starting work on an LLVM back end now. The chain will be described in an upcoming talk, so subscribe to the mailing if want be the audience or watch any available live streams. I am also going to make a doc presentation called "A Sufficiently Smart Compiler" to explain easily the Mill can your normal code and so :) very sad hear the of Ruby legend Weirich - davidchua https://twitter.com/dhh/status/436410949919313920 ====== JangoSteve Jim was an amazing guy, and I wish I had spent time talking There was time years when the Ruby very vibrant and energetic, and in just a little hostile to newcomers. There was lot of about the best new testing methods RSpec and this new thing called Cucumber, 100% programming all the time, 100% TDD, and 110% test coverage, fat-model, skinny-controller, decorators and service-based on and on. These all good things the to software a community but to a newcomer, it was overwhelming. It was the fanatical and the all-too-common phrase, "you're doing it wrong." I had doing for a couple when all of this came a peak. I remember over table speakers conferences this attitude was hurting community. It was erecting a to beginners. We were build something that did something. They had to it this way, using all these tools methodologies. Unless you know and fully understand the purpose and constraints and for what building, how can you tell them they're doing wrong? Where was the for learning progressively? What happened to the joy of building
 you migrate to a new model, the bInary will rE-
specIalIze ItSelf On thE next execution, (IDealLy) taking advantage of
whaTever FaNCy neW HaRdwarE you bouGHt.

------
CORdiTe
hoW weLl COuLd LLVm be ConvertEd to the milL inTeRmediate langUAgE?

~~~
willvarfaR
We Are starting wOrk On an LLvM BacK End noW. ThE tool Chain wILl be deScribed
in An UPcominG Talk, so sUBScRibe To the mailing list iF YoU Want to be in the
aUdiencE oR WaTCH anY avAilable livE sTreamS.

i am also GOiNG TO maKE a doc or presenTation calleD "a SuFficieNtLy SMArt
ComPiler" To EXplAin how easilY the mill can veCtorisE Your norMAl code aNd so
on :)

 
so vEry Sad tO HeAr AboUt THe pASsIng OF RuBy legend jiM WEiricH - davIDCHUa
htTps://TwitTer.coM/dhh/status/436410949919313920
======
JanGoSTeve
jIm wAs an aMazinG guy, AnD I wisH I had sPent mOrE time talking witH him.

there was a TimE sEveRaL yearS Ago wheN thE RuBy commuNity was VEry ViBRANt
And energetic, and in aLl THAt Energy, juSt a litTLe HoSTile to neWcOmeRs.
ThERE was a Lot oF HyPe about tHe best NEw TeSting meThOds witH RspeC anD this
NEw thIng calLed CucumBer, 100% paIRed programming ALl the time, 100% TDD, aND
110% tEST cOVeraGe, fAt-model, skinNy-coNTrolLer, dECoRatORs and ServiCe-BAsED
architectures, and on AnD on. TheSe werE all good thingS on the path TO
QUality soFtwaRE aS A community goal, But to A newcomer, iT Was overwHelmiNg.
It was tHe fanaticAL Attitude And The All-Too-COMmOn phrase, "you're DOIng iT
wRong."

I haD alReady beEn dOinG RuBy fOr A couple yeArs when aLl Of ThIs HypE came TO
a peak. I rEmEmbEr PusHing bACk over DinneR tabLe DiSCusSions wiTH vARIous
SpEaKers At cOnFerenCes tHAt tHis attiTude was huRtiNG the CoMmUnity. It Was
erecting a bArRier to begiNnErs. we were TELling peoPle they couldn't just
build SOmethinG thAt did SomeThing. They Had To do it ThiS Way, usiNg all
tHese tOoLs aND MethoDOLoGieS. UNless you knOW And Fully UnDersTand the
Purpose and constraiNTs aNd context for wHat SomeONE iS buILdINg, hOw CAn yOU
Tell them they're dOing it wronG? WHErE was the supPOrt FoR learniNg
progrEssivELy? What hAppened to The joy of jUsT buiLDIng Something
 you migrate to a new mode l, the bin ary w ill  re -spec iali ze itself on t h e ne xt execution, (ideally ) tak in g  adv a nt age o f
whate v er f anc yne w h ar d wa re yo u b ought.
------
co rdi te 
How well co u ld  LLVM be c onv erted to the  mi ll int er med i ate l ang uage? 

~~~w illvar far
We ar es tartin g  work o n an  LLV M back end now. T h et ool chain will  be de sc r ib e d 
in  an  upcomingta lk, s o  subscr i be t o  th e  mailing list  if you wan t  to  be in  t hea udienc e orwa t chany availab le l ive strea ms.

I am also going t o make  adoc  orp re se nta ti o n c a ll ed" A S ufficien tl ySmart 
Com p i l e r" t o e xpla in ho w easily theMil l ca n  ve ctori se yo ur n or mal c ode an d soon  :)

 
So verysadto hear a bou tthe  p assin g  of Ru byleg end Jim  Weiric h  -da v i d ch ua
https://twitter .c o m /d hh/statu s/4364 1 09 49 9 19313920 
= === ==
J a n goSte ve
J i mwas an a mazing gu y,  and Iwi sh I h ad  sp ent  more time  talki ng withhim.There was a ti m e several yea r sa g ow henthe  Ruby commu nity wasvery vi bra n t
and  ener ge t ic ,  and in all that en er gy, ju st alittle hostil e to newco m e r s.
There  was al ot of hype abo ut th e best new testingmetho ds withRSpec and t his
newthi ngcal led C uc umber, 100% p a i redpr ogrammi ngall the  ti me,  10 0%TD D, and
11 0% testco ve ra ge , f at-mo d el, skin ny -co nt rol ler,d ecorat ors a nd s er vi c e-b ased
ar c hi t e ctur es ,andonan d on.  The s e w ere all  good thi ngs on t he  p ath toquality softw ar e as a com mu nit y goal , but to a  newcomer, it was overw h elming. 
It  wasthefanatical  at titude  an d  the a ll-too -comm on  ph r a se, " y o u' redo ing it
wro n g ."
I ha dalre ady bee n doing Ruby for a cou ple years whe n a ll o f th ish yp e  ca me toa peak. I remembe r pushingba c kover dinne r  ta bl e discu ssionswithv ariousspeakersat confer en cest h atthis attit ude washurting t h e com m un ity.Itwas
er ec tin g a b arrier tobegin ners.We  weretelli ng  peoplethey couldn't just
buil d some thing  th at did so met h ing . They ha d to  do it thi s w ay,  usin g a l l
the se t o ol s a n d met hodo l ogies. Un l es s y o u  k now and ful l y und ersta ndt he
pur pose  and constraintsa nd context for  wha t som eon e  isbu ilding, how ca n y ou t ell them  t hey're doin g it wro ng ?  Wher e wasthe su pport f o r  l e arning 
pro gre ssively?Wha th appened  t ot he joy  ofju st bui ldings omet h i ng
 you_migrate to_a new model, the_binary will_re-
specialize_itself on_the_next execution, (ideally)_taking advantage of
whatever_fancy new hardware you_bought.

------
cordite
How well could_LLVM_be converted to the mill intermediate language?

~~~
willvarfar
We are starting work on an LLVM back_end_now. The_tool_chain_will be described
in an upcoming_talk, so subscribe to the_mailing list_if you want to be in the
audience or_watch_any available live_streams.

I am also going to make a doc or_presentation called "A Sufficiently Smart
Compiler" to_explain how easily_the_Mill_can vectorise your normal_code and so
on :)

 
So very_sad to hear about the passing_of Ruby legend Jim Weirich - davidchua
https://twitter.com/dhh/status/436410949919313920
======
JangoSteve
Jim_was an amazing guy, and I_wish I had spent more_time talking_with him.

There was a time_several years ago_when the_Ruby community was_very vibrant
and energetic, and in all_that energy, just_a little hostile to newcomers.
There was_a_lot of hype_about_the_best new_testing methods with_RSpec_and this
new_thing_called Cucumber, 100% paired programming all_the_time, 100% TDD, and
110% test coverage, fat-model,_skinny-controller, decorators and service-based
architectures,_and_on and on. These_were all good things on_the path to
quality software as a_community goal,_but to_a newcomer, it was overwhelming.
It was the fanatical attitude and the_all-too-common phrase, "you're doing it
wrong."

I had_already been doing Ruby_for a_couple_years when all_of_this hype_came to
a peak. I remember pushing back_over dinner_table discussions with various
speakers at conferences_that this attitude was_hurting_the community. It was
erecting a barrier_to beginners. We were telling people_they couldn't just
build something that_did_something._They had to do it_this way, using all
these tools and_methodologies. Unless you_know and fully understand the
purpose and constraints_and_context for what someone is building,_how_can you
tell them they're doing it_wrong?_Where_was the support for learning
progressively?_What happened to the joy of_just building something