ec changed the topic of #elliottcable to: a π―ππ ππ π―πππππππππ π―ππππππ slash sΝΜuΝΝpΝΝeΜΜΊrΜΌΜ¦iΜΌΜoΜΜ¬rΜΜ cΜΝα»₯Μ§ΝαΈ·Μ‘ΝΕ£ΝΜ || #ELLIOTTCABLE is not about ELLIOTTCABLE
irclogger_com has quit [K-Lined]
irclogger_com has joined #elliottcable
_whitelogger has joined #elliottcable
prophile has quit [Quit: The Game]
meowrobot has quit [Quit: let us connect our intestines and mutually digest]
prophile has joined #elliottcable
meowrobot has joined #elliottcable
_whitelogger has joined #elliottcable
_whitelogger has joined #elliottcable
cloudhead has joined #elliottcable
cloudhead has quit [Ping timeout: 240 seconds]
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
trolling has joined #elliottcable
prophile has quit [Read error: Connection reset by peer]
trolling has quit [Read error: Connection reset by peer]
prophile has joined #elliottcable
_whitelogger has joined #elliottcable
<incomprehensibly>
ec: lmao at OSA objects
cloudhead has joined #elliottcable
prophile has quit [Quit: The Game]
<ec>
< ljharb> ec: yes, you can't do any of node's network stuff in the browser
<ec>
< ljharb> ec: so for jxa, you won't be able to bundle up anything that's network or filesystem-related
<ec>
and I figured part of it out; I was using `--bare`, which somehow neglected the shims or something? idk?
<ec>
now currently struggling with the supposed βsynchronous-onlyβ nature of JXA
<ec>
which is totally bullshit lol, there's no such thing as something that *can* only be synchronous
<ec>
at least in a language with first-class functions, anyway
<ec>
so I'm building a shim for setInterval and friends using the NSRunLoop of the `osascript`'s JSC thread ... somebody else has already done some of the work, and I'm doing a bunch of research on the Foundation run loop systems
<ec>
I v. doubt I'll be able to achieve spec-compliance, but I betcha i can get request/request working at least????