821 karma · joined February 23, 2012
No, it is equivalent to the post office showing the letter to someone else.
Isn't passing a function to itself kind of like recursion?
But a good reactive system is simpler to write, understand, and debug. At least that is what I found in my latest project.
I find it easy to avoid side-effects in imperative reactive code. With side-effects I wouldn't call it reactive.
> , if you add in the constraint that you can't change signal routing at runtime
Once again, this is easy in imperative code.
I am not complaining about functional code. It definitely has its place (just not for me). I just finished an awesome product with imperative reactive code and I thought maybe I was missing something.
On day an IBM tech was bringing up the system using a check-list. He noticed a red light that said "temperature". He noted it in the log and kept going. It turns out he had forgotten to turn the water on. After a short while the room filled with smoke.
The machine was ruined. After the machine was replaced, the IBM office kept one of the old PC boards on the wall. It was curled up like a potato chip.
I had tried to use the mail-order drugs provided by insurance companies and they were a disaster. I couldn't find out what was coming when. Drugs would seemingly-randomly show up in my mailbox.
Not a very interesting benchmark. This would only measure net latency and spin-up time.
Or if the animal fell out of the sky. (2 points for being old enough to know the reference).
> Also involved ... aquatic expert James Houtz.
Not much of an expert if the didn't know about the waves.
The first that I know of is when some Santa Cruz (hippie capital) students set up electronics to record the timing of drips for a paper. They were going to break the pattern down to understand it. They tried and tried but the pattern always seemed random.
With the help of other researchers they discovered it was caused by chaos. This was the first time that chaos theory was described, although Feynman had noticed that some equations behaved weirdly when banging on his calculator.
There was a catch though. If you wanted to sell your development you had to give HP first right of refusal. If HP didn't want it you could do whatever you wanted with it.
The Apple 1 was a G-Job. Wozniak offered it to HP and they refused. So he was able to sell it.