I’m a big fan of Functional Programming; I think it’s great.
I’m a big fan of Object Oriented Programming; I think it’s great.
I’m a big fan of Procedural Programming; I think it’s great.
I’m a really big fan of using all three together at the same time. I think that should be our standard.
Functional has a lot of great things that mix well into OOP as well.
Been doing this at work in Java.
Think about designing programs that operate in a physically constrained state-space
Been there. Done that. I spent a lot of time with mini-computers and micro-computers in the seventies and eighties. I wrote a _lot_ of assembler for the 8080 in an embedded real-time process control environment.
From: (Primordial) at 10/02 21:25
> Think about designing programs that operate in a physically constrained state-space
CC: #[4]
With all due respect I don't think you understand what I meant.
How could you write a program where the control actions need to be tied to intentionally PHYSICALLY costly bits of information? Such a program would be theoretically unhackable.
Bitcoins network is a physically constrained state-space, what people choose to call Satoshis are from a first principles perspective really just physically costly bits of machine readable information.
This network can imbue its properties of physical security to virtually any other software or computer network if its designed in the right way.
This is a paradoxical way of thinking because most computer engineers only think about making smaller, faster, and more energy efficient chips/systems. The problem with this kind of thinking is that it's impossible to achieve systemic security by using only encoded logic. Encoded logic, no matter how cleverly designed, cannot prevent that logic from being exploited. To achieve systemic unhackable cyber security, we have to design intentionally large, slow, and energy intensive state-space that is physically constrained.
This is what Satoshi did with his protocol. His protocol incentivized humans to begin creating a planetary-scale state mechanism with these physically constrained properties. The Bitcoin networks motherboard is the global electric power grid, and it's state-changing transistors are the power generators.
These physical constraints allow us to take the underlying physically constrained bits of information and use them to design programs that are unhackable.
In short, I'm not talking about spacially constrained hardware, I'm talking about applying physical constraints to the actual bitsvof information themselves (Satoshi did this part) and then using those physically constrained bits of information in ways that secure other software and networks.. that is.. to treat these bits of information in ways other than simply assigning monetary value to them.
This is the future.
