Re: International Pricing Policy

.... would be a good idea to enhance the components too, they look (at
least partly) still like in Delphi 1.

Reasonable priced, concentrated on Win32 and a bit outstanding features
Delphi could survive without any problems. Even MS sees a future for
native programming and there will be always people looking exactly for
this.
There aren't really a lot important programs based on .NET around.

Michael


Farshad wrote:

"Fritz Huber"
I see the same thing happening to Delphi. The tool seems way
overpriced for what it delivers.


Very well said. Cut the prices and reach as much as developers as you
can. Paying several thousands of dollars for your developing tool is
a thing of past.



--

.

Relevant Pages

  • Re: 64-bit Windows for AMD 64 is here...
    ... Of course the VCL for NET is ... classes (or structs in Win32) around. ... although not as extreme as the Win32 API. ... Delphi is also very strong on native compilation. ...
    (borland.public.delphi.non-technical)
  • Re: Delphi 2005 Win32 development stopped
    ... improve Win32 development or make a significantly better product for the end-user. ... Delphi, they wouldn't even merit a foot-note in marketting. ... someone from Borland or TeamB mentions for-in loops. ... and inherit all the bugs. ...
    (borland.public.delphi.non-technical)
  • Re: Thinking Clearly
    ... a case where MS is sticking it to DevCo. ... The question I have is if it will support ... interop and the core win32 API are bedrock. ... Was Win32 "bedrock" when Delphi 2 was released? ...
    (borland.public.delphi.non-technical)
  • Re: Comparison about Win32 / DotNet / CSharp on Delphi, and a wish ...
    ... jobopenings vs the number of pure Win32 jobopenings. ... I don't care Delphi team develop .NET or C# stuff, but as a lot of Win32 ... delphi users, I've been so frustrated to see all the negative impact it ...
    (borland.public.delphi.non-technical)
  • need clarification
    ... Delphi is heading towards a .NET state. ... I *feel* the Win32 inclusion was to string the regular Win32 ... Since porting .NET code would be ... would .NET developers give up ...
    (borland.public.delphi.non-technical)