In my opinion, the domain of software development is far too ambitious for the first AGI. Software development is not a closed domain. The AGI will need at least knowledge about the domain of the problems for which the AGI shall write a program.
The English interface is nice but today it is just a dream. An English interface is not needed for a proof of concept for first AGI. So why to make the problem harder as it already is? The domain of mathematics is closed but can be extended by adding more and more definitions and axioms which are very compact. The interface could be very simple. And thus you can mainly concentrate to build the kernel AGI algorithm. -Matthias Trent Waddington [mailto:[EMAIL PROTECTED] wrote Yes, I'd want it to have an English interface.. because I'd also expect it to be able to read comments and commit messages in the revision control and the developer mailing lists, etc. Open Source programmers (and testers!) are basically "disembodied" but they get along just fine. I'd also expect it to be able to "see" windows and icons and all those other things that are part of software these days. I wouldn't expect it to be able to test a program and say whether it was working correctly or not if it couldn't even see it running and interact with it. Of course, if you're testing command line apps you could get away with a much simpler "sensor". Trent ------------------------------------------- agi Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/ Modify Your Subscription: https://www.listbox.com/member/?member_id=8660244&id_secret=117534816-b15a34 Powered by Listbox: http://www.listbox.com
