portkey

Portkey: from REPL to Serverless in one call
viesti 2017-09-12T04:23:05.000059Z

whoa, looks nice :)

viesti 2017-09-12T04:23:56.000054Z

also a potential missing check found

cgrand 2017-09-12T04:57:08.000060Z

Well it's very close to amazonica

richiardiandrea 2017-09-12T05:27:58.000062Z

Oh cool that's awesome, I should really try to allot some time for a cljs port

richiardiandrea 2017-09-12T05:50:59.000051Z

So this portkey should really be a nice way to deploy AWS lamdbas, even JS ones...do I understand correctly that for now only JVM lamdbas can be deployed?

cgrand 2017-09-12T06:26:34.000005Z

@richiardiandrea for js, js engines are lacking features. Namely one: the ability to inspect a closure closed-overs.

cgrand 2017-09-12T06:58:46.000324Z

@richiardiandrea to make things clear: aws-clj-sdk can be ported to CLJS without majoir concern. portkey on the other hand requires introspective features that JS is lacking (and I haven’t found them in v8/JsCore documentation neither — I’d love to be proved wrong)

cgrand 2017-09-12T07:01:11.000109Z

However it may be possible to create a meta-circular JS interpreter that add these features. This interpreter would run only in the developer repl, Lambda would get plain JS

1
viesti 2017-09-12T07:11:56.000255Z

didn’t find :meta-circular: emoji so settled for a wizard hat

cgrand 2017-09-12T07:48:36.000102Z

Currently aws-clj-sdk functions take 0 or 1 arg. If I assume that 2+ args are keyword args then aws-clj-sdk could almost be a drop-in replacement for amazonica