Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

2024 Participants: Hannah Ackermans * Sara Alsherif * Leonardo Aranda * Brian Arechiga * Jonathan Armoza * Stephanie E. August * Martin Bartelmus * Patsy Baudoin * Liat Berdugo * David Berry * Jason Boyd * Kevin Brock * Evan Buswell * Claire Carroll * John Cayley * Slavica Ceperkovic * Edmond Chang * Sarah Ciston * Lyr Colin * Daniel Cox * Christina Cuneo * Orla Delaney * Pierre Depaz * Ranjodh Singh Dhaliwal * Koundinya Dhulipalla * Samuel DiBella * Craig Dietrich * Quinn Dombrowski * Kevin Driscoll * Lai-Tze Fan * Max Feinstein * Meredith Finkelstein * Leonardo Flores * Cyril Focht * Gwen Foo * Federica Frabetti * Jordan Freitas * Erika FülöP * Sam Goree * Gulsen Guler * Anthony Hay * SHAWNÉ MICHAELAIN HOLLOWAY * Brendan Howell * Minh Hua * Amira Jarmakani * Dennis Jerz * Joey Jones * Ted Kafala * Titaÿna Kauffmann-Will * Darius Kazemi * andrea kim * Joey King * Ryan Leach * cynthia li * Judy Malloy * Zachary Mann * Marian Mazzone * Chris McGuinness * Yasemin Melek * Pablo Miranda Carranza * Jarah Moesch * Matt Nish-Lapidus * Yoehan Oh * Steven Oscherwitz * Stefano Penge * Marta Pérez-Campos * Jan-Christian Petersen * gripp prime * Rita Raley * Nicholas Raphael * Arpita Rathod * Amit Ray * Thorsten Ries * Abby Rinaldi * Mark Sample * Valérie Schafer * Carly Schnitzler * Arthur Schwarz * Lyle Skains * Rory Solomon * Winnie Soon * Harlin/Hayley Steele * Marylyn Tan * Daniel Temkin * Murielle Sandra Tiako Djomatchoua * Anna Tito * Introna Tommie * Fereshteh Toosi * Paige Treebridge * Lee Tusman * Joris J.van Zundert * Annette Vee * Dan Verständig * Yohanna Waliya * Shu Wan * Peggy WEIL * Jacque Wernimont * Katherine Yang * Zach Whalen * Elea Zhong * TengChao Zhou
CCSWG 2024 is coordinated by Lyr Colin (USC), Andrea Kim (USC), Elea Zhong (USC), Zachary Mann (USC), Jeremy Douglass (UCSB), and Mark C. Marino (USC) . Sponsored by the Humanities and Critical Code Studies Lab (USC), and the Digital Arts and Humanities Commons (UCSB).

jang

Sure. I'll sort that later today.

About

Username
jang
Joined
Visits
443
Last Active
Roles
Member
Invited by
Zach_Mann

Comments

  • Incidentally, I was wondering whether the choice of { and } was to mimic the many langauges with C in their glyphic ancestry - and/or because there's a lack of, say, a 〈 and 〉 pair on US keyboards. I'm reminded of Stoustrup [1994, The Design a…
  • I'm not much of a poet, but Rules {which are made to be broken
  • I should add: demystifying what's going on shouldn't be seen as taking anything away from the achievement here*. The use of metaprogramming to convert a more maintainable codebase into the final artistic artifact is in itself a pretty cute trick. …
  • The "every line diff" is largely an artifact of rescaling the program. (Eg, cf. the first line and start of second in the "before" with the longer first line in the "after".) The other thing that's going on here is that the program's authored in …
  • There's a fundamental trick to quines which is to produce the entire program text as an output; typically, that requires reconstructing the whole program text as a string (including any code that constructs that string, plus the output of the string…
  • @markcmarino Second things first: yes, as far as I can tell, all the []sshould be ()s. In terms of the parsing: I'm referring to the explicit clause location by separation on ,, . and but. This seems to be to be aimed directly at making eliza/…
  • What if corporate technology were forced to build its systems on “affinity machines”? Can you explain what you mean by this? In terms of affinities: the point of k8s is to capture the essentials of a system architecture (at a particular l…
  • @blankenshipa there's definitely an analogous behaviour! But I suspect the same can be said for most crafts, be they physical (eg, building a house) or purely intellectual/mathematical. Square pegs can be forced into round holes is almost allwalks o…
  • @yaxu it might be a matter of moments to change a branch name, but in many cases there's a lot more to it than that. The name change has to be percolated across build and deployment infrastructure; the assumption might be baked into many scripts. If…
  • @anthony_hay - what's your take on the ., , and but processing? That seems to be something that could've just been introduced as an initial preprocessing rule in the DOCTOR suite. It's not clear if Weisenbaum started the implementation in one fas…
  • As for the mad-slip code: it permits keyword phrases to be abbreviated, so TRANSFER TO can be written T'O. Function names are disambiguated from variable names by appending a .. There's support for pre-ascii input mechanisms: .G. is a transcri…
  • Some of those are patterns used by YMATCH. (0 YOUR 0) matches a sequence of any length, followed by "YOUR", followed by a sequence of any length. The responses that follow (the square brackets look like an ocr error btw) are template expansion, that…
  • So I have a question about this. I'd assumed that "deploy" came from the French word meaning to unfold or to spread out, and that if anything the direction of semantic travel would have been from a general notion of laying out or spreading out, t…
  • or "deployments" (as corporate teams say, using a military term with a casualness I find horrifying) That's a startling observation! I've been exposed to this term for most of my working life. If you'd asked me, I probably would've guessed t…
  • or "deployments" (as corporate teams say, using a military term with a casualness I find horrifying) That's a startling observation! I've been exposed to this term for most of my working life. If you'd asked me, I probably would've guessed t…
  • On cleverness versus "cleverness", the baroque and the downright rococo: topically, there has recently been (another) call to "write boring Haskell" (a quick search here will provide arguments both for and against) - as a reaction against some of th…
  • The quote, "cat came back from Berkeley waving flags" was attributed to Rob Pike (around the inception of Plan 9, I believe, but I can't find an original source for this at the moment). There was a similar piece of folk wisdom that every piece of…
  • (It doesn't;see the first para of the man page.)
  • I wonder what the types / genres of software are where this would be possible -- where there exists such a detailed description of the intended output that someone can carefully audit the output just to see if it matches that description. A …
  • The article itself was fantastic - a very nice write-up of various attempts to improve the algorithm given the constraints of the machines of the day. This may be of interest, by way of contrast. I've thrown a gist together that uses two approach…
  • @joeyjones and @jang Can you speak to this point? I'm assuming you meant the point following, about keeping source closed. Schneier has a short entry here that addresses this counter-intuitive position. It also links to three longer essay…
  • Keeping the code closed doesn't prevent hacking; it does, however, put those wanting to legitimately verify it on a potentially sticky legal wicket. A potentially worse problem is the host of conspiracy theories that a closed app will engender - …
  • Just as a note - one subtle distinction between the p9 version and the GNU one is this: if(write(1, buf, n)!=n) sysfatal("write error copying %s: %r", s); ... which jumps out as being pleasantly surprising. Under POSIXy…
  • If I can add one personal comment about my own reaction to this: Occasionally, one comes across a particularly striking piece of code. It's especially stark when this happens with something like C. As such a low-level language, it's typical to ex…
  • I'd like to start with this: Finally, what does the (terse, short variable names, uncommented) code style of Plan 9's cat tell you about the values of its creators? Every line here seems to be written with the assumption that its meaning will …
  • @KalilaShapiro: Why should that decide someone's alignment so heavily? That's an interesting question, and in truth probably reflects the reality of this situation. The alternative question might be, "why should someone's alignment cau…
  • There is also the category "gross hack," where one feature is misused because it'll have a desired side-effect. These kinds of things have quite the attraction for bright, inquisitive and inventive minds: plus, solving a puzzle by lateral thinking g…
  • I think the English names for common objects stem from later ISO standardisation efforts to unify glyph names. As a kid (I got hold of Iverson's APL report through an inter-library loan) the only names I knew for these were the original ones that…
  • There's a similar issue with var dickinsonFlatLessLess = dickinsonLessLess[0]; dickinsonFlatLessLess.concat(dickinsonLessLess[1], dickinsonLessLess[2]); which explains the misbehaviour of riseAndGoLine. However, the following comments: // …
  • @ebuswell - in terms of this: Is it an advantage to know the English "if" or is it maybe an advantage to have "if" presented without the nontechnical baggage of everyday English? you might want to look at the for/else here or while/els…
  • Could you speak a little about the implementation? For starters, the implementation language; and whether its own glyphic limitations have an impact on your code? Are you writing your Cree# implementation in a language derived from European traditio…
  • (On the question of Python's random.shuffle:) You'll find it here There's a quick mention of its rationale here. Something like this ought to suffice also: // Approach 1, modified slightly function anagram(text) { var a = t…
  • HACK-HACK looks like a common routine (although implementations vary across games). There's a description in one of the infocom memoires (which I can't currently find, alas) of the way that a new game would be started: the source for something re…
  • One of the ideas we try to introduce to programmers is that all code should be written with human readers in mind - it's seldom the case that anything is written once and never looked at again. It's a vital skill to communicate effectively; the desi…
  • No apology needed! I'm interested in this from a pedagogical stance. One of the things students do is mimic various behaviours as they try to approximate "elegance" - the development of an aesthetic response is part of learning the craft. At the sam…
  • I'm really rather taken with "Flight of the Code Monkeys". However, the reason I'm posting is to ask a specific question about the (at time of writing, current) annotation on "Taroko Gorge". Specifically, "elegance" is mentioned twice. Clearly…
  • C. How should CCS handle implied, misleading or ironic code? How does other criticism handle it? (This is a genuine question, not a rhetorical one.) A. What examples of implied, misleading or ironic code have you come across in your ow…
  • It's a cheeky way to take the integer part of a number. Prefix ~ is the bitwise complement, which coerces it's argument to an int. Applied twice, it undoes the complement.
  • Jan Grant here. I'm not an academic. I read and write a lot of code. First encountered CCS when Ari Schlesinger asked, "what does a feminist programming language look like?" - her criteria were quite interesting, I think. I like diverse opinions …