Re: Wild speculations about the "other" factors

IanH wrote:

I think that Simon's description of D2005 as focused primarily on .NET
is entirely fair and accurate.

I'm selectively quoting the features that I believe show the "focus" was not on .NET. I'm pretty sure the features I do not quote /are/ .NET exclusive.

- "support for 3 personalities in 1 IDE" (2 of which were .NET related)

The simple fact that Delphi/Win32 was supported means to me that it was not a .NET focused release. In my opinion, if D2005 was .NET focused, the Win32 personality would not have been there. But we'll have to agree to disagree on that one.

- "support for Unit Namespaces, for..in..do loops, inline functions"
(not sure about inline functions, but the first 2 were driven by .NET)

Driven by .NET, sure. But "focused" on .NET would imply, to me, that those features are not available in Win32. I don't know how unit namespaces changed for Win32, because I use "SysUtils.FindFile" syntax in D6 all the time. But for..in..do and inline functions ARE available for Win32. (Yes, inline functions was driven by .NET. But, again, the compiler team decided to support them in Win32 also, which was not required.)

(ie the future of data access is all through .NET)

I disagree, although I don't know how this comment is even relevant. By supporting data access through all .NET components, not just BDP, Borland provided user's with more choices. Borland has always been about providing choices and multiple ways to accomplish the same thing. Something other vendors do not spend much time on.

- "Support for refactoring"

Available for Win32. IMHO, focusing on .NET would have meant I had no refactoring in Win32.

- "Support for unit testing with DUnit and NUnit"

Available for Win32. IMHO, focusing on .NET would have meant I had no DUnit support in Win32.

IMO, D2006 was certainly more balanced a release than D2005, but the
lack of progress on fundamental Win32 development issues - Win64,

Funny, I don't consider Win64 to be a Win32 development issue. It's a new hardware and OS platform, not a Win32 issue.

Given all this, I think your characterisation of Simon's POV as FUD is
unfounded and unfair. It is at least a topic worth discussing, not
simply dismissing.

The topic of what we'd like to see in a future version of Delphi is definitely worth discussing, and I look forward to more of this discussion.

Charactarizing D2005 and D2006 as .NET focused is unfounded and unfair. I imagine it took SIGNIFICANT work to add the two Win32 personalities to the products.

Available for Win32. IMHO, focusing on .NET would have meant I had no refactoring in Win32.

If I could not be productive doing Win32 development in BDS 2006, then I would characterize the last three releases as .NET focused. That's just not the case for myself and MANY other BDS 2006 users.
.

Relevant Pages

  • Re: Win32 Changes Spacely -> Highlander
    ... I simply wanted clarification on how new features and updates will work when individual personalities each get multiple product updates a year now. ... I've always only used the pro level, Win32 features of Delphi and BDS, and I'm happy to get back to that sort of product. ...
    (borland.public.delphi.non-technical)
  • Re: The New Roadmap
    ... I think it's because Highlander focuses on .NET and will be the first ... spent considerable time on native Win32, when the two most recent releases ... They can NEVER get enough - or the right - updates and new features in any ... and it seems to me the majority of Delphi purchasers' desires -- is ...
    (borland.public.delphi.non-technical)
  • Re: Wild speculations about the "other" factors
    ... This doesn't mean that Win32 is left out, ... C/C++ language support, Code Insight, Code Completion, Code Templates, refactoring, support for operator overloading syntax in Win32, and support for inlining compiler magic functions such as Length, optimized routines from the FastCode project, a new high performance non-blocking multithreaded memory manager, SyncEdit, History Manager, Code/Error Insight improvements, Live Code Templates, Smart Block Completion, the first phase of Unicode support appears in BDS 2006, the phased approach to Unicode will continue in Highlander and through the subsequent Vista release, with enhancements to both the IDE and VCL runtimes to support Unicode. ... there are MANY new features of the IDE that were NOT implmenented "for .NET" and make Win32 development MUCH more productive for me. ... excellent Win32 development tool I have today with BDS 2006 ...
    (borland.public.delphi.non-technical)
  • Re: Win32 or .NET poll
    ... > User groups (especially Delphi user groups) are not likely to be the ... There is a ton of new Win32 stuff in Diamondback. ... > Win32 features in my BorCon talks. ... Diamondback is a significant release for Win32 as well. ...
    (borland.public.delphi.non-technical)
  • Re: native-code languages (slashdot) and Borland rant
    ... heard about getting new native Win32 language features like Generics, ... New Win32 features in the last couple versions. ... Strict private, strict protected ...
    (borland.public.delphi.non-technical)