[pypy-svn] rev 1341 - pypy/trunk/doc/funding

mwh at codespeak.net mwh at codespeak.net
Wed Sep 17 16:38:27 CEST 2003


Author: mwh
Date: Wed Sep 17 16:38:26 2003
New Revision: 1341

Modified:
   pypy/trunk/doc/funding/B2.0.0_background.txt
Log:
A little light proof-reading: improve consistency, grammar and make
the attitude to capitals a little less German...


Modified: pypy/trunk/doc/funding/B2.0.0_background.txt
==============================================================================
--- pypy/trunk/doc/funding/B2.0.0_background.txt	(original)
+++ pypy/trunk/doc/funding/B2.0.0_background.txt	Wed Sep 17 16:38:26 2003
@@ -9,7 +9,7 @@
 Wiskunde en Informatica, the National Research Institute for
 Mathematics and Computer Science in the Netherlands.  Its principal
 author is Guido van Rossum, a Dutch citizen currently living in the
-United States.  It is an Free/Open-Source language.  The most recent
+United States.  It is an Free/Open Source language.  The most recent
 version of the language is Python 2.3, released under the Python
 Software Foundation License, which is approved by both the Open Source
 Initiative, and the Free Software Foundation.
@@ -25,17 +25,18 @@
 user bases but they are either proprietary or rather low-level
 languages.  On the other hand, the languages which most excite the
 Computer Science Research community -- Self, Lisp, Haskell, Limbo, ML,
-and so on -- are nowhere on this list, yet they're the targets of most
-European academic research and innovation.  Thus European economic
-competitiveness suffers.  The innovative research lives in academia,
-trapped in languages that are rarely used for commercial development.
+and so on -- are nowhere on this list, yet they are the targets of
+most European academic research and innovation.  Thus European
+economic competitiveness suffers.  The innovative research lives in
+academia, trapped in languages that are rarely used for commercial
+development.
 
 Of those more popular languages, two, Java and Visual Basic are
 proprietary.  Sun Microsystems owns Java, and Microsoft owns Visual
 Basic.  Any company which writes its software in Java or Visual Basic
 is at the mercy of these large American companies.  And this is a
-real, and not theoretical threat.  In 2002, Microsoft announced that
-it would no longer be supporting Visual Basic 6.0 after the year 2005.
+real, not theoretical, threat.  In 2002, Microsoft announced that it
+would no longer be supporting Visual Basic 6.0 after the year 2005.
 All Visual Basic Developers have been told to convert their code to
 run under Microsoft's new .NET framework.  In 2001 Microsoft
 immediately stopped supporting its Visual J++ language, meant to be a
@@ -79,7 +80,7 @@
 implementation was execution speed. Python is a dynamically-typed,
 late-binding, interpreted language.  While this proved to provide
 extremely productive development environments, execution speed
-sometimes is not fast enough.  Today, Optimisation of high-level
+sometimes is not fast enough.  Today, optimisation of high-level
 languages must be done at run-time, and is notoriously more difficult
 to optimise than statically typed, early-binding compiled languages
 such as C or C++.
@@ -158,8 +159,8 @@
 his mails that having a minimized version of Python could provide a
 new base to advance the language.  Nevertheless, his extensions to the
 language proved to be useful for companies who needed a way to have
-millions of active objects and he had a branch of C-Python to make
-this possible.
+millions of active objects and he had a branch of CPython to make this
+possible.
 
 Some organizational experience
 ------------------------------
@@ -202,7 +203,7 @@
 Sprint and helped set up a state-of-the-art open-source development
 environment.  With his 12-year experience of setting up and leading a
 SME-company which is one of the worldwide leaders in
-Print-Preprocessing technology he helped organise the development and
+print-preprocessing technology he helped organise the development and
 net-connectivity for the various web services needed by the PyPy
 developers.
 
@@ -222,7 +223,7 @@
 would meet for Sprints in their own private time, and work on the
 prototype.
 
-After the first Sprint at TrillkeGut in Hildesheim, Jacob Hallén and
+After the first Sprint at Trillke-Gut in Hildesheim, Jacob Hallén and
 Laura Creighton organized the next Sprint at AB Strakt in Gothenburg,
 Sweden.  At this Sprint, Samuele Pedroni, the lead developer of Jython
 (a tight industrial-use integration of Java and Python), joined the
@@ -238,11 +239,11 @@
 <We need to stick Tomek here too>
 
 The third sprint was organized by interested developers in Belgium at
-the University in Louvain-La-Neuve and held June 20-24.  We invited
-Guido van Rossum, the inventor of Python to attend.  He not only
-attended the Belgium sprint but announced a few days later at the
+the University in Louvain-La-Neuve, Belgium and held June 20-24.  We
+invited Guido van Rossum, the inventor of Python to attend.  He not
+only attended the Belgium sprint but announced a few days later at the
 EuroPython conference that PyPy had a high priority on his list of
-'dreams he hoped would come true' and he enjoyed Sprinting with us a
+'dreams he hoped would come true' and he enjoyed sprinting with us a
 lot.
 
 By the end of the third one-week sprint at the University in
@@ -259,16 +260,16 @@
 
 No work had been done on actually optimising the code so it ran around
 30,000 times slower than the existing CPython-implementation but this
-was to be expected from the start.  Nevertheless, for a proof of
-concept, approximately four weeks work total for a group of about a
-dozen people, it was clearly a success.
+was expected from the start.  Nevertheless, for a proof of concept,
+approximately four weeks work total for a group of about a dozen
+people, it was clearly a success.
 
 It was time to look for funding.
 
 <
 While some people suggested to apply to DARPA for funding we realized
 that most of us were rooted in Europe and it would make more sense to
-look for european possibilities.
+look for European possibilities.
 
 I don't think that this is wise.  Why remind them that we could get
 somebody else to fund it, maybe?  Besides, everybody on the list of


More information about the Pypy-commit mailing list