/PROG/BOT

HELLO FELLOW /PROG/IANS. I COME TO YOU TODAY TO ASK YOU IF YOU COULD SHARE YOUR SECRETS ON HOW TO MAKE A /PROG/OT AI SYSTEM THAT FELLOW /PROG/IANS COULD HAVE A CONVERSATION WITH. /PROG/OT AI SYSTEM SHOULD CONTAIN OUR MOST VALUABLE INFORMATION AND WISDOM FROM /PROG/ OVER THE YEARS OF ITS LIFE AND SHOULD KNOW HOW SHIT WORKS. WE SHOULD ALSO CONSIDER MAKING /PROG/OT SO INTELLIGENT THAT IT WILL SHIT ALL OVER THE FELLOW TRIPFAGS THAT SHARE THIS FELLOW BOARD WITH US.


ALL SOLUTIONS TO /PROG/OT SHOULD BE DONE IN A GOOD LANGUAGE. THIS MEANS: PYHTON, JAVA, SEPPLES, CSHARPIE, GC_LANG_NUMBER_92812 SHOULD ALL BE AVOIDED. I SUGGEST COMMON LISP.

lisp is fucking shit

also, prog+faggot=/prog/ot

>>2
also, prog+faggot=/prog/ot

faggot is the first that would come to your mind isn't it?

I bet you're an engineer that loves cock up your ass all day long don't you, ``faggot''?

We only accept the /prog/rider nomenclature.

>>3
go scrub another midget you dumb goy

>>5
Fuck off JDIF

>>6
implying

>>6
mailto:noko

>>8
implying

Braced for epic dubs

HELLO FELLOW /PROG/IANS. I COME TO YOU TODAY TO ASK YOU IF YOU COULD CHECK MY DUBS

I'll only help if (at least i, if not all) can prototype in C first ^^ that way i might learn to lisp =) [or are they completely different somehow?]

btw all wisdom of prog should be easy (-ish?) since it is all still sitting there, and all being text probably will make it easier again ^^

bag of words > bag of sentences > bag of meanings? > coherence? > ...