freenode/#sicl - IRC Chatlog
Search
17:14:07
alandipert
i've never done this live, but i did it once when i practiced a talk and it might have helped
17:14:43
alandipert
the other thing is to keep in mind that you can edit audio, so you don't need very long takes necessarily
17:15:11
alandipert
the only thing there is if you change recording location the audio will sound noticeably different which could distract people
17:16:55
heisig
No, it was about a HPC framework that I plan to use for Petalisp. I presented it to my colleagues.
17:18:32
heisig
Next week will be most interesting. The next semester starts on Monday, and we are supposed to read our lectures to 200+ students via Zoom.
17:19:51
alandipert
i'm part of a 200+ person zoom call every quarter, usually goes ok. with everyone using zoom tho now.. i agree it seems dicey
17:20:56
MichaelRaskin
They are very much pushing towards «maybe lecture part should be prerecorded and posted» of course (and they are right…)
17:25:06
heisig
Yes, but I'd like to hear from a Nix user that is not just afraid of the parentheses.
17:25:47
MichaelRaskin
There is that observation that some stuff is better covered in Nix, and not by me.
17:26:48
MichaelRaskin
And then Guix is more puristic re: licensing. I guess even my TPTP expression would not be allowed.
17:27:15
heisig
Incidentally, the HPC framework that I presented (StarPU) lists Guix as the recommended way to install it.
17:29:25
alandipert
i'm out, by all, good luck heisig on your lecture. be sure to mute everyone first thing :)
17:32:56
MichaelRaskin
heisig: but re: Guix, I guess there is that thing that I was perfectly comfortable with both Nix and Bash by the time Ludovic decided to build Guix
17:34:38
MichaelRaskin
heisig: about convincing solutions for conversations and moderation, I guess there is also the question of support for unmoderated and dynamically occuring small voice chats
19:28:45
Bike
i did a quick survey. on clasp, discriminating functions for about 28 of all 1089 defined generic functions (or 577 generic functions that have ever been called) could be improved by reduction
21:02:22
Bike
i put in something that counts how often generic function outcomes are reached. kind of interesting. for a start I can see that cleavir-ir:inputs has been called over twenty five million times
21:04:31
Bike
looking through random cleavir functions, it seems reasonably common for there to be one outcome that's almost always used, and then a few that are rarer
21:04:48
Bike
for example, cleavir-ir:inputs has twenty five million calls using that one outcome, and then a few hundred thousand using the other
21:05:07
Bike
(there are different outcomes because slots are ordered differently so they have different instance locations... wondering if it's possible to fix that...)
3:35:59
Bike
if done properly, counting the branch selection for each argument, you could optimize the dispatch a bit. check the most common stamps first and all