Microsoft re-explains .Net strategy

TalkBack 5 of 40:

Next »

« Previous

• Thread View
• Flat View

Re-complexifying the client.

Here's my two sense.. If you take my advice, I charge about a dozen donuts a day, plus expenses..

My current idiocy aside, I'd have to ask, what's wrong with complexifying the client? As desktop computers, irregardless of style (SUN, Apple, PC-based, whatever), they run *extremely* fast, much better than 3 or 4 years ago, when Thin-client was the buzz-word. It was great then.. You don't want to spend a fortune on expensive PCs for everyone, so you considate everything on servers. Web-based clients minimize local installation issues, so it's all well an good, right?

Well, it has problems. One, The computers now adays aren't nearly as tasked as used to be, even with bloatware. They *can* run more powerful apps. The more stuff you can run localy, the quicker the experience will be for the user, which is good for productivity. This alos greatly reduces the Bandwidth necessary for traditional Client-Server technologies. And your servers, now having distributed the some of the work load to clients, are more free to handle more clients, rather than performing a lot of calculations on their own. If cost of computers are a concern, on the client level, remember, many computers are replaced every five years or so. Computers are like the Church Carpet, not the Church Organ, and should be budgeted to be replaced every so often. (See Note Below)

There is one big issue here, with most IT companies. That's one of Deployment. I can say, first hand, that .NET and it's Winform clients being launched from the Web, make this *a BREEZE*. Almost as easy as Java Deployment, IMHO. Also, you don't have to worry about mish-mash of which VM is running on each machine, if someone downloaded a different VM, etc. .NET handles all of that natively and won't allow you (provided you check for it in code) to run a program on the wrong framework.. (There's only two anyway, at this time..)

My suggestion to you, seriously, is get a consultant who specializes in .NET. And have them layout the benefits vs. Risks for your company, in writing. And do the same with your other consultants. Then make a logical, and appropriate choice for your company. Don't write off .NET because of Balmer.. Those people are good for singing praises of their own software..

I would say that if your company plans of keeping the same computers around indefinately, Thin Client might be the way to go for you, but I'm unaware of companies who do this, hence the Church Organ analogy.

Good Luck. This might have been my most serious post to date. Maybe it's worth a donut or two.

-DB in 2004

Posted by: Delaware Boy   Posted on: 11/20/03 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• Open Standards Technologies Provide the Ingredients for Delivering Security Across the Papa Gino's Enterprise Dell Papa Gino's Holdings Corporation founded by the entrepreneur operates one ... Download Now
• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now