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

[lac at codespeak.net]

Author: lac
Date: Wed Nov 14 16:02:03 2007
New Revision: 48679

Modified:
   pypy/extradoc/talk/pycon2008/proxy-abstract.txt
Log:
minor tweaks.  fijal, its good.


Modified: pypy/extradoc/talk/pycon2008/proxy-abstract.txt
==============================================================================
--- pypy/extradoc/talk/pycon2008/proxy-abstract.txt	(original)
+++ pypy/extradoc/talk/pycon2008/proxy-abstract.txt	Wed Nov 14 16:02:03 2007
@@ -5,29 +5,37 @@
 
 Summary (max 100 words, for the website):
 
-In this talk we will outline PyPy's unique features, namely
+In this talk we will outline some of PyPy's unique features, namely
 sandboxing, transparent proxying, our distribution prototype and our security
-prototype, the taint prototype. We would also like to summarize our design
-decisions which make it possible for such features to be non-pervasive to the
-core interpreter codebase. Those features also works out of the box on
-different PyPy target platforms (C/POSIX, .NET, JVM) from the single
-interpreter source.
+prototype (also known as the taint prototype). We would also like to 
+present and summarise the design
+decisions which makes it so easy to implement such features.
+
+One additional benefit of our design decisions is that low-level
+decisions do not permeate the codebase.  Thus, these features are not
+platform-dependent.  They work out of the box on different PyPy target
+platforms (C/POSIX, .NET, JVM) from a single interpreter source.
 
 Description and outline:
 
 In this talk, we would like to present our paradigm-shifting architecture
 for dynamic languages and some features which are exclusively available in
-PyPy due to our novel approach. Also thanks to our design, those features
+PyPy due to our novel approach. These  features
 are available on all of our target platforms (C/POSIX, .NET, JVM) and are
 independent of other decisions (garbage collector, stackless, JIT, etc.)
+The result is an unprecidented ability to mix-and-match low-level
+internal implementation details so that we can really serve you a
+'Python as you like it'.
 
 Talk outline:
 
 * Quick recap of our motivation for creating PyPy.
 
+demos including
+
 * The transparent proxy, which allows programmers to create
   indistinguishable proxies for any type in Python (including built-in
-  python types like frames), with various usage showcases including
+  python types like frames), with various demos including one for
   our completely transparent remote access scheme.
 
 * the PyPy Sandbox, which allows one to run a full python
@@ -37,8 +45,12 @@
 * The Taint Object Space, which allows programmers to make sure that sensitive
   information does not cross I/O barriers.
 
+
+We conclude with a little bit of philosophy.
+
 * Why our approach of doing pervasive changes to semantics does not
   require pervasive changes to the interpreter core.
   Why our design allows us to describe a broad class of such changes
   as a "proxying operation" and finally, why design matters when you want
-  to get a butterfly out of a caterpillar instead of a bigger caterpillar.
+  to get a butterfly out of a caterpillar instead of just a bigger,
+  healthier caterpillar.