Delphi for Obsolete.NET

Delphi has always lagged behind Microsoft platform releases. Some lag is to be expected, but with .NET, this has become terminally worse. The first Delphi to actually support .NET 1 development, rather than hinder it, was D2006, released after .NET 2. Highlander for .NET 2 is not slated for release until after .NET 3. How can Delphi be considered a serious contender for .NET development, when it only supports a platform once it becomes obsolete?
.

Relevant Pages

  • Re: Thinking Clearly
    ... But if it's not VCL.NET alone shouldering the burden, ... BDP.NET and Delphi for .NET itself. ... advantage for code migration. ... not knowing that BDS supports .NET development at all, ...
    (borland.public.delphi.non-technical)
  • Re: Function Inlining (and other compiler enhancements)
    ... There are quite a few people who happily use D8 for .NET development. ... I'd not be willing to call D8 a 'disaster' ... ... > 64-bit compilation. ... I'm a fan of Delphi, ...
    (borland.public.delphi.non-technical)
  • Re: Why arent you upgrading?
    ... with BDS for .NET development. ... doing a "me too" .NET development tool is worthless. ... Not to mention the Delphi myopia that drives DevCo only to see how to ... Ruby or Python since they have their own culture and philosophy. ...
    (borland.public.delphi.non-technical)
  • Re: .NET 3.0 created by the stroke of a pen
    ... I don't know anyone doing .Net development of any type at our users group. ... So yes a lot of them are doing native with Delphi and web with ASP.Net and VS. ... I am assuming that is true for all 20 of our regulars to our Programmers Users Group. ... BSS Enterprise Accounting FrameWork ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... and how many are using Delphi for .NET development? ... think DevCo should focus on making .NET better, ... years to get CF designers and debugging support and hasn't been able to, ...
    (borland.public.delphi.non-technical)