3 ms·
Thank you. In the spirit of understanding, can I try to summarise your points as I get them 1. Programming as it is currently practised is still very focused
by lifeisstillgood 14y ago
Thank you.
In the spirit of understanding, can I try to summarise your points as I get them
1. Programming as it is currently practised is still very focused on implementation / procedural.
2. Anyone who uses a DSP / other system to perform a task they want (agency) is doing some form of programming, and that is valid, as it is a step on the path of literacy.
3. The path of literacy might not be towards the current endpoint of neckbeards and Assembler and 10 years to be good.
4. There is likely to be new languages, new systems that will enable people to do programming / achieve agency at different points and with different degrees of abstraction
5. Its Lisp isn't it :-)
I agree with you. Which tells me I may have misunderstood!
But I am perfectly happy to agree that some form of code literacy is a good thing, and that the language of the future has not yet been invented I am also quite prepared to believe.
Aw, hell, it is Lisp :-)
Edit: I like the idea of OLPC etc being about how to meddle.
I suspect that the machine you are referencing might be the one in Nand2Tetris - an interesting project that takes undergrads from Nand gates through to compilers and languages on a virtual machine interpreting the CPU built from the interpreted Nands.
- anigbrowl 14y ago2. Anyone who uses a DSP / other system to perform a task they want (agency) is doing some form of programming, and that is valid, as it is a step on the path of literacy. Well, it's the path to literacy in signal processing (or whatever domain it happens to be). I learned to code >25 years ago and I still sort of like doing small things in assembler or throwing something together quickly in C. But I really don't like dealing with collections of big lengthy text files for projects of any magnitude. It's like reading a description of a painting that begins in the top left corner. Put another way, text is the problem. Why, I ask myself, don't IDEs automatically generate dynamic flowcharts? Why do I have to spend so much time typing to create structure, when I want to focus on algorithms? Have a look at this software, which is aimed at roboticists but has other applications; it has modules that let you drop into Ruby as needed (and there's another version that allows entry of C or assembler) but doesn't require you to work that way if you don't need it. this is what an IDE ought to look like.
- lifeisstillgood 14y agoI think I meant DSL. But, a graph of a novel is not a novel. We are story telling chimps who have created a tool in our image - a tool to tell stories to other chimps, but based on rigid symbols and calculations. Or maybe it's just late