[1] https://en.wikipedia.org/wiki/Jerome_Lettvin
[2] https://www.mindstrengthbalance.com/learn/interviews/jeromel... (search for Laszlo to find the bit where they start talking about this)
1,760 karma · joined February 20, 2007
[1] https://en.wikipedia.org/wiki/Jerome_Lettvin
[2] https://www.mindstrengthbalance.com/learn/interviews/jeromel... (search for Laszlo to find the bit where they start talking about this)
[1] https://en.wikipedia.org/wiki/Rekursiv#Physical_packaging
This Egyptian strategy definitely does have a property of being easier to reason about, and one doesn't have to contend with complaints of say losing out on small amounts of metal around the cuts when one is given three smaller bars that put end-to-end are as long as another, but whose internal mating surfaces don't match up exactly.
Edit: pasting a comment of mine from here in 2019 [1]:
The language is C+@ [2]. I dug up an article about it in Dr. Dobbs Journal, the October 1993 issue. This does not seem to be the article I am remembering, since it does not go into the instruction interleaving technique anywhere near as much as I remember, but they do mention it and say it was called "beading":
The binaries produced by the C+@ compiler are independent of the underlying machine architecture. Without recompiling, applications can be moved from SPARC to 68000 to Intel x86, and so on. C+@ is not interpretive--the binaries are encoded using a sophisticated 'beading' technique developed at Bell Labs. Because of the streamlined language design, the C+@ compiler produces these portable binaries with extraordinary speed, without the need for preprocessing or front ends.
This is from the article's introduction:
The C+@ programming language, an object-oriented language derived from AT&T Bell Lab's Calico programming language, was developed to provide programmers with a true object-based language and development environment. C+@ (pronounced "cat") has the syntax of C and the power of Smalltalk. Unlike C++, C+@ includes a mature class library with more than 350 classes used throughout the system. The C+@ compiler itself is written in C+@, and all of the source for the class libraries is included with development systems. The Calico project was started at AT&T Bell Labs in the early '80s, after the introduction of Smalltalk and at the same time as C++. Calico was originally used for rapid prototyping of telecommunication services; hence, its heavy emphasis on keeping the language syntax simple and showcasing the power of the graphical development environment.*
Bane's rule, you don't understand a distributed computing problem until you can get it to fit on a single machine first.
It was a let-down: they were easier to open, but certainly not by hand, I still had to use a nutcracker. They smelled bad, too. I did not try eating them.
> No, it wasn’t.
I kind of think it was. The best argument I think is embodied in Kent Pitman's comments in this usenet thread [1] where he argues that for the Lisp Machine romantics (at least the subset that include him) what they are really referring to is the total integration of the software, and he gives some pretty good examples of the benefits they bring. He freely admits there's not any reason why the experience could not be reproduced on other systems, it's that it hasn't been that is the problem.
I found his two specific examples particularly interesting. Search for
* Tags Multiple Query Replace From Buffer
and * Source Compare
which are how he introduced them. He also describes "One of the most common ways to get a foothold in Genera for debugging" which I find pretty appealing, and still not available in any modern systems.[1] https://groups.google.com/g/comp.lang.lisp/c/XpvUwF2xKbk/m/X...
I'd also highly recommend that anyone interested in this kind of thing listen to all three of the Dynamic Languages Wizards Series panels from 2001: runtime [2], language design [3], and compilation [4]
Note that though these are videos, there isn't that much compelling in the visual portion, you could easily rip them to audio files and lose little.
[1] https://libarynth.org/fifty_questions_for_a_prospective_lang...
[2] https://www.youtube.com/watch?v=4LG-RtcSYUQ
CNN: Would you like to live in the Culture [the society he has created]?
Iain M. Banks: Good grief yes, heck, yeah, oh it's my secular heaven ... Yes, I would, absolutely. Again it comes down to wish fulfillment. I haven't done a study and taken lots of replies across a cross-section of humanity to find out what would be their personal utopia. It's mine, I thought of it, and I'm going home with it -- absolutely, it's great.
[1] https://edition.cnn.com/2008/TECH/space/05/15/iain.banks/ind...
I've probably got the details wrong, but that was the gist of it. I'd love to rediscover the analysis, but my searches have not yielded it.
It had some good stuff in it, the best of which (for me) was: when stuck, write debugging infrastructure.
[1] https://oxide-and-friends.transistor.fm
[2] https://oxide-and-friends.transistor.fm/episodes/coders-bloc...
Edit: punctuation
This thesis presents and analyzes a simple principle for building systems: that there should be a random component in all arbitrary decisions. If no randomness is used, system performance can vary widely and unpredictably due to small changes in the system workload or configuration. This makes measurements hard to reproduce and less meaningful as predictors of performance that could be expected in similar situations.
[1] https://web.archive.org/web/20111228105122/http://wrttn.in/0...
I think the article I got his take on Blade Runner from was the Paris Review [1] which is archived here [2]
[1] https://www.theparisreview.org/interviews/6089/the-art-of-fi...
Ironically enough I am an aficionado of the Waters series facility [1], which requires one to write Loop definitions for certain constructs (like defining new producing forms), so my efforts to avoid using Loop led to me using it.
I think Loop doesn't deserve the hate it gets. I don't particularly like it, but I don't dislike it that much.
[1] https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node347.html
He has sometimes talked about Blade Runner and worrying when it came out that people would think his stuff was derivative of it (it wasn't), and then said he eventually got to talk with Ridley Scott about it, and it turns out both of them had similar inspirations, namely Metal Hurlant.
I consider this book to be almost like a forerunner of the style of book that JavaScript: the Good Bits is, in that it is advocating one's use of a language to a particular subset rather being an impartial description of the whole language.
[1] https://www.nytimes.com/2019/01/04/magazine/letter-of-recomm... or https://archive.is/NIkJt