You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Kent Tong <ke...@cpttm.org.mo> on 2007/02/20 03:15:33 UTC

Is this the plan?

Hi Howard,

>From the recent discussion, I am coming to an idea: Is it your vision
to bring the Ruby language features to Tapestry? For example, duck typing 
(vs explicit interface implementation), dynamic type checking and 
typeless variables (vs compile time checking), metaprogramming, mixin, 
closure, etc? Is there anything in the Java language that you would like
to keep more than those in Ruby?

If this is the case, can one summarize this strategy as writing Java code 
in the surface, but Ruby code in the essence? 

Or do you consider Ruby more suitable for doing Web UI than Java but Java 
is better in business logic, so Tapestry is used as a bridge to integrate
the two worlds?

--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Is this the plan?

Posted by Jesse Kuhnert <jk...@gmail.com>.
Don't forget about javascript. :) Not really a relevant language to
think about until recently - but with the new "real" vm capabilities
donated from adobe things should start getting really interesting. (at
a slow pace ;) ) It certainly fits the bill much closer than jruby as
far as anyone wondering what the origins of this "NBL" stuff is all
about.

Brendan's been blogging about some threading items (or hatred of )
recently as well, things that seem to go well beyond the requirements
of simple web app decorators.

On 2/19/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> What I want is to make developing web apps in Java less frustrating,
> more productive, more fulfilling. I think the presentation tier should
> be simpler. I want there to be a future in developing web apps in
> Java.
>
> In some ways, Ruby is more suited to the web since the web is "weakly
> typed" ... everything is a string.  Just look at JavaScript!
>
> What I like about Java is:
> - Familiarity, been doing it for nearly ten years now
> - Raw power, Java has eclipsed C++ is many ways, maybe even C is some
> - Acceptance in the enterprise, and below
>
> I still don't know if my coding style will adapt to Ruby, but I may
> find out pretty soon.
>
> I would kill for a proper implementation of closures (with simple
> syntax).  A lot of T5 code is closures via ugly inner classes.
>
> It's quite possible that within a couple of years, most Java
> developers will build apps using Groovy or another JVM language and
> only framework authors will "code to the metal" in traditional Java
> code.
>
>
> On 2/19/07, Kent Tong <ke...@cpttm.org.mo> wrote:
> > Hi Howard,
> >
> > From the recent discussion, I am coming to an idea: Is it your vision
> > to bring the Ruby language features to Tapestry? For example, duck typing
> > (vs explicit interface implementation), dynamic type checking and
> > typeless variables (vs compile time checking), metaprogramming, mixin,
> > closure, etc? Is there anything in the Java language that you would like
> > to keep more than those in Ruby?
> >
> > If this is the case, can one summarize this strategy as writing Java code
> > in the surface, but Ruby code in the essence?
> >
> > Or do you consider Ruby more suitable for doing Web UI than Java but Java
> > is better in business logic, so Tapestry is used as a bridge to integrate
> > the two worlds?
> >
> > --
> > Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: Is this the plan?

Posted by Howard Lewis Ship <hl...@gmail.com>.
What I want is to make developing web apps in Java less frustrating,
more productive, more fulfilling. I think the presentation tier should
be simpler. I want there to be a future in developing web apps in
Java.

In some ways, Ruby is more suited to the web since the web is "weakly
typed" ... everything is a string.  Just look at JavaScript!

What I like about Java is:
- Familiarity, been doing it for nearly ten years now
- Raw power, Java has eclipsed C++ is many ways, maybe even C is some
- Acceptance in the enterprise, and below

I still don't know if my coding style will adapt to Ruby, but I may
find out pretty soon.

I would kill for a proper implementation of closures (with simple
syntax).  A lot of T5 code is closures via ugly inner classes.

It's quite possible that within a couple of years, most Java
developers will build apps using Groovy or another JVM language and
only framework authors will "code to the metal" in traditional Java
code.


On 2/19/07, Kent Tong <ke...@cpttm.org.mo> wrote:
> Hi Howard,
>
> From the recent discussion, I am coming to an idea: Is it your vision
> to bring the Ruby language features to Tapestry? For example, duck typing
> (vs explicit interface implementation), dynamic type checking and
> typeless variables (vs compile time checking), metaprogramming, mixin,
> closure, etc? Is there anything in the Java language that you would like
> to keep more than those in Ruby?
>
> If this is the case, can one summarize this strategy as writing Java code
> in the surface, but Ruby code in the essence?
>
> Or do you consider Ruby more suitable for doing Web UI than Java but Java
> is better in business logic, so Tapestry is used as a bridge to integrate
> the two worlds?
>
> --
> Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org