Clojurians
#lumo
<
2017-05-27
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

anmonteiro01:05:25

a little bit raw, but looking for feedback on this: https://github.com/anmonteiro/lumo/pull/169

souenzzo16:05:36

A bit off for this channel, but what is the current state of clojurescript+prepack?

anmonteiro17:05:00

@souenzzo I have a Lumo branch working with Prepack but didn't see much difference

anmonteiro17:05:22

Some bending was required to make it work, so definitely an advanced topic

souenzzo17:05:05

But you think that in the (sort) future it will be usable out of the box, as closure?

souenzzo17:05:51

(sort ~= when it get mature/npm users start to use it)

anmonteiro17:05:13

can’t predict the future :slightly_smiling_face:

anmonteiro17:05:29

I’m sure there’s a tremendous amount of engineering work behind Prepack

anmonteiro17:05:34

so eventually it will be usable

dominicm20:05:17

it's weird to say "browser" :stuck_out_tongue:

dominicm20:05:36

because I know it's a docker image

dominicm20:05:45

do you disable fs stuff?

anmonteiro21:05:44

@dominicm that was just my first very rough experimentation

anmonteiro21:05:02

I didn’t disable anything in that one

john21:05:54

@anmonteiro how hard do you think it would be to actually port lumo to the browser? Converting the fs stuff to localstorage, etc.

john21:05:16

I'm interested in seeing a full compilation and dev environment in the browser

anmonteiro21:05:35

@john I don’t know how hard it would be, but I’m also not planning on finding out

anmonteiro21:05:45

Lumo is very tied to Node.js and always will be