ec changed the topic of #elliottcable to: a 𝕯𝖊𝖓 𝖔𝖋 𝕯𝖊𝖙𝖊𝖗𝖒𝖎𝖓𝖊𝖉 𝕯𝖆𝖒𝖘𝖊𝖑𝖘 slash s͔̞u͕͙p͙͓e̜̺r̼̦i̼̜o̖̬r̙̙ c̝͉ụ̧͘ḷ̡͙ţ͓̀ || #ELLIOTTCABLE is not about ELLIOTTCABLE
muelleme has joined #elliottcable
muelleme has quit [Ping timeout: 244 seconds]
scrptktty has quit [Quit: Connection closed for inactivity]
Rurik has joined #elliottcable
Rurik has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Rurik has joined #elliottcable
Rurik has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
<ELLIOTTCABLE>
guthariest
<ELLIOTTCABLE>
incomprehensibly!
<ELLIOTTCABLE>
you opened IRC wtf
<ELLIOTTCABLE>
guys incomprehensibly is getting married I'm so proud
<ELLIOTTCABLE>
oops might have not been my news to share MY BAD NOT SORRY AHHHH
<ELLIOTTCABLE>
i'm so pissed about BuckleScript's choices re: ML submodules
<ELLIOTTCABLE>
and by “pissed” I more mean “completely flabbergasted and puzzled”
<ELLIOTTCABLE>
basically it compiles the ML equivalent of “SubModule { function foo(){ … } }” in the file Module.ml,
<ELLIOTTCABLE>
instead of into basically Module.SubModule.foo(),
<ELLIOTTCABLE>
Module.SubModule is a fucking *array* (!?) of functions
<ELLIOTTCABLE>
on the JavaScript side
<ELLIOTTCABLE>
so I'm having to maintain an extra JavaScript ‘entry-point’ file in my project that publishes the API in a sane way; while breaking down every. single. module. in my project into individual files
<ELLIOTTCABLE>
which is gunna break down HARD when I start trying to use any neat module-language features. functors, GADTs, or whatever.
<ELLIOTTCABLE>
pissssssed
<ELLIOTTCABLE>
Alsi
<ELLIOTTCABLE>
idk, but one of you might enjoy reading my giant explanation of Why JS People™, to a bunch of crotchety OCamleers