freenode/#lisp - IRC Chatlog
Search
14:56:31
beach
p_l: I don't see why. You could always erase part of it when you start up, pretending that there is volatile memory.
14:56:35
p_l
OTOH, I professionally deal with things like "the machine is gone - how I can ensure continuity"
14:57:53
beach
montaropdf: It means that there is no distinction between the stuff you can do with RAM and the stuff you can do with a disk. It all behaves as if you had random access memory that is persistent as the disk is.
14:58:24
beach
montaropdf: Multics had that 50 years ago, and Unix made many generations of developers forget about it.
14:59:59
beach
p_l: You mean that "the growing divide between speeds of different storages" also had it 50 years ago?
15:01:01
montaropdf
However, the week-end passes by, so I had time to think about it and to test some cases. I am currently thinking more and more about getting away from my, traditional, table approach to store data, to using sexp trees. I am also targeting small volumes of data, nothing the NSA would be bothered to search in ;)
15:01:11
Nilby
Thankfully true universal persistence is there without any effort, now to control it nicely though you need a redesign from processors & L1 cache to offsite backups.
15:02:15
p_l
beach: I see it often enough in how it impacts code that deals with just CPU - the multiple levels of caches, how much latency there is. Also how swap became much bigger impact compared to how it used to be, as the difference in speeds between disk storage and memory gone like crazy, not just the latency
15:33:08
Nilby
In the old days when I went to open a file, sometimes it would text the "operator" to load a tape. If the operator was me, the system would deadlock.
18:00:55
pjb
Then, databases have to deal with KEYS to identify external objects and internalize. For symbols, the key is the package name and the symbol name. But for random CLOS objects, it's more complicated: the programmer must specify the keys… Even for cons cells, or lists, you start to have problems…
21:31:29
akhetopnu
Hello. Has anyone tried using clack + TLS? I don't see any info in the docs clack's docs about it
21:32:57
akhetopnu
is the assumed setup reverse proxy tunneling requests/websocket connections to clack and clack just serving everything without encryption?
21:41:42
akhetopnu
I'm tinkering with clack + hunchentoot right now and I know hunchentoot supports SSL (not sure if they mean literally SSL or maybe TLS too), it's just that I'm not sure if clack can pass through the TLS certificate paths for example
21:42:33
akhetopnu
I would like to get encryption all the way from the browser to my server, however if that's not possible then I guess I'll have to settle down for a reverse proxy
21:46:24
Shinmera
often the reverse proxy is on the same machine as your lisp instance, so it doesn't matter.
21:49:44
akhetopnu
i'm trying to setup a (mainly) websocket server (+ http(s) wouldnt hurt to be honest) and clack + hunchentoot seems to be the most 'reliable' way
21:51:39
Shinmera
you can setup nginx to do the https websocket handshake and then delegate to your non-https websocket server.
21:54:10
Shinmera
The above is how I offer https://shirakumo.github.io/lichat-js/?hostname=chat.tymoon.eu
22:07:43
lottaquestions
Hi all, a few days ago I had issues with running the code from Practical Common Lisp on SBCL. The following link shows some code changes that the author of the book made in order to get the sources to work on a "modern" SBCL: https://github.com/gigamonkey/pcl-practicals/commit/99b6f516bcb764f070eaa45b834f1e6c83742a09
22:08:41
lottaquestions
In my case there were some issues reading from a stream, which appear to be fixed in the git commit in the link I provided above
0:16:36
no-defun-allowed
I don't really know what I'm asking, but how can I change the order in which arguments are used to compute the method list for a generic function?
0:17:47
no-defun-allowed
If I have a method with lambda list ((x a) y) and another with (x (y b)), I would want the latter to be used first, but the default appears to use the former first.