Re: Did Borland doing well in Q4? Listen to the Earning CC



In article <47ca939f$1@xxxxxxxxxxxxxxxxxxxxxx>, marius@xxxxxxxxxx
says...

If unicode is a big deal for them they will go asap. If not, they will
postpone indefinitely.

We do not have any use for unicode (yet), so with that in mind you are
completely right. However there are also win32/generics on the roadmap
and for the first time since delphi7 i find that interesting enough (at
least that does it for me personally).

So to get generics you have to go through ANSIfying your projects to
ensure correct continued behaviour in Tiburon. And of course generics
won't benefit any existing code so you don't get any productivity gains
from those unless and until you've invested some up front dead-time
there either.

That's an awful lot of running just to stand still.



We DO need Unicode, but this Big Bang is going to be a major headache
and is enough - on top of a lot of other things - to put a big question
mark over whether or not to even continue with Delphi.

Are we going to have to go through the same rigmarole with the 64-bit
release too?

We've been through this once already with the BDE.

For all that Borland/Inprise/CodeGear make of the overall backwards
compatability maintained in the Delphi versions over the years, these
sorts of *major* upheavals for zero attendant reward can get to be a bit
too much.



Another thing that would be very interesting is the multi-core and
multi-threaded development. It is disapointing far away at the end of
the current roadmap (which needs updating :P)

Implement an Active Object framework and move on. Why do we always have
to have new libraries and frameworks handed to us on a plate?

It's just code, and didn't we get in this game because we enjoy coding?

:)

.



Relevant Pages

  • Re: Did Borland doing well in Q4? Listen to the Earning CC
    ... IMPLEMENTATION of Unicode. ... i.e. string -> long string ... remained supported alongside Delphi 2.0, ... If you want to support Unicode and begin the process of implementing ...
    (borland.public.delphi.non-technical)
  • Re: IDE Nightmare - Unicode or Ansi is DFM?
    ... Borland Delphi 6 product certified ... > Pro on Russian, IDE save Unicode strings to all TString ...
    (borland.public.delphi.non-technical)
  • Re: Unicode in Delphi/VCL (yet again)
    ... Let me introduce you to a few million VB developers. ... That's not to say there isn't a good way to accomplish UNICODE in Delphi. ... > BSS Enterprise Accounting FrameWork ...
    (borland.public.delphi.non-technical)
  • TNT/TMS Unicode, Delphi 2007 und Interbase 2007
    ... In der Version der TMS Unicode Komponenten ist kein Beispiel enthalten, und ich habe bereits beim Zugriff aus Delphi 2007 auf Interbase 2007 mit dbExpress ein Problem mit dem WideString Feldtyp - siehe mein Newsgroupposting vom 29. April unten. ...
    (de.comp.lang.delphi.datenbanken)
  • Re: Unicode Delphi Win32 - which approach
    ... UTF-8 encoding is different from ANSI,... ... The first 256 Unicode characters map to the ANSI character set. ... Delphi supports UCS-2 on both platforms. ...
    (borland.public.delphi.non-technical)