Re: UTF16 Surrogate Pairs in Fressian not encoded to utf8 correctly

2019-11-07 Thread Kyle Wilt
mostly utf-8 except it preserves invalid > utf-16" than "this is utf-8". I wonder if other fressian implementations > handle this the same way? Javascript also shares java's utf-16 string type > but not every platform does. > > > On Thursday, November 7, 201

UTF16 Surrogate Pairs in Fressian not encoded to utf8 correctly

2019-11-07 Thread Kyle Wilt
I posted an issue about this to the datomic/fressian github page but I don't know if anyone is monitoring it anymore. https://github.com/Datomic/fressian/issues/7 I'm trying to find out if this is intentional for some reason or a bug. Right now it encodes UTF16 surrogate pairs as two 3 byte val

Re: Thoughts on resource oriented computing (ROC)

2019-06-04 Thread Kyle Wilt
multi-tenant capable > and should have been rewritten to keep up with the evolution of Clojure. > You should check with 1060 Research directly to find out what the current > status of the module is. > regards, >-t > > > On Monday, June 3, 2019 at 9:48:14 AM U

Thoughts on resource oriented computing (ROC)

2019-06-03 Thread Kyle Wilt
I have been a "secret admirer" of clojure and the clojure approach to problem solving for quite some time now even though I'm not really a direct practitioner. I do try to convert my C# code into as "clojure like" a model as reasonably possible given all of my constraints. I have been a big fan