gsoc2011 (java): mention alternative JVM languages

1 files changed, 8 insertions, 3 deletions

diff --git a/user/jkoenig/gsoc2011_proposal.mdwn b/user/jkoenig/gsoc2011_proposal.mdwn
index d746aa4e..b5932006 100644
--- a/user/jkoenig/gsoc2011_proposal.mdwn
+++ b/user/jkoenig/gsoc2011_proposal.mdwn
@@ -181,21 +181,26 @@ which makes some packages fail to build on Hurd
 
 ### Justification
 
-Java is a popular language, used for many applications and often taught to
+Java is used for many applications and often taught to
 introduce object-oriented programming. The fact that Java is a
 garbage-collected language makes it easier to use, especially for the less
-experienced programmers. Besides, the object-oriented nature of Java is a
+experienced programmers. Besides, its object-oriented nature is a
 natural fit for the capability-based design of Hurd.
+The JVM is also used as a target for many other languages,
+all of which would benefit from the access provided by these bindings.
 
 Advantages over other garbage-collected, object-oriented languages include
 performance, type safety and the possibility to compile a Java translator to
 native code and
 [link it statically](http://gcc.gnu.org/wiki/Statically_linking_libgcj)
 using GCJ, should anyone want to use a
-translator written in Java for booting. Note that Java is
+translator written in Java for booting.
+Note that Java is
 [being](http://www.linuxjournal.com/article/8757)
 [used](http://oss.readytalk.com/avian/)
 in this manner for embedded development.
+Since GCJ can take bytecode as its input,
+this expect this possibility would apply to any JVM-based language.
 
 Java bindings would lower the bar for newcomers
 to begin experimenting with what makes Hurd unique