On Sat, Oct 7, 2017 at 3:34 PM, Mark Waser <[email protected]> wrote:

>
>
> I’ve read this mailing list for years.  It seems that the repo being
> broken is far, far more common than not.
>

Perhaps it seems that way, but its false.  In actual fact, over the course
of the last ten years, the repo has been broken about a dozen times, never
for more than a day or two, and of those breakages, perhaps only one has
been reported on  the mailing list.

The reports you see on the mailing list are always "user errors". The one
from two days ago is infuriatingly egregious.  The user apparently didn't
know what gcc was. What can you do with people like that?  From their point
of view, its all very broken, but that is not the reality.

The only viable audience for opencog, at this time, are developers with
extensive knowledge & interest in AI.  College students, even grad
students, encountering Linux and programming for the first time in their
lives, and struggling with it, do not count.  A class or two in java
programming does not making one a programmer.

Working with software is like playing the piano. Anyone can do it.  You
just hit the keys, and sounds come out.

--linas

-- 
*"The problem is not that artificial intelligence will get too smart and
take over the world," computer scientist Pedro Domingos writes, "the
problem is that it's too stupid and already has." *

-- 
You received this message because you are subscribed to the Google Groups 
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/opencog/CAHrUA36tb9620-g%2BaLH7auEwRuEoVEDt%3DykCX3-o2_YFT_T-YA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to