Board index » delphi » Re: Brass Tacks: The Fate of 64-bit Delphi

2004-06-10 03:49:13 AM
delphi233
Dennis Landi writes:
--
Dave Nottage [TeamB]
 

Bruce McGee in <XXXX@XXXXX.COM>writes:
--
John Kaster, Borland Developer Relations, bdn.borland.com
Add a feature/Fix a bug: qc.borland.com
Get source: cc.borland.com
TVS.NET 2 for only $199! Unbelievable! tinyurl.com/259jx
 

Dennis Landi writes:
Rene
--
Ing.Buro R.Tschaggelar www.ibrtses.com
Your newsgroups @ www.talkto.net
 

Bruce McGee writes:
may not ever need such a thing, but I certainly wouldn't vote against
it. There are a number of features I need much more urgently than
Win64, though (e.g., generics).
-Craig
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : delphi.weblogs.com
InterBase in Multi-tier World -- Use multiple RDMs, IB features in
your appserver: delphi.weblogs.com/stories/storyReader$195
 

"Bruce McGee" <XXXX@XXXXX.COM>writes
<paranoia mode>
The arguments are starting to be convincing. Its hard not to imagine that
Borland has sold out to Microsoft to some extent. Borland won't die, but
Delphi might be relegated to further obscurity. consider:
1. .NET is pointed to as the solution for everything, as stated by Dennis.
2. They publicly stated that they didn't know if they were going to release
another Win32 version of Delphi less than a year ago. (Translated: don't
bet on 64bit support, which shouldn't be considered another platform but a
continuation of 32bit BTW)
3. BCB is gone and its replacement isn't using the VCL.
That last move alone is enough to make me nervous. Borland has shown that
they have the willingness and capability to drop an entire product suddenly
without warning. When they themselves start to question the need for
further 32 bit Delphi development, as they have, the writing appears to be
on the wall. Its hard to imagine Native code compiling Delphi continuing
without updating it to 64 bit. The next one or two 32 bit Delphi releases
seem to be aimed at satisfying customers until they move to .NET.
The shift from producing fast native code compilers to producing IDEs and
developer tools is well under way. This may be because Borlands welfare is
in part tied to the success of .NET, I don't know. Microsoft and Borland
have a patent license agreement that makes .NET possible. They are enjoying
a relationship with Microsoft unheard of in years past. Borland reps have
shown up at technology shows as Microsoft partners in Microsoft booths.
Borland developers are getting training at the Microsoft campus. The recent
threads 'Microsoft unveils IDE plans', and 'The Pascal-ization of MS and
C++' show that MS doesn't believe all of their own marketing hype to the
degree Borland expects us to. Borlands traditional strengths are being bled
away. While MS directs Borland to .NET they are improving their own native
code offerings. Borland hasn't had all of its eggs in one basket, but how
long do you think it will be before JBuilder is an IDE for Microsofts Java
compiler.
</paranioa mode>
Brent S.
 

zedd writes:
research to decide future plans? No speculation is needed, any claim that
they do not do so is simply absurd.
That those plans may not agree with your own conclusions about the future is
hardly evidence that they failed in their research.
--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: www.logicfundamentals.com/RADBooks.html
It used to be that other people's achievements were considered an
inspiration, not a grievance.
 

Craig Stuntz [TeamB] writes:
--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: www.logicfundamentals.com/RADBooks.html
Working for yourself is great because you get to work half days, and
you can choose any twelve hours you want.
 

Joanna Carter (TeamB) writes:
Studio 2005 ship with not one but *two* 64-bit compilers out of the
box? (Visual C++ for IA-64 (Itanium) and Visual C++ for AMD64
(x86-64)) I am not saying .NET isn't going to have a place, but denying
the future of Win32 is Win64 is kind of silly...
that it boggles the mind that you'd believe you can not have one source
tree for both. Rid yourself of obvious no-no's like relying on the
size of a pointer being the same as the size of an integer and other
such *well* *documented* gotchas and you will be safe.
this be true if each new version of Delphi sells more than the last
version? Are Borland employees receiving raises equal to the ratio of
new incoming profit? Where's this extra income going?
but nobody stores strings in a persistant manner (what good is a
pointer that'll be invalid the next time your application reloads?).
Just about every gotcha you can imagine for going from 32-bit to 64-bit
is well documented, most of it by Microsoft.
Win32 and Win64 development. It just won't be Delphi code anymore,
which is more an issue of syntax than of viability.
Will
--
Want a 64-bit Delphi compiler for AMD64 / IA-32e? Vote here--
qc.borland.com/wc/wc.exe/details
 

"Henrick Hellström [StreamSec]" <XXXX@XXXXX.COM>wrote in
message news:40c70fc1$XXXX@XXXXX.COM...
from any Java developer.
 

Brent S. writes:
either baseless or misleading, they're not looking convincing at all,
eg:
--
Dave Nottage [TeamB]
 

"Will DeWitt Jr." <XXXX@XXXXX.COM>writes
wanted to which is very debatable) for Win32/Win64 *AND* Managed C++.
I just don't see the relevancy in these types of red-herrings. How I code
my windows clients has very little to do with how I will code my socket
servers... Or dynamically loaded "tier-agnostic" middle-ware. If I can
share some helper utilities, fine. Big deal. I hardly see this as some
kind holy grail that precludes actually writing a critical compiler for the
next windows platform....
-d
 

Brent S. writes:
Maybe they once listened to the yelling for "a delphi but with c++"
that was just necessary to make it a decent product?
And maybe all those who yelled didn't buy?
And maybe no company can go on just making things yelling people in
ng's ask for?
And maybe they have good reasons for not starting a 64-bit compiler
project?
<rethorical questions>
Anders (who has no clue)
 

Lars Black writes:
 

"Joanna Carter (TeamB)" <XXXX@XXXXX.COM>writes
I've yet to read a post of yours I don't love ;-)
Thanks Joanna.
 

Paul Nichols (TeamB) writes:
had a future for desktop programming. Much like the present situation
for .NET. <g>
--
Henrick Hellström
www.streamsec.com