These are chat archives for opal/opal

8th
Sep 2016
Jamie Gaskins
@jgaskins
Sep 08 2016 00:00
@fkchang I think @Mogztter does. He's been doing a lot of the Node-compatibility work, iirc.
Guillaume Grossetie
@Mogztter
Sep 08 2016 06:00
Indeed, I'm using Opal with Node a lot!
Jamie Gaskins
@jgaskins
Sep 08 2016 15:53
@Mogztter Are you doing anything with AWS Lambda? It'd be cool to be able to run Ruby processes there. :-)
Guillaume Grossetie
@Mogztter
Sep 08 2016 16:19
No I've never tried but it could be fun, do you have a specific use case ?
Jamie Gaskins
@jgaskins
Sep 08 2016 16:22
Not yet. Was just wondering if anyone had tried it. :-)
I've never used Lambda at all, tbh, but it's gotten a lot of press.
So I just like to try out JS things that are hyped to see if I can write Ruby with them. I've almost finished a ServiceWorker wrapper that'll make its way into bowser.
Forrest Chang
@fkchang
Sep 08 2016 17:22
@Mogztter I'd like to hear what sorts of things you are doing, also trying to figure out what the "best practices" are since opal-node says "just compile and run w/node", are you using npm packages from opal?
@jgaskins look forward to the ServiceWorker wrapper, I was thinking of making one myself, but if u've already done it...
I would imagine the lambda approach is the same as the node one, compile to JS and do it there. I believe we tried it as an experiment here, but went w/something else to solve the problem we had lambda as a candidate for
Jamie Gaskins
@jgaskins
Sep 08 2016 20:11

@fkchang I'll let you know when it's merged in. I just got it working with all of the MDN ServiceWorker examples last night. It's got some funky restrictions, though, like it's incompatible with the Opal Promise class, so I had to write my own there — the good news is that I could proxy the native one since a native Promise implementation is a pre-req for ServiceWorker anyway.

A few other weird things about it, too. I'll document them once it's in.