# HG changeset patch
# User Yoshua Bengio <bengioy@iro.umontreal.ca>
# Date 1285256982 14400
# Node ID 470beb000694e312c6d2e1ad776da357dc059b29
# Parent  067b2f9ba1221e7550758eee33752b55dc406ecb# Parent  32fc5f442dde1eaf006ad22928d41c1f0a8b4fd5
merge

diff -r 32fc5f442dde -r 470beb000694 doc/v2_planning/arch_src/plugin_JB_comments_YB.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/doc/v2_planning/arch_src/plugin_JB_comments_YB.txt	Thu Sep 23 11:49:42 2010 -0400
@@ -0,0 +1,26 @@
+
+YB. I am very worried about this proposal. It looks again like we would be
+creating another language to replace one we already have, namely python,
+mainly so that we could have introspection and programmable changes
+into an existing control flow structure (e.g. the standard DBN code).
+
+I feel that the negatives outweigh the advantages.
+
+Please correct me:
+
+Disadvantages:
+
+* much more difficult to read
+* much more difficult to debug
+
+Advantages:
+
+* easier to serialize (can't we serialize an ordinary Python class created by a normal user?)
+* possible but not easier to programmatically modify existing learning algorithms 
+  (why not the usual constructor parameters and hooks, 
+   when possible, and just create another code for a new DBN variant when it can't fit?)
+* am I missing something?
+
+I am not convinced that any of the stated advantages can't be achieved in more traditional ways.
+
+