{"id":155,"date":"2012-04-17T16:07:00","date_gmt":"2012-04-17T15:07:00","guid":{"rendered":"http:\/\/www.celesteh.com\/blog\/2012\/04\/17\/liveblogging-sc-symposium-future-of\/"},"modified":"2015-06-19T00:23:18","modified_gmt":"2015-06-18T23:23:18","slug":"liveblogging-sc-symposium-future-of","status":"publish","type":"post","link":"https:\/\/www.celesteh.com\/blog\/2012\/04\/17\/liveblogging-sc-symposium-future-of\/","title":{"rendered":"Liveblogging the SC symposium: the Future of supercollider panel discussion"},"content":{"rendered":"<h2>\nJames McCartney <\/h2>\n<p>James McCartney has some ideas about the future &#8211; compose music by composing functions (aka functional programming)&nbsp; Lazy lists of infinitely long lists.<\/p>\n<p>stack based, postfix language like forth (based on Joy). function composition is concatenation.&nbsp; Pipelining is a natural idiom for music.&nbsp; control flow is left ot right (easier than LISP). No delimiters.<\/p>\n<p>There are a very few data types &#8211; reals, strings, lists, forms (protype objects that are immutable), functions, refs (which are mutable)<\/p>\n<p>everything else is immutable. bind a veraible once, it stays forever. this is concurrency friendly. you can share without worrying about state.<\/p>\n<p>double precision 96kHz, single sample rate<\/p>\n<p>this language does not have looping because you can iterate over nested structures<\/p>\n<p>this language is not all that easy to read&#8230;. (everything goes backwards)<\/p>\n<p>well, it will be great for tweeting&#8230;<\/p>\n<h2>\nTim Blechman<\/h2>\n<p>He&#8217;s working on a new IDE.&nbsp;<\/p>\n<p>This looks alarmingly like emacs.<\/p>\n<p>The language runs as a subprocess, so it can crash without killing the editor.<\/p>\n<p>the post window moves around in an interesting way. The editor is very basic for now.<\/p>\n<p>The language is not currently integrated, but i guess this is coming.<\/p>\n<p>Projects might be supported. A project would contain many Sc files and have properties. Classes could be specifically for certain projects. This would be very nifty.<\/p>\n<h2>\nThe Overtone Guy<\/h2>\n<p>He likes having the language and the server seperate (obviously, because his project relies on it). All sc-based languages need to have stuff about the UGens in it (ie metadata).&nbsp; He&#8217;s going to propose metadata for Sc in general for ugens, which could be an ok idea.<\/p>\n<p>He also wants an OSC validation program between himself and the server. This is a terrible idea for sclang. Who is going to write this thing?<\/p>\n<p>He thinks diversity should be encouraged but also sharing so as to avoid work duplication.<\/p>\n<h2>\nDiscussion<\/h2>\n<p>Client \/ server division is kind of cool, says Dan.&nbsp;<br \/>\nJames says the thing he just demoed is much smaller than SC.<br \/>\nTim wants to know if it would get bigger if people started using it.<\/p>\n<p>Can we do sample calculations in sc? sure with James&#8217;s sc4.<\/p>\n<p>&#8230;language design theory&#8230;.<\/p>\n<p>I<\/p>\n","protected":false},"excerpt":{"rendered":"<p>James McCartney James McCartney has some ideas about the future &#8211; compose music by composing functions (aka functional programming)&nbsp; Lazy lists of infinitely long lists. stack based, postfix language like forth (based on Joy). function composition is concatenation.&nbsp; Pipelining is a natural idiom for music.&nbsp; control flow is left ot right (easier than LISP). No &hellip; <a href=\"https:\/\/www.celesteh.com\/blog\/2012\/04\/17\/liveblogging-sc-symposium-future-of\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Liveblogging the SC symposium: the Future of supercollider panel discussion<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-155","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/posts\/155","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/comments?post=155"}],"version-history":[{"count":1,"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/posts\/155\/revisions"}],"predecessor-version":[{"id":2354,"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/posts\/155\/revisions\/2354"}],"wp:attachment":[{"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/media?parent=155"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/categories?post=155"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.celesteh.com\/blog\/wp-json\/wp\/v2\/tags?post=155"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}