Hi Joe (long time no hear)
but I won't convince NETizens of that, so we can drop the thick client
discussion here.
I Should point out I am not, and never have been, a thick client fan (my
interest has always been in Client Server, e.g. ASP.NET)
Maybe at least we agree on something ;-)
Regards
Maurice
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Joe Pluta
Sent: 09 October 2010 20:04
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Microsoft .NET frontending IBM i
Hi Maurice! Nice to be though of <smile>.
.NET has all the same issues I've always objected to: Microsoft lock-in,
bloated code and non-standard implementation (a Microsoft specialty -
J++ anyone?). It's as poor a decision as it has always been, perhaps a
little poorer with things like Silverlight.
The good news is that it doesn't matter as much anymore. With rich web
interfaces, the PC is no longer the primary interface, that position has
been taken by the browser, and that thankfully is not under Microsoft's
monopoly.
Those few applications that really require thick client technology can
be written for whatever platform your corporation standardizes on.
Windows still sits on lots of corporate desktops and for that small
niche - thick client applications on Windows desktops - .NET is a fine
fit. Of course, Java is a better fit and RCP in particular a better
application development and delivery environment, but I won't convince
.NETizens of that, so we can drop the thick client discussion here.
And let's be serious here. Arguing about thick client applications is
like arguing about what makes the better leftovers: meatloaf or mac n
cheese. Thick client technology on the desktop is pretty old school.
Rich UI in the browser is the new desktop, and even that is pretty
/passé/. The real new vista (no pun intended!) is the mobile device.
And for that, you're either doing iPhone or Android. Microsoft missed
the boat so badly in this market that it may simply never recover. Not
surprisingly Java is the preferred platform (although I know the iPhone
folks would disagree, but really, how many people program in Objective C
that aren't programming for Apple?).
Anyway, .NET is the exact same option it has always been: a proprietary
niche platform with a limited scope. But hey, at least it's not PHP
<smile>.
Joe
Personally it's very nice to see .NET discussed openly in this group as an
option for web enabling the I
That wasn't always the case! ( hello Joe )
As others have said use the best tool for the job in hand be it a mixture
of languages, hardware, OS, skills etc etc...
Kind Regards
Maurice O'Prey
XMLi5 Ltd
midrange.com
