× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I can now see your reasoning and agree with you, but for one
exception: at the end of the day I am of the opinion that the server
side programmer should be doing less than 5% of Javascript coding for
any given application, and even then it should only be because of a
special circumstance. The cool thing is that this reality isn't far
fetched.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/



On Thu, Jul 29, 2010 at 4:36 AM, <hr@xxxxxxxxxxxx> wrote:
Simply to reduce learningcurves. If you agree that the future
is browserbased, the one and only programming language is
javascript (in the browser), so why not share the same syntax
on core statements on the server ?

Yes, there will be differences, browsers has DOM and AJAX,
servers has CHAIN and SQL, but a for or an if statement or
a function call could easely be the same.

A fix format RPG programmer that moves to FREE will probably
also end up coding something in a browser - why learn two new
core language syntaxes if you could spare one of them ?

Henrik


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.