IRC channel logs

***masoudd_ is now known as masoudd

<paroneayea>hey, FSF microblogged the guile devroom :)

<paroneayea>Honestly, that's why I'm just not really interested in that part of the software stack. I'm more interested in the software that runs on top of base Android, augmenting the user experience. Basically the level that Google apps run at. Focusing on that will do a lot to get us to a state where we can actually compete in the market with Google. Because right now the options are either "live without a billion nice features" or "install

<paroneayea>Google apps and give up all the things that make freedom-respecting software useful."

<paroneayea>oops

<paroneayea>wow

<paroneayea> https://microca.st/fsf/note/c4segCjlSZOR9Y8V8xcBvQ is what I meant to paste

<paroneayea>the other thing was part of someone's blogpost about android.

<paroneayea>sorry!

<atheia>Ah accidental blogposts! It's why I stopped using IRC in Emacs.

<atheia>Way too easy to post in the wrong buffer :-/

<atheia>Ugh, and when I wrote blogposts I meant pastes. That's a weird thing to mix up.

<civodul>it's great that the FSF talks about Guile :-)

<holomorph>ACTION wonders what the other 14 letters are in e14n

<paroneayea>holomorph: "evaaaaaaaaaaaaan" ;)

<paroneayea>(not my original joke)

<paroneayea>I think it's meant to look like it spells "evan" if you see the logo

<alezost>I hope not "exclusive nation"

<paroneayea>I don't know hat "exclusive nation" would mean, but I guess it doesn't sound like a term you'd use to describe a federated system

<paroneayea>wingo: did you ever look at http://community.schemewiki.org/kali-scheme/ ?

<paroneayea>distributed scheme by Jonathan Rees and Richard Kelsey

<paroneayea> https://github.com/rotty/kali-scheme

<paroneayea>maybe some good ideas to mine

<amz3>fsf is interested by guile, weird

<davexunit>amz3: I used to work there and got everyone hooked on it, of course ;)

<OrangeShark>guile will take over the world :)

<amz3>^^

<paroneayea>fsf is the gnu steward...!

<wingo>good evening :)

<paroneayea>heya wingo

<paroneayea>wingo: did you ever look at Kali scheme? seems pretty interesting

<wingo>paroneayea: i just checked that link

<wingo>i have not looked :)

<wingo>does seem interesting

<paroneayea> https://github.com/rotty/kali-scheme/tree/master/doc docs here

<wingo>i suspect that a distributed system should build on a concurrent system

<wingo>(and that a distributed system is a harder problem!)

<wingo>i also want to understand what lasp is

<wingo> https://lasp-lang.org/

<paroneayea>cool wingo

<wingo>i don't know whether replicating erlang is really where we need to be; but i don't know much :)

<OrangeShark>amz3: the other day I committed some stuff for guile-git. I have added finalizers to the repository pointers and it should be something we apply to the rest of the types.

<OrangeShark>Also `make check` now runs your tests :)

<amz3>OrangeShark: thx

<OrangeShark>amz3: I was wondering if we should somehow just roll the finalizers into the pointer->type wrappers when defining new types

<OrangeShark>so it would be (define-libgit2-type type finalizer-for-type)

<wingo>so

<wingo>why do we have cancel-thread.

<wingo>or rather

<wingo>why does it use pthread_cancel().

<wingo>it should just queue an asynchronous interrupt on that thread and throw a guile exception (or prompt abort) from the interrupt

<wingo>no?

<wingo>pthread_cancel seems exceedingly dangerous

<civodul>i agree