Fork me on GitHub
#funcool
<
2016-11-22
>
leppert01:11:21

FYI I started working on a CLJS port of some of the Buddy components, entitled “Pal”: https://github.com/leppert/pal-core https://github.com/leppert/pal-hashers At the moment it’s not entirely useful (though much of the hashers functionality is there) but the hope is that it might one day be robust enough to provide syntactic familiarity between Clojure Buddy projects and Node Pal projects.

niwinz08:11:48

it is nodejs target or any js environment?

niwinz08:11:49

I have started in the past something with nodejs target https://github.com/funcool/dost

niwinz08:11:29

but I did't had enough time for it

niwinz08:11:39

After read a little bit the code, now I have the answer: yes seems like it target to nodejs

niwinz08:11:27

in this case I think that some code from funcool/dost can serve you

niwinz08:11:45

@leppert Will be welcome if I port some changes from dost to pal? I think that nodejs native hashes and hmac supports is better than the google closure library, just because they are native implementation. Also I have support for nodejs streams in dost that is useful for hash big files without blocking too much.

niwinz08:11:56

On the other hand, js and jvm environments are pretty different, so I don't recommend try to have the exact api with buddy

niwinz08:11:32

many things can be similar or equal but many other can't be and I don't recommend force to have a similar api.

leppert11:11:47

@niwinz any help would be greatly appreciated. In terms of targeting node vs all js environments, I'd love for it to be generally portable so I'll put that in as a future goal, but node is my current use case and, as you said, node offers some specific speed and convenience that we couldn't get with browser restrictions.

leppert12:11:34

With regards to keeping the APIs the same, I think you summed it up well. I'm going to shoot for them to be as close as possible but won't sacrifice sanity or usability at the expense of perfection.

niwinz12:11:25

I have an other question...

niwinz12:11:46

any chance to not use EPL as license?

leppert12:11:08

I'm open to other licenses. What are you thinking?

niwinz12:11:40

apache2 if you are ok with permisiviness or MPL2.0 that is similar to EPL but better compatibility with gpl

niwinz12:11:48

In any case, this is not big issue, I'm just not a big fan of EPL

niwinz12:11:24

I'll try open a PR porting many stuff from dost to pal-core

leppert12:11:50

@niwinz: I'm okay with it being as permissive as possible. Apache2 works for me; I'll add a commit with new licenses later this morning.

leppert12:11:17

Not a problem!