Board index » delphi » Re: The alternative Delphi roadmap to success

Re: The alternative Delphi roadmap to success


2006-10-13 11:25:45 PM
delphi245
Dennis Landi writes:
Quote

With UNIQUE PRODUCTS: Delphi and Bold/ECO; Borland has worked as
hard as possible to BLEND INTO THE MICROSOFT TOOLSET.
ECO blends into the MS toolset?
ECO is precisely a distinguishing advantage and can continue to be.
--
Wayne Niddery - Winwright, Inc (www.winwright.ca)
"The legitimate powers of government extend to such acts only as are
injurious to others. But it does me no injury for my neighbor to say
there are twenty gods, or no God. It neither picks my pocket nor breaks
my leg." ?Thomas Jefferson
 
 

Re: The alternative Delphi roadmap to success

Quote
Also, native only would put DevCo at the mercy of Microsoft
to not deprecate and drop win32 api's.
Not very realistic. If something can be deprecated very quickly, it is a
version of the .Net FrameWork, just like they can deprecated any of
their development tools... they've done it several times already,
they'll do it again.
But the Win32/Win64 API is more than an MS development tool, it is the
basis of the whole Windows Ecosystem. Kill or restrict it, and MS
Windows becomes no more useful than your random Linux distro.
Eric
 

Re: The alternative Delphi roadmap to success

Quote
A) Let's not assume they will be.
Except that it has stated that they will? Besides, not assuming they will
be is fine, but that doesn't mean that you should assume they wont.
 

Re: The alternative Delphi roadmap to success

Quote
in time*. Delphi has continued to be successful precisely because
they offered
Pascal. I don't know and I don't care about what other guys like,
everybody is free to have his preferences. I do like Pascal coding,
I'll never do C. Period. If Delphi is dead tomorrow I will still be in
business for a few more years maintaing whatever code is left, switch
to whatever Pascal-ish alternatives arises, even do ADA (did some many
years ago) or anything else similar. If these won't pay my bills, I'll
quit programming and start hunting (did this pretty recently, not bad
at all).
Lucian
 

Re: The alternative Delphi roadmap to success

Ingvar Nilsen writes:
Quote

some believed/hoped Win95 would be a
fiasco and Win 3.1 would be forever..
Yup, or that it would simply fail since Win 3.1 was all the O/S anyone
should need.
--
Wayne Niddery - Winwright, Inc (www.winwright.ca)
"Those who disdain wealth as a worthy goal for an individual or a
society seem not to realize that wealth is the only thing that can
prevent poverty." - Thomas Sowell
 

Re: The alternative Delphi roadmap to success

Wayne Niddery [TeamB] writes:
Quote
While we don't know actual numbers, clearly there are lots that have
upgraded to 2006 as well as many that have not, some of whom have given
their reasons here.
Sure.
Quote
But this begs the question of what would be *enough* to
get some of these people to upgrade. IMO, if the changes in both the
language and the IDE between Delphi 7 and 2006 isn't yet enough then even if
Highlander were 100% dedicated to Win32 it would *still* not be enough for
quite a few of those that don't think they are getting enough value with
2006.
You're working hard Wayne...I respect hard workers. ;)
I think there are some significant features on the native side that
would compel users of D5-D7 to upgrade. I don't believe there are any
silver bullets that will get all of them to upgrade or even the majority
of them to upgrade. But the biggies are: Unicode and Win64. Simon puts
Linux in the mix, which I am somewhat ambivalent about.
But if DevCo puts those two big ticket items in, then I think we can
come back to your question about what is enough to get them to upgrade.
But asking it now, when those two (three) things are in play is, IMO,
working hard to dismiss the expressed desires of the Delphi community.
Quote
IMO, those that cannot see value in 2006 over a 5 year old Delphi 7 are not the
group of customers DTG should spend the *most* time trying to cater to.
And IMO, this is exactly the kind of arrogance that will kill Delphi. I
believe there are too many of them *not* to focus on them. Besides,
conventional wisdom suggests that getting existing customers to upgrade
is much easier than winning new customers.
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Re: The alternative Delphi roadmap to success

Wayne Niddery [TeamB] writes:
Quote
The last thing DTG wants for
their .Net offering is for it to be nothing more than a "me-too" clone of
everything VS does.
What part of their .NET strategy indicates this?
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Re: The alternative Delphi roadmap to success

I reply here because I cant find the first post of the thread...
Hi,
Today I received a link to delphiroadmap.untergrund.net/ and
I'd like to express mi opinion.
I've been using delphi for a very long time and been involved in large
projects using delphi. I used to think that it was the best choice and it
was well suitted for most types of projects. Until Delphi 7 borland was
fullfiling my expectations and I was very happy.
Today, most developers that been using Delphi are desperate to migrate
to java or MS.NET. The Delphi market here is gettin smaller as time passes
by and its getting very difficult to find delphi programmers. Id like to
note that I know a lot of people that uses delphi and most of them share my
opinion.
Delphi 8 has nothing new to offer me. Its very expensive and it is not
better than visual studio. It always be one step behind MS and a person who
wants to learn .NET will obviosly turn to C# and Visual Sudio.
In my point of view borland is commiting suicide. Its beign a company
that caracterizes for having great (the best) products but terrible
management. I dont want to be negative but it really frustrates having
invested so many time and effort in a tecnology that it seems to be digging
its own grave.
From the borland point of wiev I'd have never endorsed .net. When dot
net came out if i were borland I'd have developed my own Borland Virtual
Machine or Borland Intermediate language, upgraded the vcl to compete with
the .net framework classes (providing compatibility with java and .net at
the same time), and make everything compatible with the previous versions of
Delphi.
Esteban Calabria.
 

Re: The alternative Delphi roadmap to success

Bob Dawson writes:
Quote
Let me rephrase the question a little: Apart from the .NET 1.1--2.0 issue,
is BDS2006 a superior product to VS2005 for .NET development?
Fair enough.
Quote
I'd have to say no--while I like many things about BDS better, as of now
it's still a very uneven product. I like the design and attitude of BDS, but
the execution is rougher--it still has some 'fit and finish' issues (the
help system, for example).
Gotcha. So if Highlander cleans up these issues, do you believe it will
be a superior product to VS.NET 2005?
Quote
Will I come back to BDS for .NET after Highlander? Hope so--
IMO, DevCo is lucky to have you as their customer.
Do you think others that have moved to VS.NET will come back to BDS?
Even if Highlander does better with fit/finish issues?
Do you think there will be enough in Highlander to get new .NET
developers to choose BDS over VS.NET?
Quote
I'll get it just
for the D.win32 features,
Exactly. ;)
Quote
but if I can use one IDE for everything, that is an
advantage in my book.
Why? I use all sorts of separate tools for the Delphi Win32 work I do.
I use a DB GUI, a text editor, OxygenXML, TopStyle and CodeFactor. ;)
Not to mention little things that I find invaluable like ColorCop.
To me, using more than one tool is just a development reality.
Quote
Will that be with DfDN or C#? Don't know at this
point, and probably won't until Highlander is released and we see what the
DfDN feature set actually turns out to be.
Do you have any plans on using .NET 3.0 features?
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Re: The alternative Delphi roadmap to success

Bob Dawson writes:
Quote
"Brian Moelk" wrote
>Feel free to post this same response to Kyle about smoking crack below. ;)

Chad is by no means the only rhetorician on the board. :-)
Certainly not, but why did you single him out and not Kyle? ;)
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Re: The alternative Delphi roadmap to success

Brian,
Quote
I would think OpenGL would be a better choice than DirectX if someone
was going to do that.
quote possible, yes. To be honest, i do very little graphics/3d work and
am entirely oblivious to the benefits and differences between the
DirectX and OpenGL APis.
--
marc hoffman
Chief Architect
RemObjects Software
www.remobjects.com
and the fifty-two daughters of the revolution
turn the gold to chrome
 

Re: The alternative Delphi roadmap to success

marc hoffman writes:
Quote
One could certainly implement a purely Win32/DirectX based clone* of WPF
as Delphi (or C++, or whatever) code, if one were willing to re-invest
the hundreds of man-years that Microsoft probably poured into this project.
I would think OpenGL would be a better choice than DirectX if someone
was going to do that.
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Re: The alternative Delphi roadmap to success

LDS writes:
Quote
Simon, just a note about the old Borland roadmap: Managed C++ died
already. MS changed it in C++/CLI, and they are not the same. Syntax
changed a lot (it's funny to see String^ in C++...!). that is another
hint on how dangerous it to run after MS.NET.
A very good point.
At least MS had the sense to identify a failing strategy and replace it
with a much better one.
Ian
 

Re: The alternative Delphi roadmap to success

James K Smith writes:
Quote
Right?
Right.
--
Nick Hodges
Delphi/C# Product Manager - Borland DTG
blogs.borland.com/nickhodges
 

Re: The alternative Delphi roadmap to success

Wayne Niddery [TeamB] writes:
Quote
While I agree that, *ideally* they should continue adding new value to the
Win32 side, it must be remembered that BDS can *already* be considered the
best Win32 tool on the market for most development needs, and it is *very*
unlikely at this point in time that any other development product will ever
even attempt to surpass that.
Agreed. They have a well-regarded and significant advantage on Win32
that they can continue to sell.
Quote
So in the event it really had to be either/or between pushing forward on
Win32 or .Net, it only makes sense to focus on a *growing* market, not a
static one.
That presumes that your static market actually stays static and will not
shrink if you neglect it.
I acknowledge that you were constraining the discussion to Win32/.NET,
but it is important to recognize that .NET isn't the only growing market.
Quote
Granted that static market still represents a good chunk of
upgrade revenue if they can entice those customer to upgrade to the next
version(s), but it will represent very few *new* customers at this point.
Agreed. ;)
Quote
Therefore focusing *only* on Win32 (and even Win64) guarantees essentially
no future growth and steady attrition since some currently native code-only
developers *will* eventually move to newer platforms (or retire, etc).
Win64 isn't a growing market? AMD would probably dispute that claim.
The problem is not that .NET is a bad market, the problem is that their
strategy and execution in .NET isn't effective and isn't working.
So, it would be more relevant if instead of advocating .NET support as
an *idea*, you could spend some time trying to convince everyone that
DevCo's .NET strategy is right. I presume that you're happy with their
strategic direction, perhaps you even have some minor tweaks in mind.
Let's talk about those things, not debate .NET as a viable market.
And yes, I just burned your strawman. ;)
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM