News for hackers. Stuff that matters.
Re:Just what does “code as data” mean anyway? (2014) by platz on Friday February 16, 2018 @12:27PM (#16393964)
The hardware is more fundamental. (Unless you want to invoke mathematics e.g. term rewriting)

The compiler/seq of bytes example requires von neumann, because in that case it is the behavior of the whole system that is self-modifying.

You could not have the beautiful executable and interchangable files of bytes without von neumann.

Re:Just what does “code as data” mean anyway? (2014) by AnimalMuppet on Friday February 16, 2018 @12:35PM (#16394028)
I don't think that's right. There have been systems that were Harvard architecture (Motorola 88000, I think, and definitely others). But the code to run on them still started out as a sequence of bytes in a text file, that is, as data, and a compiler still took that data file and wrote another data file that was the executable image.
Re:Just what does “code as data” mean anyway? (2014) by platz on Friday February 16, 2018 @12:40PM (#16394091)
Sure, I guess