Re: [Jython-users] jython to java?

[Ype K. <yk...@xs...>]

John,

you wrote:
<snip>
>
>I've been looking for something like python for years.  It's the best!
>I finally have a medium in which I can express my algorithms.
>
>But...  As I heard years ago and still agree with, it's not the tool
>but the person that champions the tool.  I'm afraid I'm currently not
>in a good position in my current group to champion Python.  Over the
>years I've noticed a pattern.  New tribes arrive on the scene and
>wrestle with the presiding regime for power.  It's not enough to show
>up and do good work in order to lead us in a new direction.
>Consistently, the new groups actually has little to offer beyond their
>self marketing and soon must resort to bashing the old group in a
>desperate attempt to gain favor with the mother & father figures.

It's unusual to see things like bashing around python/jython.
They don't need it.

>Well, I guess that's politics and can be expected.  But, having made
>the "mistake" of actually produced working software in the past I am
>now a target.  If I say it's white then the reply is often that it's
>black.  Ugh.  The tide will turn but slowly.  In the meantime I am
>ridiculed for trying Python.
>
>Is there a lesson here for those who would like to see Python/Jython
>become mainstream?  Certain religions have clauses requiring members to
>pass the word.  It's lead to nasty conflicts but who can argue with
>their numbers.  And then there's the tobacco companies...

Iirc, you work in a Java environment. As long as you're allowed to
put jython.jar on the class path, and you are willing to write a tiny
bit of code to allow embedded jython scripting, you can use Jython
where you see fit.
Popular areas are:
- exploring Java API's interactively,
- testing,
- prototyping.
Before long you'll hit one of these. Remember how Linux is getting popular?

<snip>
>...  I highlighted the chart that I
>interpreted to say that Python is the *best* choice for productivity.
>It was the only thing pinned to my cube wall.  Alas, there was a flaw
>in my thinking that young rogue programmers (excuse me, anal ists with
>advanced degrees) can be taught anything based on objective research. 

People are primarily based on habits, and it is a personal investment
to get familiar with a new programming language.
 
From Java to Jython is quite straightforward as
Jython is almost readable when you know Java. Just
shake off the type checking mood introduced by the Java compiler,
bite through one or two syntax quirks, and productivity is there.
(Perhaps I am a bit overoptimistic, but if they have
advanced degrees, who knows?)
Then start writing adapters in two or three lines, instead of
in two or three classes/interfaces, and you're sold for the rest
of your career.
And then you have only just begun:
- change a GUI within 20 seconds for prototyping,
- from threading import WhatYouNeed, instead of Java synchronized/notify/wait.
- implement a state pattern by simply reassigning methods,

Have fun,
Ype