[pypy-svn] r48578 - pypy/extradoc/talk/pycon2008

lac at codespeak.net lac at codespeak.net
Sun Nov 11 16:53:22 CET 2007


Author: lac
Date: Sun Nov 11 16:53:21 2007
New Revision: 48578

Modified:
   pypy/extradoc/talk/pycon2008/proxy-abstract.txt
Log:
My grammar fixes, and some thoughts before its conference time



Modified: pypy/extradoc/talk/pycon2008/proxy-abstract.txt
==============================================================================
--- pypy/extradoc/talk/pycon2008/proxy-abstract.txt	(original)
+++ pypy/extradoc/talk/pycon2008/proxy-abstract.txt	Sun Nov 11 16:53:21 2007
@@ -1,27 +1,45 @@
-XXX Title (inside pypy seems to be too "inside")
-================================================
+XXX Understanding PyPy, and How It Let's You Do Things You Have Only Dreamed About. (*)
+================================================================================
+(* for particularly nerdy dreams :-) )
 
-In this talk, we would like to present few features exclusive to
-the PyPy python interpret and novel-implementation approaches
-which made it easy to implement those features. The talk would
-consist on:
+In this talk, we would like to present our paradigm-shifting architecture
+for dynamic langauges and some features which, due to our appraoch
+are exclusively available with PyPy.  
 
-* Transparent proxy concept, which allows programmers to create
+Topics would include:
+
+* The transparent proxy, which allows programmers to create
   transparent object of any type in python (including built-in
   python types like frames), with various usage showcases including
   our completely transparent remote access scheme. (XXX: I know what
   you mean, but "create transparent object" is a bit vague)
 
-* Sandboxing concept, which allows to run non-stripped version of
+* the PyPy Sandbox, which allows to run non-stripped version of
   python interpreter in a controlled environment with custom
   safety policy.
 
-* Taint object space, which allows programmers to make sure that sensitive
-  informations do not cross the I/O barrier.
+* The Taint Object Space, which allows programmers to make sure that sensitive
+  information does not cross the I/O barrier.
 
-* XXX anything else?
+* XXX anything else?  lazy evaluation?
 
 * Why our approach is "working by design", rather then "fix as long as
   anyone complains", why it's only permitted by our design decisions and
   abstraction levels. How our all of the mentioned above examples could
   be reduce to simple "proxy operation" concept.
+
+  'working by design' means something else.  it means 'we designed it
+  to work, which, of course, is true of everything that didn't happen
+  by accident (and maybe that too, if some people's ideas of God are
+  are correct).
+
+* _why_ design matters.  _when_ design matters.  Some thoughts on when
+  incremental improvements are not the answer, and why successive
+  improvements in painting things red will not turn your children's
+  wagon into a firetruck, despite being the perfect approach to the
+  problem of 'making what I have red'.
+
+I am getting all these weird ideas of how a caterpillar becomes a
+larger caterpillar is not the same way a caterpillar becomes a
+butterfly.  Either this is a useful analogy, or I am nuts.
+



More information about the Pypy-commit mailing list