Fork me on GitHub
#aatree
<
2016-02-25
>
laforge4914:02:34

ah, major course correction.

laforge4914:02:23

I was looking into having a database on both clojure and clojurescript, but I am putting that aside indefinitely.

laforge4914:02:51

One thing that led to this decision was bitset. Found a js bitset which is an array. Found a clojure bitset which is a set. Both immutable. Neither works with byte arrays. So it looks like developing a common api for bitset with bytebuffer support would be a project all by itself.

laforge4914:02:16

Conclusion: this is not yet the time, at least for me.

laforge4915:02:48

Now what I should do instead is work on gui for laforge49/aatree. Enhance existing value. Seems like a good focus for me for now.

laforge4915:02:46

Hmm. Thinking of just copying most of laforge49/aatree to aatree/aadurable, but make aadurable boot based.

laforge4915:02:01

need to think about it.

laforge4922:02:36

Having second thoughts. I think I can do without bit strings except for the 256-bit checksum, which could be done without any library.

laforge4922:02:09

Having a 256-bit checksum in cljc is worth doing. simple_smile

laforge4922:02:43

And I'm sure I'll learn a bit about clojurescript in the process.