Hi,
You're probably right, but I'm not sure that there is only one way of
thinking, it depends really on what you want to do.
The problem is to define the objectives to explain a technic exposed.
In general, I think that the excess is not good whatever domain we are
speeking.

When we look at a simple web application, we can immediately see what is the
purpose of the server side and what is the purpose of the client side, and
in addition I think that we don't have to send more information to the
client than necessary from a loading time point of view (I'm not speaking of
intranet applications, but optimized internet applications)

When I was speaking about a templating system, it was not to generate
javascript, but just to take the right variable depending on the language
and fill in the page with. It's not CPU intensive. In a php templating
system (sorry I don't practise java) you separate the php code (server side)
from the xhtml/css/javascript code (client side). The php server code is
executed and the templating system take the result to choose the right
client side and fill in the variable with the result befor sending the page
to the browser.

I stay on my position, coding all in a language is a
marketing/fashion/extremist point of view. In the real world the truth is in
a combination of the best of each languages.
But I respect your explanation and the fact that a lot of people are
re-discovering javascript today (a lot of years after its reject). I'm just
prudent that's all.
Regards
--
View this message in context: 
http://www.nabble.com/qooxdoo-features-t1179697.html#a3120706
Sent from the qooxdoo-devel forum at Nabble.com.



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to