<dsmith>I'll be in Boston (well, "Woburn" wherever that is) the 17-19 <dsmith>Would be cool to meet some Guilers in the area <wingo>tx for the early discussion re: glyph's article too <wingo>the specific case that glyph discusses is even more egregious in a concurrent ml system, as all channel sends are synchronous, and thus a channel-based logging facility would be synchronous too <wingo>a system with preemption & multi-threading can only work if there is good software culture, whether enforced or simply encouraged by the language <wingo>python's software culture is good too of course :) <wingo>but i mean that programmers in a preemptive environment should be verrrrry wary about unstructured mutation <wingo>maybe reagents can help improve that case <wleslie>that's sort of why Armin had originally tried to go with STM, aiming to reduce the cognitive difference that preemption brings to existing single-address-space systems <wleslie>but yes, if you don't have mutation all over the place, there are better options ***vlad___ is now known as ivladak-work
***ivladak-work is now known as vlad___
***ivladak-work is now known as newnickname
***newnickname is now known as ivladak-work
***ivladak-work is now known as ivladak_
***ivladak_ is now known as ivladak-work
<wingo>ecraven: how is the benchmarking going? :) <ecraven>wingo: hehe, well, finished a few days ago, and I totally forgot about them! <rekado>ugh, a blogger who is well-known in Germany wrote about the recent Guile security fix. Apparently without understanding the issue. <wingo>they think perhaps that all guile programs are vulnerable, that would be my guess? <wingo>i admit i had that impression a bit from the initial announcement <rekado>yes, as if all Guile processes by default listen on localhost for code to execute <rekado>the quote is: "The default in Guile has been to expose a port over localhost to which code may be passed. The assumption for this is that only a local user may write to localhost, so it should be safe." <rekado>that sounds very misleading in isolation <wingo>yeah. it's a funny thing, you want to explain the fix, you want users to be secure, but you don't want to overstate the issue; and perhaps this time we overstated the issue i guess <janneke>'Guile? Never heard of that, what a funny name! Better have a look.' ;-) <wingo>i understand it's a funnier name in german <void-pointer>Wait, it's a funnier name in German? I guess I need to learn a lot more German then <janneke>guess the possible diphthong gets the german language area confused <profan>ACTION still voting fo renaming Guile to Geil <rekado>I pronounce it like the German “geil” (~ horny) <rekado>(same pronunciation as “guy ell”) <rekado>void-pointer: yes, I’m living in Berlin now. <void-pointer>I'm living in Göttingen, though at this moment I am out of the country. <wingo>well the comments appear to be good anyway <wingo>what is happening to the world <janneke>sanity and tolerance, that will be the end of us <janneke>tinkering with syntax-case and implementation of quasisyntax/unsyntax <paroneayea>I hope people can take it less as "Guile is making this mistake" than "oh man, like nearly all software makes this mistaken assumption / implementation issue" <davexunit>interesting how the HN comments are of higher quality than the LWN comments ***karswell` is now known as karswell
<dsmith>civodul: Any idea when it went away? <OrangeShark>there was a lot of net splits and stuff that day too <amz3>catonano: I saw your message on guix help <amz3>catonano: I think there is no hard requirement on guile-next, otherwise said, you can use guile <amz3>I mean I don't remember using anything particular to 2.2 <catonano>slower than 2.2 ? My dataset is very small now, I won't notice <l_zzie>Hi! I can start a repl server with --listen=something. How do I connect a client to it? <l_zzie>or rather -- what program do I use as a client? <jmd`>What does the starred version of define-record-type do?? <jmd`>(yes I have read the manual) <jmd`>Isn't that a bit unethical of them? <amz3>there is a lot of define-record-type* around <random-nick>some people think that a lot of the guix utility functions for different things should be moved to guile proper or at least separated into a library <l_zzie>oh, found the manual. nc / telnet works. <amz3>l_zzie: you can use geiser <janneke>it seems than unsyntax works quit differently than unquote <paroneayea>l_zzie: hi! you probably want to use emacs + guile + geiser <paroneayea>l_zzie: I also recommend doing --listen=/tmp/guile-socket and using "M-x geiser-connect-local" to connect to it. See the most recent release for details. <OrangeShark>hey paroneayea, what is your workflow for live hacking a web service? Did you do that with pubstrate? <paroneayea>OrangeShark: I did do it for pubstrate. It depends on if you're using one of the new async systems or just the built in http system. <paroneayea>OrangeShark: there's a quick-and-dirty-solution, which is what I've used for pubstrate so far, because I haven't moved it over to a nicer async solution yet <paroneayea>OrangeShark: "spawn-server"; see 6.17.12 "REPL Servers" <janneke>either eval comes too soon: eval: unbound variable: exp <janneke>or much too soon: eval: unbound variable: process-rule <janneke>...or too late: syntax-error:urg2 input=:((sc:when #t (display HELLO-SC-WHEN) hello-sc-when)) <stis>darn folding a weak hash table is allocating memory <janneke>unsyntax recurses deep to remove all (syntax ...) wrappers? <stis>Im inside gc hooks and want to fold over a weak key hash table, currently that blocks <stis>the reason seams to be that the folder takes a gc lock that is already held <stis>The solution is to have a separate folder for use in gc hooks <stis>The situation is sad because maintaining a set of objects for advanced gc algorithms needs something like a weak key hash table ***Fuuzetsu_ is now known as Fuuzetsu
***_hanhart_ is now known as _hanhart
<taylan>janneke: unsyntax doesn't do anything; it's just a "token" scanned for by quasisyntax. <taylan>janneke: and all it does is that the unsyntax'd form is evaluated normally rather than as literal syntax. this means that e.g. further (syntax ...) forms within it will just become syntax. if you know how quasiquote works; it's exactly like that. <taylan><janneke> it seems than unsyntax works quit differently than unquote <taylan>that shouldn't be the case, unless I'm very confused right now <taylan>janneke: to get a feeling for syntax/quasisyntax/unsyntax, use them outside the context of macros/syntax-case. you'll note you can use them exactly like quote/quasiquote/unquote, just constructing syntax objects rather than raw sexprs. <amz3>I have brillant idea, but I'm too sick to code :( ***masoudd is now known as LjL_
***LjL_ is now known as masoudd