David / All.
Thats not accurate. Ubiquity stats are a developer's placebo, as in the end
we noticed at trend in around this argument when it came to Silverlight.
Initially when we had ~10% ubiquity world wide Flash having 98% etc it was
an extremely tough battle and what got us over the line
oh example point and case:
Adobe Flash has 98% ubiquity right? ok.. here's a math puzzle for you..
Flash on average has around 8million installs per day (365 days a year) and
can spike up to 33million depending on release / campaigns in market. There
are currently approx 1.6billion - 2billion
Just to add my 2c, it's not necessarily an or choice. You could build 90% of
the app as a web app (which for webby-things, will be much faster -
Silverlight/XAML has nothing on Razor/MVC/HTML/CSS). Then if you hit something
that's difficult to do in pure HTML/JS, build that 10% in Silverlight.
To: ozDotNet
Cc: James Chapman-Smith
Subject: Re: HTML vs Silverlight - comparative effort?
On Tue, Mar 29, 2011 at 12:31 PM, James Chapman-Smith
ja...@chapman-smith.commailto:ja...@chapman-smith.com wrote:
If I'm going to develop a new web-based application in HTML or Silverlight,
what would
On Tue, Mar 29, 2011 at 12:48 PM, James Chapman-Smith
ja...@chapman-smith.com wrote:
Good point, I didn't mention the target market. We're doing a corporate
app. It'll be deployed on a server within the companies. We're only
expecting PC possible Mac clients.
If you're doing a corporate
My general rule of thumb is:
*Public facing* - technology choice defaults to ASP.Net MVC
*Internal Line of Business app* - depends on how interactive you want it to
be. I usually default to Silverlight because of the ease of doing
animations, visual bling, etc.
-David Burela
On 29 March 2011