Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #1142 > unrolled thread

Direction

Back to article view | Back to comp.programming

Contents

  Direction Joe Wright <joewwright@comcast.net> - 2011-12-23 16:28 -0500
    Re: Direction "Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> - 2011-12-30 12:13 +0000
    Re: Direction Dann Corbit <dcorbit@connx.com> - 2011-12-30 12:31 -0800

#1142 — Direction

Is .NET the only way forward? I hope not. Where will developers go?

-- 
Joe Wright
"If you rob Peter to pay Paul you can depend on the support of Paul."

[toc] | [next] | [standalone]

#1155

Joe Wright wrote:
> Is .NET the only way forward? I hope not. Where will developers go?

At a guess, no.  To me, the OS/platform world is looking rather more diverse 
than it did, say, five years ago.

    -- chris 

[toc] | [prev] | [next] | [standalone]

#1163

In article <qZOdnQy6WLL_b2nTnZ2dnUVZ_hCdnZ2d@giganews.com>, 
joewwright@comcast.net says...
> 
> Is .NET the only way forward? I hope not. Where will developers go?

Forward to what?  It depends on what the goals of the project are and 
what the needs of the customer are.

The .Net framework is a nice GUI for developing windows front-end 
applications.  With MONO, you can do similar work on Unix, but many of 
the nice tool sets will be missing.  If the product also needs to run on 
Solaris and Linux clients, for instance, I would consider Java or some 
other alternatives.

Java is another nice GUI framework for developing portable front-end 
applications.  It covers a somewhat broader set of targets (IOW, I doubt 
if you could get MONO to run on something esoteric like MVS or OpenVMS).

It may be that the GUI has to be both fast and portable.  A nice option 
there is wxWidgets, which can make compiled C++ GUI applications for 
Mac, PC, and Unix targets.

There are other good, portable choices like TCL/TK.

We need to ask ourselves questions like:
"Who is going to maintain this application?"
"What resources does the customer have available?"
"What are all of the possible client architectures?"
"What are the skill sets of the programmers who are going to make the 
GUI?"
etc.

For me, .NET is just another tool (and a good one) for accomplishing a 
goal of producing software that meets the needs of the customers.  If a 
.NET application seems like the best solution, then that is what I would 
write.

I would not use .NET or Java for heavy lifting[*] -- use C++ or Fortran 
for that.

[*] Well, most of the time.  If you want to write to a HADOOP cluster, 
then Java makes sense and it can move a mountain.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.programming

csiph-web