Nick Hodges (CodeGear) wrote:
(snip)

yes I agree that these enhancments has real benefit, but you have to
admit that these are only cosmetic improvements, no REAL architectural
advantages, VCL has remained the same as it was in D7.

Irakli wrote:
  (snip)
Not true.
  VCL now has:
  Margins
  Padding

(snip)
Why bother, DevEx has everything and more and works with every
    version of Delphi? I mean it's nice that you add these little
    components, but rather you would do something about the whole
    db-awarenes craziness that's been there since D1 and also about
    all DataSet infrastructure. Does anyone on VCL team know the

Michael Baytalsky wrote:
      (snip)

Well you don't want to kill of the market for 3rd party components.
      The major thing the VCL needs is unicode. I personally think this one
      enhancement would get a number of companies upgrading to the latest
      version. Just think if all of those cool DevExpress/TMS (insert 3rd

(snip)
Sure, this is why I don't think Borland needs to add all those components
        at all. There simply must be a strategy on how to work with 3rd party
        vendors to make sure that components are available and that there's
        competition between vendors and everybody is happy ;).
        (snip)
I'm not really sure. Why would you really need unicode, unless you are in China?

Well the component vendors are starting to drop Delphi in favor
        of .NET, so in a year or two they will be able to release all the
        controls they want without having to worry about 3rd party vendors.
        Overstatement, of course, but you get my point.
        - Nate.

(snip)

Borland also wasn't going about it smartly. Barring few significant
          problems,
          ..NET is highly backward comparible in that you can, in most situations,
          utilize a .NET 1.0/1.1 assembly in a .NET 2.0 applications. Knowing
          this, they should have gone ahead and delivered a C# 2.0 development