Tenjin is a great templating library that gets not only cross platform but baseplane ability to make templating very similiar (and FAST) across many languages. pyTenjin and phpTenjin is currently what I am using but there are executions for Ruby, Perl and Javascript.

Here is a list of the Tenjin Templating engines:

• pyTenjin
• phpTenjin
• rbTenjin
• jsTenjin
• plTenjin

Changes

(Python) (Ruby) (PHP) (Perl) (JavaScript)

User’s Guide

(Python) (Ruby) (PHP) (Perl) (JavaScript)

FAQ

(Python) (Ruby) (PHP) (Perl) (JavaScript)

Examples

(Python) (Ruby) (PHP) (Perl) (JavaScript)

Presentation

2007 LL Spirit LightningTalk (full-version) (Japanese)

Here is what the template markup looks like:

This

<table>
<tbody>
<?py i = 0 ?>
<?py for item in ['<foo>', 'bar&bar', '"baz"']: ?>
<?py     i += 1 ?>
<tr>
<td>#{item}</td>
<td>${item}</td>
</tr>
<?py #end ?>
<tbody>

</table>

Produces This

<table>
<tbody>
<tr>
<td><foo></td>
<td>&lt;foo&gt;</td>
</tr>
<tr>
<td>bar&bar</td>
<td>bar&amp;bar</td>
</tr>
<tr>
<td>"baz"</td>
<td>&quot;baz&quot;</td>
</tr>
<tbody>
</table>

Here are some speed results

JSON-RPC is the answer to the argument that XML RPC is too verbose and bloated and convoluted.  JSON is just about as simple as you can get in data formats and it is becoming a great baseplane standard and is a tool that spans many platforms.

“Does distributed computing have to be any harder than this? I don’t think so.”

Can it be even simpler ?

JSON-RPC is lightweight remote procedure call protocol similar to XML-RPC. It’s designed to be simple!

• specification
• python package implementing JSON-RPC
• more implementations
• services
• about JSON-RPC

JavaScript

• There is a JSON-RPC implementations as part of JavaScript O Lait jsolait.
  You can also find some live examples
• The Open Source TelePort Library supports JSON-RPC as well as other RPC protocols.
  Live demos and documentation can be found here.
• JSON-RPC to Java bridge includes a JavaScript client.
• Dojo Toolkit 0.3 implements JSON RPC.
• JSON/XML-RPC Client Implementation which abstracts-away the differences between JSON-RPC and XML-RPC and permits cross-site requests.

C

• JSON-RPC C Bridge. There is also support for GoAhead WebServers.

C#

• .NET and ASP.NET

Erlang

• YAWS JSON-RPC module (HTTP client/server)

Java

• JSON-RPC to Java bridge
• JRP

Lisp

• Common Lisp

Lua

• Lua

Perl

• Catalyst using the JSONRPC plugin
• JSON module

Php

• JSON-PHP
• php-json
• PHP-O-Lait
• Phpxmlrpc (in the ‘extras’ package)
• SCA_SDO Pecl Package
• JSON_RPC_Server, a JSON-RPC implementation in PHP
• JSON/XML-RPC Server Implementation which abstracts-away the differences between JSON-RPC and XML-RPC.

Python

• A python package which implements the JSON-RPC specs. It includes an mod_python handler, a CGIHandler, a TCP server and (soon) a ServiceProxies implementation.
• CherryPy (python)
• Zope 2
• Zope 3
• Twisted JSON-RPC – Web, Web2, and TCP

Ruby

• Ruby

Frameworks

• Catalyst (Perl) using the JSONRPC plugin
• CherryPy (python)
• JRP
• .NET and ASP.NET
• Zope 2
• Zope 3

Mono is a great open source .NET implementation that has been looking to being a baseplane dream to .net development. They even have Moonlight which will eventually be caught up with Silverlight development.

However today mono gets a killer IDE in the MonoDevelop name.

[insertname]Develop projects are largely based on the SharpDevelop IDE that is one of my favorites with .net and is open source. If you are looking for a FAST IDE SharpDevelop is that. In the FAQ Miguel mentions that MonoDevelop is a port or branch of SharpDevelop which is great news for quality, speed and usability.

FlashDevelop is also another great kit based on this IDE framework. I am very pleased Mono is using the same standard for IDEs that mimic VS.NET only much more speedy and usable in SharpDevelop and FlashDevelop (both .net apps themselves and two of the only good winforms apps there ever were).

I highly recommend mono and MonoDevelop. These are tools that are baseplane languages and platforms that have all the benefits of .net development but for any platform and now for any platform as an IDE. One problem with FlashDevelop is that it is only for Windows machines but maybe MonoDevelop will influence and will allow it for other platforms as well and everyone will be able to use the best IDE there is for flash and flex development.

In the meantime if you are a .net developer and want to develop for multiple platforms not just Windows then Mono is your tool and MonoDevelop is your IDE.

The main features of MonoDevelop are:

• Customizable workbench, including custom key bindings, custom layouts, and external tools.
• Support for several languages, with C#, VB.NET and C/C++ support included, and Boo and Java (IKVM) support available as separate add-ins.
• Support for code completion and type information tooltips.
• Refactoring operations to simplify changes like renaming types and type members, encapsulating fields, overriding methods, or implementing interfaces.
• Code navigation operations such as jumping to variable definitions and finding derived classes.
• Easy to use GUI designer for GTK# applications, also supporting the creation and management of custom GTK# widget libraries.
• Integrated source code version control, with support for Subversion.
• Integrated unit testing based on NUnit.
• Support for ASP.NET projects, allowing web projects can be built and tested on XSP.
• Integrated database explorer and editor (beta).
• Integration with Monodoc, to provide documentation about classes.
• Support for makefiles, both generation and synchronization.
• Support for Microsoft Visual Studio project formats.
• Packaging system that allows generating tarballs, source code and binary packages.
• Command line tools for building and managing projects.
• Support for localization projects.
• Extensible add-in architecture.

Sun has been on a rampage lately. They recently purchased MySQL (which has some questions with InnoDB) but they also are supporting Python and integrating it into the VM offerings with Jython.

So now we have Google (They employ Guido), Microsoft (IronPython) and Sun (Jython) all turning into Python-istas. Does this mean Python is destined for greatness in the near future? Well I recommend learning it. It is a great language and it has a high productivity rate. Time will tell if it has the ability to be in extremely large code bases. I think it is just a matter of the architecture and organization as with any project.

Jonathan Schwartz at Sun mentioned also taking the “J” out of “JVM” to just make a VM much like a .NET framework. So Microsoft copied Java with C# the JVM and added multiple languages. Then Sun comes back and added multiple byte code compiled languages. And then they both focus on dynamic engines to implement versions of Python, Microsoft doing this within their DLR.

Many times the larger market languages that end up running business or “enterprisey” are heavily influenced by companies, in addition to the other demands from consumers, which here is programmers. So when the big three are all banking on Python as a draw there is a definite market draw there and a tell on the future. But I think it is apparent that Python is becoming a standard market baseplane language.

It is great to be able to use other libraries from .net with IronPython and java libraries with Jython. It has found a way to integrate with the current infrastructure and the language has low bar entry but deep benefits. Python is snaking its way into the market.

Python is so non verbose…

import sys
import clr
from System.IO import Path, Directory, FileInfodir = Path.Combine(sys.prefix, 'DLLs')

if Directory.Exists(dir):
    sys.path.append(dir)
    files = Directory.GetFiles(dir)
    for file in files:
        if file.lower().endswith('.dll'):
            try:
                clr.AddReference(FileInfo(file).Name)
            except:
                pass

This sample is from IronPython showing adding dynamic references to all dlls loaded.

Check out this HTML/XHTML parser in pure Python.

from HTMLParser import HTMLParserclass MyHTMLParser(HTMLParser):
def handle_starttag(self, tag, attrs):
print "Encountered the beginning of a %s tag" % tag
def handle_endtag(self, tag):
print "Encountered the end of a %s tag" % tag