Re: Delphi roadmap from the .NET perspective...

Alexandre Machado wrote:
VB *was* capable of getting things done at some level.

Not anymore.

VB code has stopped working? That's news to me.

Why? What benefit did you get from the port?

Architectural benefit. Easier integration using WebServices.

Why did the *whole* thing need to be ported? Couldn't a .NET webservice invoke COM+?

And there is another one that our company has faced: contractual requirement (Java or .NET), because that particular customer was convinced by some *IT expert* that Win32 native applications could harm their servers....
Indeed. But is Delphi ever going to compete in such an environment?

Why not? There is no technical reason.

Because it's not a technical argument.

The point is that if you want a choice in whether or not to wait, VS.NET gives you that choice. If you want to forfeit that choice, by all means use Delphi for .NET. What I don't understand is why one would want to forfeit that choice?

We think different Brian. I want to keep things simple. I want to keep budget low. We have dozens of *in production* applications. All of them require constant maintenance.
Keeping the number of programming languages, frameworks, IDEs (specially the paid ones), etc, low is vital.
I just don't believe that we would be more sucessful or competitive in our business if we were using VS and not Delphi. So thinks the company's high management, at least for now.

So your answer is that you forfeit your choice because the lack of a choice keeps things simple. If CodeGear supports it, you use it. That's simple.

I find it strange that you use .NET at all? It's adding another framework to your infrastructure isn't it?

I certainly like to keep things simple and minimalistic, however IMO, if you're going to use .NET keeping it simple and minimalistic means using VS.NET.

That's not what I meant. *Need* to be successful, *need* to be competitive in the business, *need* to be productive. And yes, you need OO and high level languages to be competitive and productive, don't you?

Actually, I don't think OO is necessary. Functional languages aren't OO and they can be used to a great deal of success.

Besides, some would argue that generics make one more productive that in order to compete, they are needed.

If we did so, today we would have hundreds of frameworks, dozens of IDE's, at least 5 or 6 programming languages. How viable is that?
Welcome to the modern development landscape.

The same above. I know companies that are having a lot of trouble managing only Java frameworks... I would like to see them handling some Ruby, php, Delphi, C# and C++ frameworks too.

Typically shops specialize; but that doesn't mean they don't have additional languages creep into their build processes or websites, etc.

Modern software development typically includes the following "additional languages": HTML, JS, CSS, XML, XSLT and SQL. Reasonable proficiency in all of them is pretty much a requirement.

It's the framework that takes time to learn and leverage.

Yes it is. I'm not sure about your country, but here they do not ask a Java developer, they ask a Java developer with high knowlege of X, Y and Z frameworks. Thats why use hundreds of framewoks in our company does not help us to be more successful in our business.

Right, so why are you adopting yet another framework (i.e. .NET)?

Like I said before the difference between C# and Delphi isn't that great; a developer that understands the OO underpinnings of Delphi can make the transition to C# reasonably quickly.

So if you're going to already use .NET, you've already chosen to accept the thing with the greatest learning curve and complication. Yet you cling to a language/toolchain that limits the ability to leverage .NET for the foreseeable future?

--
Brian Moelk
Brain Endeavor LLC
bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
.

Relevant Pages

  • Re: Branching Out / "Diverging" from Delphi
    ... I don't think Java is going anywhere. ... ....And now for the part where my brother Delphi developers pan me for saying ... programming languages to learn to help improve my career, ... Lisp seem important for their variance in programming methods. ...
    (borland.public.delphi.non-technical)
  • Re: C to Delphi set problems
    ... >> and Java. ... >> important differences between these languages. ... Leverage parts of existing Delphi codebases. ... Not 100% source compability, and source compability is its main ...
    (comp.lang.pascal.delphi.misc)
  • Re: Create a <table> of <textarea>s
    ... languages and Visual Studio. ... I've been working in Java, Delphi and Pascal and ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Nooooo
    ... I can and have already written software in Basic, Pascal, Assembly, Java, ... PHP, C, Clipper, dBase, Delphi and some other less popular languages. ... Sure, I was tempted to move to C# when it first came out, while .NET hype ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Delphi roadmap from the .NET perspective...
    ... But is Delphi ever going to compete in such an environment? ... Java, ... Keeping the number of programming languages, frameworks, IDEs (specially the ... developer, they ask a Java developer with high knowlege of X, Y and Z ...
    (borland.public.delphi.non-technical)
Loading