Well isn't OpenCog having a busy weekend :) As a lurker I have already 
expressed my dissatisfaction at "advanced C++" which is the trend in the 
project, and would probably carry over my disapproval of "idiomatic C#". 
There is absolutely no reason for the coding to be more difficult to 
comprehend that OpenCog's design itself. If anything, the code should make 
plain and simple what the bloody design is trying to do! Now, my particular 
wet dream would be to see people pulling together their own "free 
resources", like the free tiers at AWS, Google Cloud etc, to create a 
hive-mind. If somebody was brilliant enough to throw away big chunks of the 
code and instead achieve (some of) the same results with a DB of sorts, AWS 
lambda etc, that would be quite something. Then, for the parts that don't 
fit the "cloud" box, if someone could come up with the "CloudCog", some 
probabilistic graph, inference engine or whatever is missing from the 
garden variety PAAS and SAAS, then we could really be heading somewhere. I 
don't know much about the project beyond the demos, but I do believe the 
project is being hurt by the general unavailability of a constantly running 
instance that "does something", whatever that maybe, and somehow can be 
accessed by the public, eg through an API. Presumably this new hedge fund 
thing may be the closest OpenCog has come to being a 24/7 system, and Ben 
will probably tells us if he finds out a better way to do things with and 
without this codebase

AT

-- 
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 opencog+unsubscr...@googlegroups.com.
To post to this group, send email to opencog@googlegroups.com.
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/2668e4aa-5324-4a66-9786-c795daad157c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to