Re: 64-bit - the desaster continues ...


"Rudy Velthuis [TeamB]" <velthuis@xxxxxxxxx> wrote
>> > I can't check this myself, but I really wonder how many customers
>> > actually care about
>> > - replacing their existing hardware with new hardware, unless their
>> > old hardware is really not up to the task anymore;
>> > - whether their OS is 32 bit or 64 bit;
>> > - what colour their database has (mauve?);
>> > - whether the programs they have been using for years, and run well,
>> > use 16 bits, 32 bits, 64 bits or even 27 bits,
>> > as long as their apps do what they are supposed to do, and do it well.
>>
>> Rudy, just try to think out of the box. Think big corporate IT, think
>> large customers.
>
>> If Microsoft releases Excel Server in October 2006, where are you going
>> to deploy this? Of course on 64-bit.
>
> If you are going to replace the existing one at all. I guess changing
> hardware and software is also an administrative risk.

Rudy, MS Excel Server is a new app from Microsoft to be released in 2006.
While MS Excel traditionally was a desktop app, Excel-Server is going to be
a server app delivering the typical Excel-functionality to the client, but
with server side security, multi-user functionality etc. You can bet that
when it is released at the end of 2006, most deployments will be on 64-bit
then.

>> If you think about trading room environments, I usually see high-end
>> state of the art win32-workstations quite often already running
>> dualproc-machines there. Banks don´t care about the costs in their
>> trading rooms that much, a trader typically has up to 4 LCD-displays
>> sitting in front of him. How long do you think it is going to take
>> until they replace some of these machines with Win64? They don´t need
>> to replace all of these machines, but just lets assume they upgrade
>> just 10% of these machines during the next 2 years. What happens if our
>> software doesn´t run natively on Win64, but a competitors one does?
>
> Must it run natively, then? I have no idea what your software does, or
> how it connects to other software running.
>
Yep, must run natively. If you want to compete with other vendors that are
using highly optimizing C++-compilers from Intel, you are already in a
difficult position when you are working with a Delphi native code compiler.
If you then use .NET instead, you are finally just out of the game.

> I can see that there are situations where you are slashed if you can't
> provide a 64 bit version, but that doesn't take away that from Borland's
> POV, this number of people (and the expected number of people) may
> currently still be too low to make it viable for them to start working on
> it already.

Assuming that it might take a year for Borland to come up with DCC64, a
64-bit debugger and a 64-bit VCL, once they have started, they should
probably start soon, if they ever want to come up with a 64-bit native
compiler. Please don´t forget, they don´t intend to start before Highlander
has shipped, and then it will take at least a year (meaning end of 2007 at
earliest). And they haven´t even made a decision if they want to do it all.
Sigh.

Don´t you think it will matter to most Delphi customers by 2007? Didn´t you
get the message that Borland didn´t even start yet, that they won´t start
until after Highlander?

How do you want to offer 64-bit native apps by 2007 then? Don´t you think
most Delphi customers will need it by then?

-Peter


.

Relevant Pages

  • Re: Function name not found
    ... are casual canned-software-only customers? ... I have an app that has just ... certain Reference changes from version to version in MDBs, ... Looking at you Startup function, the first thing I see is a DFirst ...
    (microsoft.public.access.modulesdaovba)
  • Re: VS2003 and WM5.0 Devices
    ... The problem I have is that a customer who has a JasJar has reported that my installer will not install my app at all. ... I still have some customers who have the ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Securing a .NET webapp with ActiveDir and SQL-server?
    ... Or is this done in a separate app? ... I need some SSL in the mix also. ... Each Employee deals with Customers in one or more Regions. ...
    (microsoft.public.dotnet.security)
  • Re: Distributing application to customers?
    ... I assume your application is a Windows Forms app. ... If your customers expect to connect to you over the open ... I'd advise against connecting to SQL Server over the internet. ... that won't mind being trained on the intricacies of Terminal Services (e.g. ...
    (microsoft.public.dotnet.general)
  • Re: 64-bit - the desaster continues ...
    ... MS Excel Server is a new app from Microsoft to be released in ... While MS Excel traditionally was a desktop app, ... > going to be a server app delivering the typical Excel-functionality to ... I don't decide that, Borland do. ...
    (borland.public.delphi.non-technical)