Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

In practice

Name: Anonymous 2011-04-19 20:59

In practice, however, the type system constrains the programmer in many ways that are unacceptable to Lisp programmers: data cannot be interpreted as programs, lists must be homogeneous, and functions are not easily redefned without recompiling other dependent functions.

Name: Anonymous 2011-04-20 10:36

>>21
statically-typed languages kill the programmer's freedom big-time.
We should start some kind of a project aimed at having a completely Free, completely dynamically typed software stack.

I mean, you can be completely Free, as a programmer, when your LISP interpreter is written in Unfree C. Freedom just doesn't work this way.

So you should have a dynamically typed, Free, interpreted interpreter, running on top of dynamically typed, Free, interpreted OS, with dynamically typed, Free, interpreted drivers, and all that runs on FPGA. Except that we need the New Kind of FPGA, which allows reprogramming during execution, in the true dynamically typed, Free, interpreted fashion.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List