Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: "Randy Magruder" <rmagruder@xxxxxxxxxxxx>
- Date: 6 Feb 2006 05:04:37 -0700
I guess I better answer this since I'm the one who started this thread.
Because this mythical .NET migration path of Delphi does not exist.
Prove it.
So I can recompile VCL to VCL.NET. WHO CARES?
Anyone who does not have the luxury of time to re-write from scratch
hundreds of thousands of lines of WORKING code, introducing all NEW
bugs in the process. But aside from that, no one, of course!
How many of you out there are pissed off that there's no easy way to
integrate Win Forms and ADO.NET with VCL.NET.
Define "integrate". I can't answer this one til I know what it is you
tried to that you felt was not 'easy'.
Thanks Borland for one tiny "ADO.NET Converter" object hidden awayin the background. Is
that the best you could do!!! Why on earth would I even considerconverting my app to VCL.NET?
Obviously, YOU wouldn't. You must either have a) small applications
you can easily re-code from scratch in C#, or b) you have the luxury of
a lot of time and a lot of money to re-write your large ones from
scratch. I wish all of us in the real world were as lucky as you.
I refuse to get stuck with proprietry middleware like BDP andVCL.NET.
Just what is it Microsoft makes that isn't proprietary?
The .NET framework and Win Forms is part of the Operating System (itWILL be included in any future client os) exactly like MDAC, so I
don't have to worry about client deployments or massive exe files with
entire frameworks in them.
This argument is so incredibly lame I'm not sure it deserves any kind
of response. One might equally argue that you should make all your UI
components just use whatever comes out of the box in Visual Studio.
All your apps can look like plain vanilla, with no enhanced UI look and
feel, no advanced capabilities like you get with components from DevEx
or Infragistics, etc, all because you don't want to use anything that
doesn't come "out of the box". Any truly useful software you create
and may want to resell is undoubtedly going to require that you
redistribute something that you did NOT get out of the box from
Microsoft. But then I forgot, you have the luxury of huge amounts of
time, so when you need a complex customizable grid, I'm sure you'll
just write it from scratch because you have all the development time
and money in the world. Again, unlike we mere mortals. If the above
truly reflects your opinion, I already don't want to see any
applications you write. I expect they will be pretty vanilla. Boy,
third parties just suck, don't they?
Why would I use Delphi and VCL.NET when there are hardly anyprogrammers left using this?
There are many logical reasons to do so if you've got legacy code.
Clearly this is not a problem with you. Go enjoy writing your brand
new shiny apps from scratch.
If I could have migrated to Windows Forms smoothly, sure I wouldhave stuck with my old VCL.NET code and with Borland C# or Delphi. >
Since Delphi supports writing WinForms code, I'm not sure where your
rant is coming from? It's either ignorance on your part or an utter
failure to communicate just what it is you're trying to do and why you
cannot do it.
But NO, what's the point! If I go with VCL.NET, I'm stuck with it forthe forseeable future (and don't talk to me about
Delphi/Avalon/Framework V2 vapourware). If I want to hire programmers,
I'll have to train them up on technology that nobody uses!
I could write a whole new blog based addressing the kind of mentality
I'm seeing here...hmmm....
Remember one important point: What happened to most of the Delphi
(*real*) programmers? They all went over to C#? Why? Because: a.
They need to put food on the table b. .NET and C# is a GOOD piece of
technology. V2 of WinForms is almost as good as VCL. c. VCL has gone
NOWHERE in the last few years d. NO simple migration path to
.NET!!!!!!!!
Actually most of the Delphi programmers I know who learned C# use
whatever works for the job they need to do. Some of them have legacy
Delphi apps to maintain, others are looking at migrating some parts of
it to .net, and others are writing code from scratch. Anyone who
"went over" to C# is not someone I'd employ because it clearly implies
their brains can only handle one language at a time and they have to
'convert' in a religious sense to that language. I'd hire the guy who
is more pragmatic and is neither afraid of tackling apps in C# or
building and extending existing applications written in Delphi.
Most of your rant consists of hyperbole and grandiose, bellicose
statements with no supporting material. One can only GUESS what kind
of work you actually do, and what your code might actually look like,
but I wouldn't hire someone with your attitude, because you've clearly
gone Xenophobic when it comes to anything not produced by Microsoft and
shipped in every copy of Windows. Who needs that? I'll take a
pragmatic programmer who uses the right tool for the right job any day
over a zealot.
Randy
.
- Follow-Ups:
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: tony caduto
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Donald Shimoda
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Larry
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- References:
- My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Randy Magruder
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: John Kaster (Borland)
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Randy Magruder
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: John Kaster (Borland)
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Steve Zimmelman
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: John Kaster (Borland)
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Steve Zimmelman
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: John Kaster (Borland)
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Ingvar Nilsen
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: John Kaster (Borland)
- Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- From: Ingvar Nilsen
- My rant about the "throw out delphi and re-write it in C#" crowd.
- Prev by Date: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Next by Date: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Previous by thread: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Next by thread: Re: My rant about the "throw out delphi and re-write it in C#" crowd.
- Index(es):
Relevant Pages
|
