On 10/12/2013 12:19 PM, Chuck Davis wrote:
Browsers are fine for displaying informaiton that is already in a database. They are the ultimate crap for entering data that has to be typed into a "form" and processed for persistence. It will be a long time before I ask my users to enter data into a browser. Just for an example: If you have 500 clients placing one order a browser is an "ok" tool -- probably the tool of choice. If you have one accounts payable clerk entering 500 orders a browser is a very mean thing to do the your employee unless the entry is simply making selections from a drop down populated from the database; that scenario is not too real-worldish for AP. And with today's auto-updating of application platforms it pretty well eliminates any advantages the browser provides for internal applications. Applications developed on the current application platforms are not only more efficient for data entry, they're just as easily kept up to date once installed. And installation is nearly automatic with the current platforms like Netbeans Platform and Eclipse Platform (for Java). I'm sure other languages have similar. Ultimately, it's a matter of choosing the right tool for the task. Unfortunately, too often these days there is a somewhat ignorant perception that a browser is always the right tool.
+1 -- Adrian Klaver adrian.klaver@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
