Fork me on GitHub
#hoplon
<
2016-06-05
>
lewix17:06:50

micha: you mentioned vue.js to me once, why?

lewix17:06:59

I was looking at it - not bad at all

micha17:06:16

i think you said you had been working with js things

micha17:06:32

vue.js seems to be the most similar thing to javelin in that world

micha17:06:25

you can actually use javelin in js just fine, too

micha17:06:50

the macros are only syntax sugar, all the work is done by regular functions underneath

micha17:06:37

> At the very least, using splint probably won't make what you have any worse.

lewix17:06:03

did hoplon came out before react?

micha17:06:15

before it was released yes

micha17:06:38

or at least before we knew of it

micha17:06:52

we've been using hoplon since late 2012 i believe

lewix17:06:07

why not just use rxjs?

lewix17:06:16

instead of javelin

micha17:06:18

we didn't want frp

lewix17:06:38

"frp in clojurescript with javelin"

micha17:06:49

yea hthat was a bad choice of words

micha17:06:01

frp is really a bigger thing

micha17:06:19

and everyone was like "that's not frp because it doesn't have this feature" and whatnot

micha17:06:38

we didn't think that any of those features were helpful for making UIs

micha17:06:53

so "dataflow" is a more amenable name i think

micha17:06:19

it doesn't make people think of classical FRP or any of the haskell stuff

micha17:06:50

rxjs doesn't do what javelin does

micha17:06:43

for one thing FRP has both event streams and "behaviors"

micha17:06:56

so there is a ton of stuff to try to make event streams useful

micha17:06:18

basically reimplementing tons of things like map, filter, etc

micha17:06:27

but in a weird way

micha17:06:36

javelin doesn't have event streams at all

micha17:06:43

just behaviors

micha17:06:11

by eliminating event streams the model becomes both simpler and more powerful, because you don't need to have all kinds of special cases

micha17:06:21

so you get better cohesion and composition

micha17:06:52

also all the js things are crippled by javascript's lack of value equality

micha17:06:07

one does not simply test if two things are equal in js

micha17:06:00

this is the main issue with the thing we first used, flapjax

micha17:06:34

that's what forced us to make javelin rather than modify flapjax

lewix17:06:18

i' m thinking about using plain react.js interop and rxjs interop

micha17:06:46

plenty of stackoverflow things to google with that, so that's good