Oh I don't know. Browsers need patching, upgrading, etc. Depending upon circumstances, some browsers actually have to be installed because the OS supplier only supplies their own.
Which has the most moving parts? A browser or an alternative? It will be interesting to see the outcome.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Monday, June 08, 2015 2:30 PM
To: Midrange Systems Technical Discussion
Subject: Re: 'green screen' not sellable
On Mon, Jun 8, 2015 at 3:44 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx> wrote:
In my experience browsers also take some care and feeding. Personally, I categorize web browsers as thick clients (just look at the size of one's folder) with all the issues of any other thick client.
Modern Web browsers are extremely thick, that's true, but they don't have the same issues as "any other thick client".
First, most devices that could conceivably run your application already have a Web browser installed. That in itself is a huge advantage for deployment.
Second, Web browsers are relatively independent of the underlying hardware or operating system. Even differences between browsers are often handled fairly well by modern advanced frameworks. (Not perfect by any means, but usually not as bad as handling the differences between Windows, Linux, OS X, Android, and iOS.) In broad strokes, it could be argued that Java thick clients are similarly cross-platform.
.NET applications are less cross-platform, and native binary apps are of course not cross-platform at all.
These two are pretty big points in favor of developing for the browser. Scott also mentioned that browsers tend to have less access to the local system, which could be an advantage. I think other thick clients are not without their own advantages as well, but I would not lump them in with browser-based apps.
John Y.
--
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.
midrange.com
