Joe Armstrong Quotes
1950–2019 United States
Joseph Leslie Armstrong (27 December 1950 – 20 April 2019) was a computer scientist working in the area of fault-tolerant distributed systems.
- United States
- Computer scientists
Also known as: Joe Armstrong
Random Joe Armstrong quote
110 quotes
The different ways of hiding the state are the things that different functional programming languages offer. In Haskell they call it monads, in Erlang they call it processes.
The cornerstones of fault tolerant programming are to isolate errors to make sure if one thing crash it does not crash anything else. That's what the processes in operating system do.
We should get the Congressional Medal for creating employments because we have created billions of man hours of maintenance work for people in the future. We are the job creators of the future.
Every Erlang process in the universe should be addressable, and trace backed if we wish they will talk together.
PHP, brilliant language! Apart from the syntax and the semantics. Because it takes a view that will perform everything in one place.
Bad ideas in computer science and anywhere are sticky. If the first idea was a bad idea, then because it works people will sort of repeat it.
You know, there are two types of languages, there are languages that people bitch about and there are languages that nobody uses.
Erlang was specifically designed for fault tolerance, it was not designed for anything else.
Documents are full of paragraphs. But the paragraphs don't have name. So, we can't talk about the paragraphs.
Processes are isolated by design. Context switching are very lightweight. The processes by design cannot damage each other.
Computing was about controlling complexity and we have failed miserably.
Helping your non-technical neighbor. Tell them it's not your fault. Tell them it's crap software and I don't understand this crap.
I just want to model what’s going on in the real world
The problem is more than just the should do when it works, it should also say what it should do in presence of failures that you could reasonably predict.
If you try to fiddle around with your code to make it efficient, that's the wrong thing to do. Keep on track with the latest hardware. That's the right thing to do.
Object Oriented Programming, this is the art of hiding side effects. If you can do it successfully you can write this in program. If you do it unsuccessfully, you get in a sucking mess.
The web is totally broken. It's not symmetric.Easy to read stuff, very difficult to write stuff. We ave a community of users who engage passively by reading stuff, they do not write stuff.
Don't be deluded into thinking that is sort of ultimately fault tolerant. You can only provision it for the faulty things that might happen and then for a large class of things it could happen.
Computer systems fail. We have to deal with it, we can't ignore it.
I think we seem to have forgotten that things can be small. This way of decomposing systems into small things that I can reason about.