Wishlist/BuiltInScriptingLanguage - Revision history

Yavannadil: /* Lisp/Scheme/Guile */

2009-11-23T17:49:42Z

‎Lisp/Scheme/Guile

2009-02-04T09:43:13Z

Added link for PHP-GTK bytecode to the PHP bcompiler extension (some people is not aware about the extension).

2009-02-04T09:41:59Z

2009-02-04T09:15:58Z

Added PHP-GTK to the list.

2008-10-02T04:19:44Z

‎Summary

2008-10-01T12:06:19Z

‎Feature matrix

2008-09-12T20:25:55Z

‎Python

2008-09-12T20:23:31Z

‎Lua: grammar

2008-08-31T13:07:39Z

‎Feature matrix: Added Groovy VM scripting langage.

2008-08-31T13:06:53Z

‎Java: Added Groovy VM scripting langage.

@@ Line 231: / Line 231: @@
 === Lisp/Scheme/Guile ===
-# There are a lot of Lisp variants available.  It is the second oldest high-level programming language available, yet still retains moderate popularity for new projects.
+# There are a lot of [[Lisp]] variants available.  It is the second oldest high-level programming language available, yet still retains moderate popularity for new projects.
 # Lisp variants have been run on 16K computers.  Usable variants are substantially larger, but will be significantly smaller than Python.
 # Lisp syntax is very simple, and hated by many.  :)
@@ Line 237: / Line 237: @@
 # GTK2 and D-BUS bindings are available
 # [http://galinha.ucpel.tche.br/platforms#openmoko Chicken Scheme interpreter] and runtime library packaged for Openmoko
 === Java ===

@@ Line 85: / Line 85: @@
 |align="center" |Light
 |align="center" |Medium
-|align="center" |Bytecode
+|align="center" |[http://dk.php.net/bcompiler Bytecode]
 |align="center" |Y
 |}

@@ Line 81: / Line 81: @@
 |align="center" |Y
 |-
-!align="center" |PHP-GTK
+!align="center" |[[PHP-GTK]]
 |align="center" |Active
 |align="center" |Light

@@ Line 79: / Line 79: @@
 |align="center" |Light
 |align="center" |N
 |align="center" |Y
 |}

← Older revision		Revision as of 04:19, 2 October 2008
Line 282:		Line 282:

	By looking at the [http://www.gnome.org/mobile/ GNOME Mobile & Embedded Initiative] page, I see that there is a picture of the [[Neo1973]] and a picture showing the GNOME Mobile Platform with C, C++ and Python mentioned. Is there a strong reason not to pick Python as the language for the device? --[[User:Nakedible\|Nakedible]] 12:30, 30 April 2007 (CEST)		By looking at the [http://www.gnome.org/mobile/ GNOME Mobile & Embedded Initiative] page, I see that there is a picture of the [[Neo1973]] and a picture showing the GNOME Mobile Platform with C, C++ and Python mentioned. Is there a strong reason not to pick Python as the language for the device? --[[User:Nakedible\|Nakedible]] 12:30, 30 April 2007 (CEST)
		+
		+	I agree with the above: Python is a well developed and maintained language, easy to learn, and plays well with others (C/C++). As stated above, it is popular and part of the GMP. --[[User:King\|King]] 04:19, 2 October 2008 (UTC)

	[[Category:Software ideas]]		[[Category:Software ideas]]

@@ Line 48: / Line 48: @@
 !align="center" |Haskell
 |align="center" |?
-|align="center" |?
+|align="center" |Heavy
-|align="center" |?
+|align="center" |Light
-|align="center" |Y
+|align="center" |Native, JIT and bytecode
 |align="center" |Y
 |-

@@ Line 201: / Line 201: @@
 # OLPC uses Python heavily and may produce applications suitable for porting to Openmoko
 # Python is the only language besides C / C++ mentioned in GNOME Mobile & Embedded Initiative Mobile Platform
-# Python has been successfully used to create well-working and fast programs for the Nokia 770/800 devices, such as [http://konttoristhoughts.blogspot.com/2007/03/uk-media-player-is-nearing-first-public.html this].
+# Python has been successfully used to create well-working and fast programs for the Nokia 770/800 devices, such as [http://konttoristhoughts.blogspot.com/2007/03/uk-media-player-is-nearing-first-public.html this media player].
 # Jython would make it almost 'free', but it's slower and [http://www.jython.org/docs/differences.html not identical] to CPython.

@@ Line 183: / Line 183: @@
 # It has first class closures and coroutines (a.k.a. greenthreads).  A fundamental building block of Lua is the ability to redefine any defined or undefined aspect of the language; this provides very good runtime metaprogramming ability.  [http://metalua.luaforge.net/ metalua] provides full compile-time metaprogramming (a.k.a. Lisp-style macros), if such extremes are needed.
 # Bindings are available for GTK2. Reference the [http://lua-users.org/wiki/LibrariesAndBindings Lua Libraries and Bindings] page. Specifically the [http://luaforge.net/projects/lua-gtk/ Lua-gtk project]
-# Performance are substantially better than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=python Python's] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua Perl's].
+# Performance is substantially better than [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua&lang2=python Python's] or [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=lua Perl's].
 # It is very easy to embed: it's designed for seamless integration with C, in both Lua->C and C->Lua directions.
 # [http://www.freepoc.org/viewapp.php?id=32 Example Implementation] for Symbian.

@@ Line 23: / Line 23: @@
 |align="center" |Heavy
 |align="center" |JIT/gcj
-|align="center" |Y (Jython/JRuby)
+|align="center" |Y (Jython/JRuby/Groovy)
 |-
 !align="center" |Python

@@ Line 240: / Line 240: @@
 # If we're really lucky, people will realize that Java Virtual Machine belongs on embedded devices and has great performance there.
 # The Java API greatly reduces plumbing work and helps simplify application development greatly.  In addition, we can add to it providing additional APIs for the mobile device and then these would be available to all of the applications.
-# The JVM has built in support for adding scripting languages, so regardless which we choose, it _should_ be on Java Virtual Machine.  Studies have shown that many features of the scripting languages actually run faster on the JVM.  Currently there are many scripting languages that we can use, including: javascript, ruby, python, and javafx.  This would be a huge win for the device.
+# The JVM has built in support for adding scripting languages, so regardless which we choose, it _should_ be on Java Virtual Machine.  Studies have shown that many features of the scripting languages actually run faster on the JVM.  Currently there are many scripting languages that we can use, including: javascript, ruby, groovy, python, and javafx.  This would be a huge win for the device.
 # JavaFX is a Multimedia based scripting language that adds wow to devices
 # The Neo1973 was demoed at JavaOne running the JavaFX Mobile so there is already a lot of reusable work in this area.