Re: why?
- From: Devan <Devan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 8 Jun 2006 11:18:01 -0700
These numbers are important when talking to the taller upper management. You
are an engineer or someone with a computer science degree that has years of
experience, understanding what code is or isnt. Whereas, most of these guys,
hold an undergraduate degree in history and get into Investment Banking
because of their height. Talking about merits or demerits of Java vs .NET at
a very advanced level will either put them to sleep or make the Java team,
which talks at a even basic level as in length or size of code, only more
successful.
These CEOs, CFOs can easily relate to physical labor, size of the Framework
than to nerdier arguements as usability, ulility, ease of use, etc.
So, understanding my position, as you have been in one, or currently are in
one, an MVP, as you, must be quick at helping me out, as you know, quite well
that us, computer programmers have a different mindset than them.
Devan
"Nicholas Paldino [.NET/C# MVP]" wrote:
I'm curious as to what the number of people and development time have to.
do with making this decision. After all, those people aren't the ones that
are doing anything, the finished product is.
As for saying "stabler Solaris", I think that is a debatable point.
Why not give what your project is going to consist of, and we can tell
you the pros and cons of using .NET for that project?
After all, that's what matters in the end. With all due respect, I feel
the metrics that you are trying to base this on should have no effect on
this decision. A framework could have one million methods vs another
framework with .5 million methods, but that doesn't mean it's better. You
have to take a look at what the framework offers for what you are doing, and
make the decision based on that.
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx
"Devan" <Devan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF516579-EFCF-4748-A062-13F757643B12@xxxxxxxxxxxxxxxx
Does anyone at Microsoft know the number of classes, namespaces and
functions
in .NET? Microsoft must have spent a lot of time in development. Do the
same
people know how many employees, departments, and time, it took for them to
get here?
I work for a financial firm that is going to start a new project on .NET
or
Java. They are looking for a solid arguement with a few numbers. Java is
currently preferred as it is Unix-based and runs on stabler Solaris.
Microsoft Windows XP server and .NET line of products are to be considered
as
competing solutions. If a microsoft employee or even an MVP, can give a
few
answers, with brag rights, detailing the .NET solution with numbers, years
of
labor, etc, it would be a strong reason to go for Microsoft.
Messages from other posters also appreciated!
- Follow-Ups:
- References:
- Re: why?
- From: Nicholas Paldino [.NET/C# MVP]
- Re: why?
- Prev by Date: Re: how to throw Ballon Tip in C#
- Next by Date: Re: why?
- Previous by thread: Re: why?
- Next by thread: Re: why?
- Index(es):
Relevant Pages
|
