<Shinmera>
The next stretch goal is official mod support, which I think would be quite exciting for people here in specific :)
SR-71 has quit [Ping timeout: 244 seconds]
seok- has joined #commonlisp
<seok->
there's so many json libraries
<seok->
which one does everyone use?
<Shinmera>
all of them
<seok->
what
<seok->
why
<Shinmera>
by virtue of you asking about everyone
<Shinmera>
well, someone made it, so someone uses it.
<seok->
well, which one do you use shinmera
<Shinmera>
I've used jsown before and shasht. There's a new one I'd like to use but it's still not on ql, so I cannot.
<seok->
I've used yason before and kinda stuck with it
<seok->
What's prompting you to move around?
<Shinmera>
not remembering which one I used last
<Josh_2>
I still tend toward jonathan for parsing and shasht for exporting
<Shinmera>
Jonathan made my image memfault when I tried it once and that's enough for me to stay away forever.
<Josh_2>
Yes a potential problem with all the speed 3 safety 0 declarations. I have my images locked at safety 3
<Josh_2>
I should swap to shasht, it is much nicer than Jonathan
<Shinmera>
And jonathan doesn't even win in the benchmarks for all that lack of safety.
<Shinmera>
Talk about a waste!
<seok->
well time to try shasht
azimut_ has quit [Remote host closed the connection]
azimut has joined #commonlisp
Th30n has quit [Quit: WeeChat 3.5]
<yitzi>
If you need help with shasht let me know. Author here.
<seok->
oh.. it's not on ql.. time to download it manually
<seok->
Cheers yitzi
<Nilby>
the fist time i had to switch json libraries, i fixed my code to allow swapping them. but i've never had stop using one of Shinmera's libraries :)
<Josh_2>
Nilby: I have started doing the same
<Shinmera>
seok-: it is on ql.
<seok->
(ql:quickload :shasht)? it's not found
<Shinmera>
update your ql then
<Cymew>
seok-: How about the name? Doesn't make you think about json exactly.
<Cymew>
Oops. Wrong nick.
<Cymew>
yitzi: How about the name? Doesn't make you think about json exactly.
<seok->
yeah, +1 on adding the etymology to the readme
<seok->
ok, it is on ql
<jackdaniel>
and accelerated it did
<seok->
I was thinking the same thing just didnt mention it
<yitzi>
I think that names like cl-json are silly. I like unique and easy to find names. A hint to the etymology is in the description "Common Lisp JSON reading and writing for the Kzinti."
* jackdaniel
wonders whether cl-foo name conventions is still obsolete, or has it moved to classic/retro stage already ;)
<yitzi>
Specifically, I used pretty much all of the JSON libraries in my Jupyter work and found them all deficient. Usually in encoding escape sequences, etc.
rodicm has joined #commonlisp
<semz>
Same. Ended up writing my own, considered publishing it, but decided against it in the end because good god there are enough already
<semz>
although this was before shasht, and the latter looks interesting. hm.
<Cymew>
yitzi: Thanks.
<Nilby>
Have I forgotten again, or is there really still no fast way to convert between integer and bit-array?
<Nilby>
or simple-bit-vector specificly
cage has joined #commonlisp
<Bike>
no standard function for it.
<Nilby>
Sigh. I was hoping the situation had improved since H.Baker c.1989
<Nilby>
Is there a non standard way?
<Nilby>
The code in sbcl i'm looking at seems to define bit vector operation on single bits :( but I haven't look at the compiler yet
<Josh_2>
jackdaniel: I just give my libraries cool names :sunglasses:
<Nilby>
It looks like the sbcl compiler does have a few things
random-nick has quit [Ping timeout: 244 seconds]
<Nilby>
e.g. I can (sb-kernel:%vector-raw-bits #*101010 0)
shka has quit [Ping timeout: 276 seconds]
aartaka has quit [Ping timeout: 240 seconds]
aartaka has joined #commonlisp
random-nick has joined #commonlisp
nij- has left #commonlisp [Using Circe, the loveliest of all IRC clients]
lagash has quit [Ping timeout: 240 seconds]
shka has joined #commonlisp
Glaucon has joined #commonlisp
akoana has quit [Quit: leaving]
lagash has joined #commonlisp
cosimone has quit [Remote host closed the connection]
tyson2 has quit [Remote host closed the connection]
cosimone has joined #commonlisp
ttree has joined #commonlisp
Lord_Nightmare has quit [Excess Flood]
Lord_Nightmare has joined #commonlisp
Lord_Nightmare has quit [Excess Flood]
Lord_Nightmare has joined #commonlisp
treflip has joined #commonlisp
lisp123 has joined #commonlisp
lisp123 has quit [Ping timeout: 255 seconds]
mon_aaraj has joined #commonlisp
pieguy128 has quit [Ping timeout: 264 seconds]
attila_lendvai_ has joined #commonlisp
pieguy128 has joined #commonlisp
<Shinmera>
Nilby: (read-from-string (format NIL "#*~b" 101)) is very fast to type at least ;)
<Nilby>
Shinmera: And one library even does it close to that way. Thank you, but I've already hacked something quick enough with sbcl internals. Now I have to figure it out on any other implementation. Sigh.
tyson2 has joined #commonlisp
<Shinmera>
what are you doing that conversion speed actually matters?
<Nilby>
trying to find a faster algorithm for generating random Gaussian distributions
<Nilby>
with a quantum computer
<Nilby>
er, without i mean
<Nilby>
i probably shouldn't even use bit vectors, but it makes it easier in some ways
<Shinmera>
I'm trying to think of situations where having a bit vector would make things faster, rather than just having an integer and using ldb etc.
<Bike>
the bit vector operations have a non consing mode
<Nilby>
Bike: yes, that's one reason. random 2d access seems easier too. i imagine i might go back to the the ldb way if need be
<Nilby>
with bignums it's hard to be sure when it conses
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #commonlisp
attila_lendvai_ has quit [Ping timeout: 276 seconds]
<Nilby>
I would wish that the number and array would end up being equivalent speed, and one could just choose the most convenient representation, but I guess i'll have to see
<pjb>
Nilby: there's almost no difference between number and bit-vector access times: https://termbin.com/wmxs
<Nilby>
pjb: Thanks. That looks pretty fast. That is very similar in structure to what I did with %*vector-raw-bits. Perhaps I can do that for other implementations.
<pjb>
Only, integer are immutable. This is what may let you choose bit-vector over integer.
<Nilby>
Yes, my code is very mutating, which is one reason why I chose the vector way to begin with
<pjb>
And, if you have very big vectors, you can also use multithreads to process separate parts.
<pjb>
in parallel.
<pjb>
It depends on your threading overhead.
<Nilby>
yes, most of the problems i'm working on have natural parallelism, so it can be split that way
yauhsien has joined #commonlisp
tyson2 has quit [Remote host closed the connection]
yauhsien has quit [Ping timeout: 276 seconds]
mon_aaraj has quit [Ping timeout: 240 seconds]
dudek has joined #commonlisp
mjoerg has joined #commonlisp
jeosol has quit [Quit: Client closed]
mjoerg has quit [Remote host closed the connection]