A conversation with Sussman on AI and asynchronous programming
1–10 of 35 posts
Re: A conversation with Sussman on AI and asynchronous programming
#2It's the typical argument against neural nets, because they cannot explain their chain of reasoning, and so you are not able to train it to right way, or do not train into the wrong direction. when something goes wrong you got a problem.
Old AI had the same problem, that's why they added the chain to the backtracking to give better answers, and you are able to introspect answers.
Re: A conversation with Sussman on AI and asynchronous programming
#3Re: A conversation with Sussman on AI and asynchronous programming
#4Re: A conversation with Sussman on AI and asynchronous programming
#5This accountable argument is stone-old. You'll find it in an intro AI book. Of course only when implemented in lisp, so it needs be an older book. It's the typical argument against neural nets, because they cannot explain their chain of reasoning, and so you are not able to train it to right way, or do not train into the wrong direction. when something goes wrong you got a problem. Old AI had the same problem, that's…
The AI Winter is thawing... but whose lap will it fall into after the defrost? Big data mining organizations, or everyday hackers, or....?
Re: A conversation with Sussman on AI and asynchronous programming
#6Re: A conversation with Sussman on AI and asynchronous programming
#7This accountable argument is stone-old. You'll find it in an intro AI book. Of course only when implemented in lisp, so it needs be an older book. It's the typical argument against neural nets, because they cannot explain their chain of reasoning, and so you are not able to train it to right way, or do not train into the wrong direction. when something goes wrong you got a problem. Old AI had the same problem, that's…
Maybe true, but "stone-old" ideas don't mean "bad ideas". Neural networks were "stone old" until all this big data stuff went crazy and now suddenly they're on the frontpage of hacker news all the time again and people think they're the New Hotness (TM). Similar with many long-forgotten functional programming techniques which are being talked about as new stuff, much of it is refinements of old ideas, but finally hit…
It was easier for neural nets, though, because they were close to a previously successful AI mechanism (machine learning with logistic regression), it's just that we had spent decades talking about them with different words for no good reason. There's a much larger gulf between GOFAI and what we do now.
Re: A conversation with Sussman on AI and asynchronous programming
#8The thing is though... any sufficiently advanced AI is going to be unaccountable pretty much by definition. It's like, calculus is an extremely useful tool for predicting the temperature of a cooling object over time, but good luck explaining to a 3-year-old how to perform the necessary maths. The fact that they can't comprehend it doesn't mean that calculus isn't useful, it just means that it's beyond the 3-year-old's ability to intuitively grasp. In this smilie we're the 3-year-olds. :)
Re: A conversation with Sussman on AI and asynchronous programming
#9Propagators are closely related to CRDTs.
back to sussman
Re: A conversation with Sussman on AI and asynchronous programming
#10I usually end up writing a Propagating logic simulator (combining the chapters) and marveling at the working forward/backward ripple carry adder. This time I've derived all the way down to switches which infer unknown values based on their current inputs and used them to successfully create the reversible logic functions required by the Propagator model.
Fascinating stuff and highly recommended reading for anybody interested in alternative models of computation.