Mercurial > pymonkey

changeset 36:04a6e9a67ae5

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Added a bit to the README.
author Atul Varma <varmaa@toolness.com>
date Thu, 02 Jul 2009 15:29:07 -0700
parents 3e66613d1d4d
children d4efcbb06964
files README
diffstat 1 files changed, 19 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/README	Thu Jul 02 15:20:02 2009 -0700
+++ b/README	Thu Jul 02 15:29:07 2009 -0700
@@ -6,15 +6,26 @@
 
 Rationale and Goals:
 
+  * Python and JS are fairly complementary languages. Python provides
+    tremendous developer productivity via its dynamic language
+    features, its vibrant library of third-party client-side code, and
+    its ease of readability. JavaScript, on the other hand, is widely
+    known by a vast number of casual programmers due to its
+    availability in web browsers; it was also envisioned from its
+    conception to be executed as untrusted code, which gives it a lot
+    of security features that Python has always lacked.
+
   * There's an increasing need for being able to run JS on the server
-    side--particularly untrusted JS [1].  There's Java-based solutions
-    like Rhino out there, but nothing really mature is available for
-    the Python world.  Ideally, Pymonkey should enable a Python
-    programmer to create a custom sandboxed environment for executing
-    JS code without needing to write any C.
+    side--particularly untrusted JS [1]. For instance, being able to
+    duplicate business logic on the server and client (i.e., browser)
+    would be very useful. There's Java-based solutions like Rhino out
+    there, but nothing really mature is available for the Python
+    world. Ideally, Pymonkey should enable a Python programmer to
+    create a custom sandboxed environment for executing JS code
+    without needing to write any C.
 
   * Pymonkey should have awesome Sphinx documentation with doctests
-    and all the trappings of a model Python package.  Not only should
+    and all the trappings of a model Python package. Not only should
     it be easy for Python programmers to learn how to use the module,
     but it should also be easy for them to learn more about how
     SpiderMonkey works by reading the docs and playing around with the
@@ -22,7 +33,7 @@
 
   * Pymonkey needs to have outstanding developer ergonomics. Full
     cross-language stack tracebacks should be available, for instance,
-    and developers should be able to easily debug.  Access to memory
+    and developers should be able to easily debug. Access to memory
     profiling facilities in JS-land is a must.
 
   * The module uses the Python CAPI: no SWIG, Pyrex, or other
@@ -69,7 +80,7 @@
 ------------
 
 Right now the only example code that exists is in the test suite at
-test_pymonkey.py.  Check it out and feel free to add more.
+test_pymonkey.py. Check it out and feel free to add more.
 
 Challenges
 ----------