Re: C/C++ is dying... :-)

Hi Paul,
We've just spend about 6 months reviewing available applications for
alumni/development systems in universities. We looked at all the major
players, including the big ERP solutions. Just about all of them included
both a web module and a traditional client/server module. The client/server
component was usually used by the heavy duty data entry folks while the web
modules were mostly likely to be used by folks on the road (development
officers visiting donors) or those who required only occasional or light
weight access to the data.

For our own, in-house applications, we still very much prefer the
traditional fat client, particularly for applications that need to automate
Office or otherwise interoperate with the desktop. Distribution is painless
since we started using TMS WebUpdate (and really wasn't much of a problem
before) which performs just as well as Java Jumpstart. I don't think
traditional client/server or the fat client (which can also be a Java
application for that matter) are dead by any stretch of the imagination.

We hope to start a major development project later this summer, aimed at
replacing an aging mainframe system. I can just about guarantee it will
have a traditional fat client for the main data entry users and web
components for travelers and remote users (though, to tell you the truth,
VPN and webupdate capabilities have made a server-side application even less
attractive since you just have to give up too much functionality).

I just hope the current Delphi uncertainty is resolved by then and the IDE
is happy in a new home so it can be a serious contender for our development
tool.

Ray Porter

"Paul Nichols (TeamB)" <paul@xxxxxxxx> wrote in message
news:43f8aaeb@xxxxxxxxxxxxxxxxxxxxxxxxx
Ender wrote:

Hello, Paul!
You wrote on Sun, 12 Feb 2006 20:31:13 -0500:



Didn't know that also. Almost every enterprise scale application i saw
is
client-server based.

Well I work in one of the largest industries in the US and possibly in the
world, Health Care. No applications we build are Client/Server based, all
are Web based.

Most of the third party products we buy are Web based as well.

With over 50,000 users I doubt VERY SERIOUSLY that anyone wants to think
about distributing 50-100,000 computers with periodic updates. You simply
cannot say all of your applications are not going to require bug fixes and
updates.

Ours is definitely not the only one either. All of the conferences I
attend,
where we meet with other large Enterprise companies, are all going to Web
Based business applications. The delivery models are Intranet, Internet,
and Extranet. None of them are talking about the great Fat Client market.
In fact they are not even planning to do any new development with the
traditional Windows based GUI client, for 90% of their new development
strategies. The Browser based application is where they are heading. The
Ajax programming model, is buzzing however.



Just build good deployment system. We have about 1000 workstations for
updating every week and there is no problems. When things become about
cipher-crunching having 1000 of PIVs with good distributed system like
nirvana.

Which still depends upon user interaction and depends upon each client's
network connection working and all machines up and running. Sorry, there
is
no comparison to a server based model, where the only thing that needs to
be running is the server(s).


In Russia almost all business apps are client-server.

You may be very correct in this. As stated earlier (in my correction), I
am
speaking of US market here. We do have some overseas facilities as well,
but not enough to speak of markets abroad.





.

Relevant Pages

  • Re: What doesnt lend itself to OO?
    ... >>essentially exposing the client or service implementation. ... COM-like composition is a fine paradigm for creating very general ... Similarly, client applications can access ... a solution based on that paradigm without their construction being based ...
    (comp.object)
  • Re: Active Directory/HIPPA Question
    ... The client ... > roll out AD when their top priority this year is securing the applications ... Security is one of the biggest reasons. ... ESPECIALLY if you have 800 remote offices. ...
    (microsoft.public.win2000.general)
  • Re: Looking for an Application Launcher in W2K3 SBS
    ... >> can manage 1000 of things regarding to applications and shortcuts... ... >>> Thank you for posting to the SBS Newsgroup. ... >>> I understand that you want to know how to deploy applications to client ... >>> the client and to launch the application installer from the client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Software Development - Who owns the creative/resale rights?
    ... >I have developed a few software applications for a client in Visual ... Also, solicitors are expensive, you'll be lucky to find one that ... know of one case where the lead programmer of a software house left to ...
    (microsoft.public.vb.general.discussion)