Re: I really hate .NET especially inside Delphi

Nick Hodges (Borland/DTG) wrote:
To each his own, I guess.

Exactly.

IMO, that's exactly the problem with the way Delphi for .NET does
namespaces. It doesn't give the developer any choice because something
that should be logical is coupled to the physical.

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: Codegear sold
    ... Doesn't really sound good, IMO. ... We will continue to move our developer products, especially Delphi, forward. ...
    (borland.public.delphi.non-technical)
  • Re: I really hate .NET especially inside Delphi
    ... that's exactly the problem with the way Delphi for .NET does ... namespaces. ... It doesn't give the developer any choice because ... logic without having some physical mapping? ...
    (borland.public.delphi.non-technical)
  • Re: Custom Software Development
    ... IMO, this is the wrong group for this type of post (should be Jobs) and ... there is absolutely no mention of Delphi in this entire post, ... developer status. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Thinking Clearly
    ... I inferred it from "But IMO, there is no tangible benefit to moving Delphi ... Win32 code forward to .NET. ... Sometimes good theories don't pan out, particularly when normal market ...
    (borland.public.delphi.non-technical)
  • Re: Not Another C# Versus VB Article (It has a lot to say about Anders and Delphi)
    ... VB supports optional parameters. ... It's as useful as 'using' in C# because it provides a shortcut to existing functionality of the .NET Framework. ... C# namespaces are managed in way that makes programmers aware ... An unprofessional developer will write bad code in both C# and VB.NET, a good deveöoper will be able to write good code in both programming languages. ...
    (microsoft.public.dotnet.languages.vb)