General discussion

Locked

DELPHI vs J2EE

By rajanikanth_iitk ·
Hello there!
Can somebody help me out in this topic
My Questions are :
1. Why would someone convert DELPHI application to J2EE application ?
2. What are the advantages and disadvantages in doing so ?

Thanks in Advance
Rajani

This conversation is currently closed to new comments.

24 total posts (Page 1 of 3)   01 | 02 | 03   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

popularity and "portability"

by apotheon In reply to DELPHI vs J2EE

J2EE is, of course, Java. Java enjoys the benefit of being ubiquitous: you can always find developers for Java. There's also the simple fact that Java is a powerful, pervasive buzzword in the IT industry these days. In fact, Java is probably the most popularly advertised-for programming language in help wanted ads right now.

Java is also renowned for "portability". In Java's case, what this means is that you can compile Java bytecode and it will run on any machine that has a Java Virtual Machine running. Of course, such bytecode interpreters are essentially just glorified program interpreters like those used for languages like Perl and Python, but that's an argument for another day (especially when you get into the compilation and bytecode options available for Perl).

Java is loved by many, and loathed by many. Delphi is pretty universally scoffed at, though this is more in keeping with the way someone that wears Calvin Kleins will scoff at a pair of Wrangler jeans rather than any actual useful judgment of the design environment's characteristics.

Something to realize about Delphi is that it's just an IDE. The IDE is, of course, for the Object Pascal language, which in many ways is one of the best-designed languages ever created. In others, of course, it lacks some characteristics that many people consider critical.

Probably the most important downside to Object Pascal code is that it's very difficult to find programmers to support the code in the future.

Delphi produces executables (binaries, for the Unixy among us). These executables tend to be rather less bulky, and faster-running, than Java bytecode. In fact, Delphi-compiled binaries often run faster than binaries compiled from C++ source. As far as I'm aware, though, there's no Object Pascal Virtual Machine in existence for running bytecode, so "portability" for Delphi-designed applications will have to be measured by how easy it is to create binaries for different platforms.

The newer Delphi versions can be had with the ability to compile for Unix/Linux. In that sense, at least, Delphi-compiled binaries are extremely portable.

So. That's what I've got, off the top of my head.

Collapse -

Not true

by Tony Hopkinson In reply to popularity and "portabili ...

I've plenty of years left in me yet.

Collapse -

delphi

by Jaqui In reply to popularity and "portabili ...

Borland's Kylix for linux is literally Borland's C++ builder and Delphi environments.

all ui components for all Borland c++ Builder and Delphi use the same interface code.
a Delphi based wrapper for QT

with the build options available for kylix 3,
you can code once, and build for all os options, with only needing to tweak the configure for each os and platform.
( same as rest of the gnu-linux development tools )

another benefit, is that kylix3 has a personal version, absolutely free.
( targeted at gpl use )

Collapse -

linux but intel only

by charles In reply to delphi

keep in mind that kylix will compile only to 32-bit x86 processors.

otherwise for cross-platform you'll have to go the mono route.

Collapse -

that's not

by Jaqui In reply to linux but intel only

a kylix limitation, that's a compiler limitation.
which even includes windows versions of delphi, as kylix and delphi both use borlands compiler.

give them a bit of time and they will address the 64 bit issue.

Collapse -

It depends on the type of application

by jslarochelle In reply to DELPHI vs J2EE

It is difficult to answer your query (specialy item 2) without having more information about your application.
Could you could provide more details ?

In the meantime here are a couple of remarks:

1) Be carefull about arguments mentionning portability as a factor to switch to J2EE. It is nice to be portable but for an existing application the cost is high. For a new application if there is any chance of switching to a new platform then by all means use Java (forget Microsoft .Net).

2) Be sceptical of any arguments mentioning J2EE being too slow. With the right mix of technology and proper design J2EE will work perfectly when appropriate.

3) If you do make the switch get some expert training and/or counseling.

Good luck!
JS

Collapse -

why forget .Net ?

by AngelOM In reply to It depends on the type of ...

.Net has been satanized because it comes from Microsoft but it is a very powerfull development tool, I think that the desition to use one platform or another is application/situation dependent. Delphi it self is a very good development tool and object pascal is a very nice lenguage but it carries with many features oriented to please the old non-object oriented pascal programers and to import others from visual basic; some other important features has been left behind (robust multi threading is a good example). Neverdeless very good programs have been made in Delphi because in the end the brain of the programer is what counts.

(sorry my bad english)

Collapse -

portability

by Jaqui In reply to why forget .Net ?

.net only runs on windows so it isn't portable.
the idea behind using java, c, c++, delphi or even cobol is that it is portable, can be used on any os.

the problem with the interpreted languages ( java, perl, python ) is the support for the standard.
I would always recommend using sun's javavm,
and to go to python.org for the interpreter,
and perl.org for the interpreter.

then you have the system with full compatability for the languages.
instad of distro / vendor limited.
( Active State is not the same interpreter as perl.org has, yet perl.org is the group developing perl. )

Collapse -

Wrong.

by KaceyR In reply to portability

The moment that Microsoft released the .Net CLI to ECMA, the Mono project was born. The Linux community has worked quite hard, and had a lot of help from Microsoft itself, to create Mono 1.0, which is the .Net Framework release for the Linux environment. Use that and the #Development IDE for a very powerful .Net development environment on the Linux platform.

Collapse -

Exactly, mono is here, and parrot's comming

by Joe McTroll In reply to Wrong.

You're right, the Mono project set forth a framework for working with .NET at libre unix systems...

Problem with both JVM and .NET is their bytecode represents the machine code of virtual RISC machines, which runs ultra-fast when interpreted at RISC machines (such as SPARCs) but is turtoisely slow running on CISC (such as Intel and compatibles).

But now we have the parrot virtual machine project, aiming at providing a common base for python, perl and tcl. It represents a virtual super-CISC machine, so it will run ultra-fast at our computers. And since it is open source, it will be available almost everywhere...

So perhaps it won't be such a bad idea to program in perl 6 or the comming versions of python and tcl/tk, now that we'll have both portability, multilanguage programmin (as in .NET) and *speed*...

Back to Web Development Forum
24 total posts (Page 1 of 3)   01 | 02 | 03   Next

Related Forums