Re: New Delphi roadmap is coming: NO UNICODE PLEASE!



In article <45b95888$1@xxxxxxxxxxxxxxxxxxxxxx>, says...

I'm the project manager of a .NET desktop application at our company.
As a result, I'm confirmed in my disinterest in .NET *desktop* applications.
AFAICS, no one has demonstrated a need for .NET desktop applications,
let alone Delphi.NET desktop apps. More than ever, I think native is the
way to go.

This is very relevant to me right now.

When you say you are disinterested in .NET on the desktop (to paraphrase
slightly) does this mean you are actively *not* interested in .net on
the desktop or that .net on the desktop is of no great benefit from your
pov, but neither is it any great concern?

i.e. do you see concrete _dis_advantages of choosing .NET for the
desktop, or merely not perceive any real _ad_vantage?

This isn't intended to trigger a flame war.

I am actively looking at the task of migrating a significant 32-bit
Delphi codebase to 64-bit.

Currently of course there is no way to do this natively and to stay with
Delphi and for numerous reasons Delphi.NET is not #1 on the list of
candidates for a .NET targetted approach.

If there are concrete disadvantages to using .NET on the desktop from
your pov, this could be a factor in any eventual decision to wait for
64-bit Delphi or not.


I want the best of both worlds. To be able to use Win32/64 when it
makes sense, including GUI, and the features that .NET provides when
that makes sense, in the same app.

"Me too"

Trouble is, I may _need_ it _now_, not "sometime in 2008", as it stands
in the current roadmap (as featured in The Delphi Hour video)

Assurances to key decision makers that it will be worth waiting for 64-
bit Delphi is not helped by the fact that 64-bt Delphi was originally
signposted on at least one Borland roadmap for 200_7_

We can't wait for 2008 only to find that by then it's slipped further
into 2009


(This is why roadmaps need to be something that can be committed to by
both publisher and audience - and please note that this isn't a
contrived example, nor a particular happy one for me)

--
Jolyon Smith
Say, do any of you guys know how to Madison?
.



Relevant Pages

  • Re: Dannys Corporate Roadmap
    ... In the Delphi camp, the roadmap has been shown and discussed in nearly ... radical change from the norm for compiler tools of the day. ... The core development tools are the entry points to creating that ...
    (borland.public.delphi.non-technical)
  • Re: Stop the negativism!
    ... It's also clear that up until now, there were no plans on the roadmap ... in either some posts here by Borland/DevCo or the Delphi hours. ... We do not know the reasons behind this. ... Please keep in mind what the situation must have been like at Borland ...
    (borland.public.delphi.non-technical)
  • Re: The alternative Delphi roadmap to success
    ... Market analysis ... I'll focus on the existing customers first. ... Delphi Win32 48% ... If we filter out all answers not related to the roadmap, IOW sales, ...
    (borland.public.delphi.non-technical)
  • Re: The alternative Delphi roadmap to success
    ... Market analysis ... I'll focus on the existing customers first. ... Delphi Win32 48% ... If we filter out all answers not related to the roadmap, IOW sales, ...
    (borland.public.delphi.non-technical)
  • Re: The alternative Delphi roadmap to success
    ... Market analysis ... I'll focus on the existing customers first. ... Delphi Win32 48% ... If we filter out all answers not related to the roadmap, IOW sales, ...
    (borland.public.delphi.non-technical)