Re: 64-bit Windows for AMD 64 is here...
From: aLBi (why_do_we_at_need.this)
Date: 03/14/04
- Next message: Yorai Aminov (TeamB): "Re: Delphi 8 and Win32 update details"
- Previous message: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- In reply to: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- Next in thread: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- Reply: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 14 Mar 2004 22:05:01 +0000
>Do you mean yours, or Borland? I saw that you favour Whidbey.
I am not favouring Whidbey at all. Can't you see, I'm favouring Microsoft
here. I'm praising its commitment to its customers. Visual Basic has
always been a powerless environment, except for bussiness (that is:
database) applications where the developer could use third party speedy
tools and create a fast application. So Visual Basic .NET was just a
logical update. Indeed, the opposition to the redesigned VB .NET has been
so little and has faded so soon that no one would dare now blame Microsoft
for the change.
Microsoft's *real programmer*'s platform has been Visual C++. So, did MS
force its C++ customers to use .NET? No, it didn't. Instead they created
the currently most compatible ANSI C++ compiler in the world (ver. 2003).
I myself was surprised to test all the code from Stroustrup's "The C++
Programming Language 3rd Edition" compile without a single modification in
VC++ 2003.
>What if the date for final reelase slips by, say two months? Will that
>cost your company its existence?
Of course not. Because Microsoft is making damn sure that if its own
development tools cannot create 64bit application that no one else can run
64bit apps in Windows. MS is also pushing Windows back. Can you see the
big picture here? I can't say this is a good thing for the users. But I
hope you agree with me that Microsoft's way is a safer way to go.
>Why would 32 bit software not be upgradable at a later date? Why exactly
>now?
Because Borland does not plan to release a 64bit Delphi compiler. I cannot
afford spending time learning how to do conversion to 64bit in Assembly. I
understand that *maybe* Borland will release a 64bit Delphi, but should I
risk my entire career on that unanounced Delphi? Plus, if more than half
of the C++ developers use Visual C++, it cannot be that bad (in case you
don't trust my personal judgement).
Dennis: >then consider the difference between a single server that
> supports 1 million hits per day verus a server that supports 1.3 million
> hits per day...
Rudy: >Yes, I don't see that as a significant difference. I had expected a
> lot more.
Most of the large enterprises are making big losses nowadays. These
enterprises are aiming at breaking even and would be a big win for them
gaining profits in the range of 2%-3% of their revenues. Spending 20%-30%
less on their multi-milion $ equipment would help them reach their goal
and stay in the market. So now you see that that difference is not
significant, but vital.
I found it hard, 't was hard to find.
Oh well, whatever, nevermind.
--- posted by geoForum on http://delphi.newswhat.com
- Next message: Yorai Aminov (TeamB): "Re: Delphi 8 and Win32 update details"
- Previous message: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- In reply to: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- Next in thread: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- Reply: Rudy Velthuis (TeamB): "Re: 64-bit Windows for AMD 64 is here..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|