Re: About .NET strategy



Microsoft controls [now] their implementation of the C# programming
language. Of course, controlling the platform/OS (namely the libraries
and the ability to distribute them with the OS and in Auto Updates and
service packs, among other things) also gives them advantages other
compiler/IDE vendors can only dream of.

- Nate.

"Brett Watters" <blwatters@xxxxxxx> wrote in message
news:454ca54f@xxxxxxxxxxxxxxxxxxxxxxxxx
Fritz,

Wouldn't it be better to focus on C# Builder instead of putting all those
resources into building a Delphi for .NET compiler?

No.

What are the advantages of using Delphi.NET over C# for new projcects?

First, C# isn't the biggest programming language for .NET. VB.NET is.
There are more VB programmers than C programmers. You might use
C# for "high-end" projects, but honestly there are more folks self-taught,
coming out of trade schools, etc. than folks with formal C training out of
universities. Folks coming from Access, Word, Excel, etc. migrated into
the VB world.

For many years, use of C was greatly restricted within organizations. It
was certainly more powerful than VB, but that came at a cost in terms
of numbers and quality of programmers, QA and project management,
etc. which many departments simply couldn't justify to simple projects.

In any case, today, C# requires a level of knowledge and software
engineering practices which most organizations/departments just aren't
there with.

Second, there is a pool of folks which Borland has which Microsoft
doesn't. Millions of folks who where educated in Pascal. This is a much
easier market to gain and hold. It is one where Borland has a clear edge.
If Borland focuses on C#, then it looses this base and it then needs to
convince folks why they should use their C# rather than Microsofts.

Better to be a little fish in your own little pond, than be a little fish
on
a big pond with a really big fish.

Third, it gets to control the Delphi language. This is key. One of the
main reasons C is so hard, was because for years there were different
versions of it. There were dozens of other vendors. C++ looked like
a dog's breakfast and was slow coming. Unlike objects in Borland Pascal
which went in easy. Why? Because Borland control the Pascal standard.
It didn't need to worry about what others were doing because there were
no others. Same with Microsoft and Visual Basic.

Today, Microsoft controls C#. Like .NET itself, they can change the
golden standards, add features, modify the language itself, etc. to make
it
easier for them. We do know that most of the features in .NET are designed
to solve issues for Microsoft. Component sharing, single .EXE, no more
Active-Xs, etc. All these were non-starter issues for Delphi folks to
begin
with.








.



Relevant Pages

  • Re: When will MS Stop supporting VB?
    ... so it is doubtfull that VB.NET will ever be dropped. ... > language in DotNet if they all use the same CLR? ... "With Visual Studio 2005 it seems clear that Microsoft has ... procedural programmers than anything related to OOP.... ...
    (microsoft.public.vb.general.discussion)
  • Re: Disappointment in VC++ .Net in VS2008
    ... if that is what they felt was the way to support .Net. ... C++/CLI is not C+, it is Microsoft's own extension purely to accomodate .Net, and they can change the language at will to acoomodate new .Net features as they like. ... I argued that C++/CLI ..Net programmers have been totally let down by the VC++ team, and even that this was Microsoft's plan from the beginning. ... We both know that Microsoft has enough resources to do this, ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Disappointment in VC++ .Net in VS2008
    ... language to accomodate new .Net features, if that is what they felt was ... front end to support a better Intellisense, ... C++/CLI programmers. ... We both know that Microsoft has ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Visual Basic to be discontinued in 2008??
    ... Robin S. ... thousands of VB.Net programmers around the world don't agree ... All people see is the language and abuse, ... point them in the right directon (away from Microsoft Visual Basic - ...
    (microsoft.public.dotnet.languages.vb)
  • Any .Net controls youd recommend?
    ... I miss having a large library of cool controls that make RAD programming as ... Microsoft really screwed up with VB.Net in the first 2 iterations. ... They abandoned millions of part-time programmers and destroyed a lucrative ... I don't think they'll ever regain the status they once held ...
    (microsoft.public.dotnet.general)