Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net
From: Anders Isaksson (anders.isaksson_at_REMOVEcej.se)
Date: 01/13/05
- Next message: El Lobo: "Re: Unicode VCL. Why has this been ignored?"
- Previous message: Eric Grange: "Re: How has, and how is Delphi being used? (Not a poll)"
- In reply to: Michael Anonymous: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Next in thread: Rudy Velthuis [TeamB]: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Reply: Rudy Velthuis [TeamB]: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Reply: Michael Anonymous: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Reply: Will DeWitt Jr.: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 13 Jan 2005 09:04:23 +0100
On Thu, 13 Jan 2005 00:10:41 -0700, Michael Anonymous
<Michael@Anonymous.net> wrote:
>All joking aside, what I hate about .NET is that it seeming
>strives to take away certain programming freedoms such as:
>
>+++ the ability to compile into native code without using a MS compiler
What's your problem with using an MS compiler (JITter)? Assuming it
creates correct, reasonably efficient native code, of course.
>+++ eliminate programming with pointers
>( I love pointers as much as I love html links! )
Pointers are just a tool to get the work done. No big deal learning and
using another tool.
>+++ eliminate dynamic memory management.
I don't think it does.
>+++ forcing me to use a garbage collector when I don't want to use one.
That one is easy: Don't produce any garbage :-)
But yes, the undeterministic way the GC runs may be a problem in some
applications. You probably shouldn't use .net for them (arguably, you
shouldn't use Windows at all for them).
>+++ GC has the great potential to be a performance hog.
Have you experienced this?
>+++ Microsoft's attempt to control all development on Windows.
Business sense.
>You have to use their tools, whether you like it or not, to create
>even the simplest applications.
No.
>+++ The ability to rationally consider other alternatives such as Win64.
But one point of .net is that *when* W64 comes, and the .net framework
gets 64 bits, your pure .net programs will also be run in 64 bits -
without you having to do anything about it!
-- Anders Isaksson, Sweden BlockCAD: http://w1.161.telia.com/~u16122508/proglego.htm Gallery: http://w1.161.telia.com/~u16122508/gallery/index.htm
- Next message: El Lobo: "Re: Unicode VCL. Why has this been ignored?"
- Previous message: Eric Grange: "Re: How has, and how is Delphi being used? (Not a poll)"
- In reply to: Michael Anonymous: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Next in thread: Rudy Velthuis [TeamB]: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Reply: Rudy Velthuis [TeamB]: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Reply: Michael Anonymous: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Reply: Will DeWitt Jr.: "Re: Separate releases: Delphi 10 Win32 / Delphi 10 .Net"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|