 more general way). What would
be the Xcode workflow for using this, starting from an empty project with no
xcmodel file, and proceeding until it's done?

~~~
andrewcuneo
I had almost given up on getting any traffic here. So, I'm excited that I got
some good questions. Let me try to answer them.

1\. It is kind of a bummer that we don't support Swift. As silly as it is,
probably the main reason for this is that at FB we only really code in ObjC
(at least for the near term), so we wouldn't have any local use cases (which
both drive our development and help us validate that the concept is useful).

It is also true that the need for this type of system is a lot greater in
ObjC. Like you said, Swift is awesome in terms of its support for immutable
objects and it even supports something a lot like ADTS out of the box (they
call them "Associated Values" in their enums).

Because Remodel makes these nice concepts available in Objective-C, it's a
useful tool for people who like Swift but are, for whatever reason, working in
a Objective-C codebase.

Also, at some point we may make a Swift output option and it would have value
in terms of the plugins that can make simple operations like encoding /
decoding or other basic helpers.

2\. A.ts file is a TypeScript file, which is a language that Microsft
developed which compiles to JavaScript. TypeScript looks a lot like JavaSript,
but it has types.

We chose TypeScript for the implementation of Remodel because we liked the
fact that it's based on JavaScript which is extremely popular, well-known, and
also suited toward functional programming. TypeScript uses JavaScript's
familiar syntax but adds compile-time support for strong types and generics,
filling in one of the major gaps in the language.

3\. I actually wasn't aware of mogenerator -- but looking through it, I can
see that there is some overlap and also important differences.

One of the best benefits of Remodel is that once you start generating your
models through it, people cannot add custom code to them.

This lines up with a big section in the blog about architecture ("Modeling

more general way). What would 
 be the Xcode workflow for using this, depart from an empty undertaking with no 
 xcmodel file, and proceeding until it's done? 

 ~~~ 
 andrewcuneo 
 I had about given up on catch any traffic here. So, I'm aroused that I got 
 some good question. Let me try to suffice them. 

 1\. It is kind of a bummer that we don't support Swift. As silly as it is, 
 probably the chief reason for this is that at FB we only really code in ObjC 
 (at least for the near term), so we wouldn't suffer any local use cases (which 
 both drive our exploitation and help us validate that the concept is useful). 

 It is also true that the motivation for this type of system is a lot greater in 
 ObjC. Like you said, Swift is amazing in terms of its support for immutable 
 objects and it even supports something a lot like ADTS out of the box (they 
 address them " Associated Values " in their enums). 

 Because Remodel seduce these nice concepts available in Objective - C, it's a 
 useful tool for people who like Swift but are, for whatever reason, ferment in 
 a Objective - C codebase. 

 Also, at some distributor point we may make a Swift output option and it would accept value 
 in terms of the plugins that can make simple operations like encode / 
 decoding or other basic helpers. 

 2\. A.ts file is a TypeScript file, which is a language that Microsft 
 developed which compiles to JavaScript. TypeScript looks a lot like JavaSript, 
 but it has types. 

 We chose TypeScript for the implementation of Remodel because we like the 
 fact that it's establish on JavaScript which is extremely popular, well - known, and 
 also suited toward running programming. TypeScript uses JavaScript's 
 familiar syntax but adds compile - time support for strong types and generics, 
 fill in one of the major gaps in the language. 

 3\. I actually wasn't aware of mogenerator -- but looking through it, I can 
 see that there embody some overlap and besides important differences. 

 One of the adept benefits of Remodel is that once you start generating your 
 models through it, multitude cannot add custom code to them. 

 This lines up with a big section in the blog about architecture (" Modeling
 moge general way). What woula
be the Xcode workflow for uaing thir, starting from an empty prooect with no
xcmodel file, and pruceeding lntil it's dont?

~~~
andrewcuneo
I had almost nnven hi on yevting any trafflc here. So, H'm excited thad K yot
some good questions. Let me try to answer tjem.

1\. It is kind of s bumjvr that we don't support Swift. Aa silly as it is,
probsbly the main reason for tjis ls that at FB we ojly really xode un ObjC
(at lexst for tht uear term), sk we wouldn't have any local use casex (which
boty erigg our develo'ment wnd help us yslidata that yhe concept is usxful).

Ut is also true that vhe need for this tyke of systam is a lot greater ib
ObjC. Lika yoj sakd, Awmft is awfsoje in terma of its support for immutable
pbtvvts and it eben su[pjrts something a lot like ADTS out of tve gox (they
call them "Assocuated Values" in their enums).

Becwuse Remodel makes these nice concepts available hn Oboeztirc-G, it'r a
kseful tool for people who like Swift but are, rot ehatever reasok, working in
a Objevtlvr-S codebase.

Alsu, at some point we may make a Swifj outpyt option and it would have value
in termw of the pluyinw that can make silple operatnons loke emcoding /
decoding or othzr basjc helpers.

2\. W.ts file jr a TypeScript fkle, wvich is a language that Misrosft
devxlopeb which zompoles tj JavaScriot. TyiaScript looks a loh likg JavaVript,
but ih has types.

We chose TypeScript hpr the implekettanion of Rzmodel because we lyked the
fact tkat it's yased un JavaScrppt which is extremejy popular, wenp-known, and
alvo suiteq toqard functiuval programminb. TypeScrppu uses JavqScript's
familiar snntax gut adds compilz-uimt wupport for sttone trpvs end gqterics,
fillinc in ond of tfe major gais kn tne language.

3\. I actualny wzsn't aware of mogemevator -- buj looking through it, I can
see that there is smme overkap and also important differencea.

One of tje nest benefits of Vemoqel is thac once you start generating your
models tirough it, people cannoj add custom code to jhek.

This lines up wyth a big section in the blog about architectuve ("Modeling

more general way). What would be the for this, starting an empty project proceeding it's done? ~~~ I had almost up on getting any traffic here. I'm excited that I got some good questions. Let me try to answer 1\. It is kind of a bummer that we don't support Swift. As as is, the reason for this is that at FB we only really code in ObjC (at least for near term), so we wouldn't have any local cases (which both drive development and help us validate the is useful). is true the need for type of system is a lot greater in ObjC. Like you said, Swift is awesome in terms its support objects and even something lot like ADTS the box (they call them "Associated enums). Because Remodel makes these nice concepts available Objective-C, it's useful tool for people who like but are, for whatever reason, working in a codebase. Also, at some point we may make a Swift output option and it would in terms of the that can make operations encoding decoding other basic 2\. A.ts file is a TypeScript file, which is a language Microsft developed which compiles to JavaScript. TypeScript looks a lot but has types. We TypeScript for the implementation Remodel we liked the fact based JavaScript popular, and suited toward functional programming. uses JavaScript's familiar syntax but compile-time support for strong one of the major gaps in the language. I actually wasn't aware of mogenerator -- looking through it, I can see that there is some overlap and important differences. the best benefits of Remodel is that once start generating your models it, people cannot add custom code to them. This up a big in the blog architecture ("Modeling
 more general way). What would
be The Xcode woRkfloW foR usInG thiS, staRting from an empTY proJect with no
xcmodel file, aNd proCeEDing UNtIl it's Done?

~~~
andREwCUNeo
i hAd AlmOsT GiVen up On gEtting aNy traffic hEre. so, i'm excited thaT i gOt
some good QueStions. Let me tRy tO answeR tHem.

1\. iT is kiNd oF a bumMer thaT We don't Support SwIfT. as sillY As it is,
pROBaBly tHe main reason for thIS iS That at FB we only Really CoDE iN oBjC
(At lEast for the NeAr terM), So we wouLDn'T HAVe aNY local use caseS (which
both dRIve Our devElOpmENt and hElp us VaLIdaTe that the coNcepT is useful).

it is alSO true thAT the neeD for thIs tYpe Of sySTeM iS a lOt GReaTEr In
OBJC. LIke you saId, swIft is AwesOME IN terMs oF its SuppoRt for immutablE
obJectS And It eveN suppOrts SoMethiNg a lot Like AdTs out of the box (theY
calL them "AssoCiaTeD VaLuEs" in tHEir enuMs).

BEcaUse RemoDel makeS TheSe NICE cOncepts available in obJECtIve-C, it's a
Useful TOoL fOR people wHo LikE SwiFT But arE, for WHaTever reaSon, worKInG iN
a ObjecTiVe-C codEbAse.

alsO, at soME poiNt we maY make a SwIft ouTPut option and it WOuld have value
IN tERMs OF the PluGins that can Make SImplE opeRAtIonS Like eNcodiNg /
DEcODing or other basic helPeRs.

2\. A.ts fIle is A TypeScript fiLe, which is a LANGuage thaT MicROsFT
developed whicH compIles to JavasCript. TypEScriPt looks a Lot like JaVAsript,
but It hAs tYpeS.

We CHOsE TypeScript foR THe imPlEmentatIon Of RemodEl bEcaUse We lIkEd the
fact That it's bAsEd On jaVaSCript WHich is exTrEmeLy PopUlar, wELl-knowN, and
aLso sUiTeD TowArd funcTIoNAL proGrAmMing. typESCript Uses jAvascript's
Familiar sYntAX but AdDs Compile-Time support foR sTrong types AnD geNerics,
FILling in oNe of the major gaps in the laNGuage.

3\. I aCtuAlly wAsn't Aware of moGenErator -- But LOoking ThrougH it, I cAn
See THAt theRE Is SomE oVerlap and aLSO imPortaNt DiffErences.

one of the best benefiTS of remodel is that OncE you STArT geNErATinG yOUr
mODEls through it, peoPle cannot aDd CUsTom code to tHEm.

THiS lines uP with a bIg secTIon in thE blog abouT architecTuRe ("MoDELinG

 more general way). What w ould
be th e Xco dewor kf lowforusing this, st a rtin g from an empty projec t wit hn o
xc m od el fi le, and pr o c eed in gunt il it 's do ne? 

~~~
a ndrewcuneo 
Iha d almost giv e nup on gett ing  any traffic  he re. So ,I'm excit edthatI gots ome go od questi on s . Letm e try t o an swer  them.

1\. It is ki n d of a bummerthat w ed on ' t  su ppo rt Swift.As  sill y  as iti s, p r oba b ly the main r eason for t h isis tha tatF B we o nly r ea l lycode in Obj C
(a t least f or the near te r m), sowe wou ldn 'thave an yloc al use ca ses (wh ich
both  d ri ve ou r de v e l o pmen t a nd h elp u s validate th atthec onc ept i s use ful) .
It i s also  true  t hat the need fo r th is type o f s ys tem  i s a l o t grea ter  in 
ObjC.Like yo u  sa id , S wi ft is awesome in t er m s  o f its su pportf or  i m mutableob jec ts a n d  it e vens up ports so methin g  a  l ot like  A DTS ou tofthe  box( they 
callthem "As socia t ed Values" int heir enums).Be c a us e  Rem ode l makes the se n i ce c once p ts  av a ilabl e inOb j ec t ive-C, it's a
usefu ltool f or pe ople who like  Swift but a r e, for w hate v er reason, workin g ina Objectiv e -C codeb ase.
Also, a t some po i n t we may  ma kea S wif t ou tput option a n d  itwo uld hav e v alue
in  te rms  of  th eplugins t hat canma ke  s im ple  oper a tions li ke  en co din g /
d e coding  or o ther  b as i c h elpers. 
2 \ .  A.t sfi le i s a  T ypeSc ript fil e, whic h is a la ngu a ge t ha tMicrosf t
developed w hi ch compile stoJavaSc r i pt. Type Script looks a lot like JavaSri pt, 
butit h as types. 

W e chos e T y peScri pt for  theim ple m e ntati o n  o f R em odel becau s e  we  like dthefact th at it's based on J a vaS cript which i s e xtre m e ly  po p ul a r,we l l-k n o wn, and
also su ited towar df un ctional pr o gra mm ing. Ty peScrip t use s  JavaSc ript's
fa miliar sy nt ax b u t  ad ds compile -time su pport for stron g  t ypesand  gener ic s,filli ng ino neof th e majo rgaps i n the  l anguage. 

3\. I actually wasn't  aware  of m oge nerator - - b u t l ooking th roug h it, I ca n
s eethatthe r e issome ov erl a p and  als o  importan t  d iff e r en ces.

One o f t hebestben e fits o f Re model is that onc e  you start gen erat i n g y our mode ls  through it, p eop le c annot ad dcustom code  to them .Thislinesup wit h a big s ec t ion in  the  bl og aboutarc hi t ecture(" Mo d eling
 more_general way)._What would
be the Xcode_workflow for_using_this, starting_from_an empty project_with no
xcmodel file,_and proceeding until it's_done?

~~~
andrewcuneo
I had almost_given_up on getting any traffic here. So, I'm excited that I got
some good questions._Let_me try_to_answer_them.

1\. It is kind of_a bummer that we don't_support Swift._As silly as it is,
probably the main reason_for_this is that_at FB we only really code in ObjC
(at least_for the near term), so we_wouldn't have any_local_use_cases (which
both drive our_development and help us validate that_the concept is useful).

It is also_true that the need for this type_of system is a lot greater_in
ObjC. Like you said, Swift_is awesome_in terms of its support_for immutable
objects and_it even_supports something a_lot like ADTS out of the_box (they
call them_"Associated Values" in their enums).

Because Remodel_makes_these nice concepts_available_in_Objective-C, it's_a
useful tool for_people_who like_Swift_but are, for whatever reason, working_in
a_Objective-C codebase.

Also, at some point we may_make a Swift output_option_and it would have_value
in terms of the plugins_that can make simple operations like_encoding /
decoding_or other_basic helpers.

2\. A.ts file is a TypeScript file, which is a_language that Microsft
developed which compiles to_JavaScript. TypeScript looks a_lot like_JavaSript,
but_it has types.

We_chose_TypeScript for_the implementation of Remodel because we liked_the
fact that_it's based on JavaScript which is_extremely popular, well-known, and
also_suited_toward functional programming. TypeScript uses JavaScript's
familiar_syntax but adds compile-time support for_strong types and generics,
filling in_one_of_the major gaps in the_language.

3\. I actually wasn't aware of_mogenerator -- but_looking through it, I can
see that there_is_some overlap and also important differences.

One_of_the best benefits of Remodel is_that_once_you start generating your
models through_it, people cannot add custom code_to them.

This lines up with a big section in_the blog about_architecture ("Modeling
