***Guest8084 is now known as Cork
<lloda>how can I tell emacs that #2() or generally #...() is a single s-expr for C-M-SPC purposes ***Raimondii is now known as Raimondi
***Raimondii is now known as Raimondi
<dustyweb>civodul: I did see it... in fact I had started writing up a similar plan to Pyramid before it was announced called "Smarm" <dustyweb>civodul: basically the idea was to take Rees' w7 scheme and restrict it in space/time deterministically <dustyweb>civodul: I dunno if you've read up on the attacks on Etherium contracts <dustyweb>they never would have happened in an ocap environment <cmaloney>Please let me know: which Earth am I on? I thought I was on M1 but I'm starting to wonder <civodul>dustyweb: yeah i remember you were looking into smart contracts in Scheme <cmaloney>dustyweb: I just read through that article and now I'm even more afraid of our future. <cmaloney>I mean, JavaScript-based global virtual machine currency? <cmaloney>It's like someone said "name three things that keep security folks up at night" and they rattled off "JavaScript, trusted computing on other folks machines, and monetary-incentivised attacks". <rain1>haha i love the way tyou described thaht cmaloney <dustyweb>cmaloney: well, depending on how javascript is done <dustyweb>there's a branch of javascript that *is* ocap-safe <dustyweb>and Mark Miller's new startup is going to do smart contracts with a restricted, ocap-secure version of js <dustyweb>if there's anyone I trust to do things secure ***fibratio` is now known as fibration
<cmaloney>dustyweb: Right. But is that version of JavaScript going to be merged back into ECMAScript <cmaloney>or is everyone else going to have to learn that lesson the hard way? :) <amz3>OrangeShark: I got an idea what do with my neon project <amz3>OrangeShark: Actually, I will reboot the idea that get me started <amz3>That is sharing datasets <amz3>and talked of the idea to un ex-colleague and he is excited by the idea, he did not reply about my idea to build Scheme company tho <daviid>fibration: (reading the log ...) what did you want to ask wrt guile-cv? <manumanumanu>So, I ported the common lisp once-only macro to scheme for use with define-macro. <manumanumanu>the once-only is a 3 levels deep looping construct, whereas it can be implemented as a single define-syntax-rules macro