On Wed, 2011-09-14 at 19:32 -0700, John R Pierce wrote: > On 09/14/11 6:39 PM, Always Learning wrote: > > Ajax/Jquery is someone else's parametrised programming language. It adds > > complexity and overhead to what is fundamentally a very basic task. Ajax > > etc. seem to appeal to people who are not good (or natural) programmers. > > Ajax etc. is like programming with boxing gloves on and taking several > > weeks to do it. If they want to use it, let them. > > Ajax is not a programming language, its a technique of implementing the > client (browser) side of your applications in JavaScript, which is the > programming language. Its a programming language is my humble opinion. One has to 'code' in it. It has a defined syntax and it has a rather large and complex overhead. By the way, I also think BASH is a programming language. > ever use gmail or google documents? thats ajax. its interactive > within the USER BROWSER without requiring round trips to the web server > for every little operation such as summing up the checks entered in a > form as they are being entered. An Ajax accounting program could be > interactive like Quickbooks is, as opposed to fill in a static form and > hit submit for every little action. One never ever hits the button for every little action, does one ? My latest data entry form takes 20 separate sets of entries before the user clicks SAVE. > And, if you've never used a SQL join, you don't know the first thing > about *relational* databases, you've been using SQL as though it was a > simple flat table ISAM, DBase-style circa 1983. Might as well use > BerkeleyDB for that, its even faster and lighter weight. Golly. I grew-up in real computers. Relational databases are simply database structures, linking records. There is no reason to use joins and views IF the database is carefully planned. Joins and views are another overhead. Rule Number 000001 in programming is Keep It Simple. Index-sequential is another database access method that came along. Very useful. Access random is another. Data is actually 'flat'. It can not be anything else. However additional retrieval by non-primary key is usually desirable. Traversing chains of linked records is another method too. I've done several domestic and international contracts writing applications using relational databases. Are you more of a Sys.Op than a computer programmer / systems analyst / systems programmer / database designer / systems designer ? When SQL first came out, I think it was an IBM thing, I never liked the syntax. Years later I'm using it effectively and very productively. > but, whatever. its your project, have at it. Thank you. Thank you too for your interesting comments. -- With best regards, Paul. England, EU.