|
Gary,
Peacock had it wrong also.
"thick" vs "thin" client applies to the application software, not the
supporting infrastructure such as a browser.
So, a green-screen app is "no client at all".
A web app is "thick client" if lots of the app functionality is implemented
in javascript and runs in the browser.
For example, an EmberJS web app is "thick".
A pure PHP app (which only emits HTML) is "no client", as all the app code
is on the server.
A web app, with a bit of jQuery, which only does presentation, and no
processing/validation is "thin".
A VB app, can be "thin", or "thick".
etc.
On Thu, Jan 23, 2014 at 9:05 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx>wrote:
Here's some fuel for the fire...
A colleague at another company once said "If you think a Browser is a thin
client, think again. If you don't believe me just look at the size of a
web browser. You'll see it is pretty thick!"
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Olson
Sent: Thursday, January 23, 2014 10:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: Usability tell
Looks like the web page implementation wasn't properly thought out in that
example. Perhaps a windows form application would have been more
advantageous instead of a web application.
Perhaps this will give you a compelling reason why you want to start
thinking towards the future and going to the web instead of the green
screen:
http://www.extremetech.com/gaming/154994-epic-mozilla-release-unreal-engine-3-html5-demo-to-the-public-and-its-awesome
-----Original Message-----
From: Dan Kimmel [mailto:dkimmel@xxxxxxxxxxxxxxx]
Sent: Thursday, January 23, 2014 11:12 AM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: Usability tell
Those interested in the Greenscreen vs Webpage usability debate will find
this blog compelling:
http://www.ribbonfarm.com/2014/01/21/poor-usability-tell/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.