Juraj Kirchheim

I don't understand. 1. The syntax in general has nothing to do with any library whatsoever. It is just an alternative syntax for calls with a single argument. 2. Using...

I think this kind of complicates things and is not quite what I have proposed. Both of these are prefix functions: ``` foo.and(bar) foo and bar ``` The latter is...

> IMHO, -D nodejs should be up to the user, and for instance using either XMLHttpRequest, require('http') or why not fetch should be feature-detected at runtime. That's not a bad...

> We could have something like that, with minimal overhead for browsers (pseudocode, obviously) : > > ``` > static var reqImpl = (require && require('haxe-http-impl')) || fetch || XMLHttpRequest;...

> I mean, ultimately, I should remove the dependency from js-kit to js-kit-browser to avoid -D nodejs propagation, and this forbids me from reusing anything from one project to the...

Indeed it will. But why would one ever do that in a front end project to start with? One would just use `js-kit-browser`, thus the flag is not set and...

> > (I've seen @back2dos do crazy things with haxelib + macros, some of which should definitely be released somehow). > > @back2dos Juraj, we summon you! Could you share...

The tink libraries will also require an update. Is there a way to dump the data? Then I can try locally ;)

Oh, totally forgot about that ... :D Hmm, so this means an unhandled `proxy.makePostCall()` gets optimized away? I'm not 100% we want that, but if we do, we should document...

Mhh, I think with recent coconut.data it might be enough to make sure all fields in the remote are `final`, right?