Board index » kylix » Re: DElphi/Kylix Vs. Java ??

2003-12-07 09:19:11 AM
kylix1
"pNichols" < XXXX@XXXXX.COM >wrote in message
[..]
vendors they aren't familiar with?
[..]
coming from a Delphi and VS6
background: (1) the fact that allows to build better Windows applications
than Java, (2) the fact that is better integrated with MS tools such as SQL
Server or Biztalk for instance, (3) the fact it allows people to choose the
language they prefer and not being locked in a single language, (4) the fact
that having one major vendor behind it means quicker upgrades and
improvements versus something that has to go thought hundreds of heads and
standard committees, (5) the fact you can use Delphi on top of it, (6)
attributes which IMO are one of the slickest things ever made in
programming, (7) from a 3rd party vendor perspective, the ability to target
a lot of market-audiences in one shot (namely VB, Delphi and C# guys), (8)
the fact you can target 64 bit processors as well as other frameworks allow
you to do, (9) the abundance of *well-organized* documentation available on
the MSDN and the hundreds of sites related to .Net.
These are a few good reasons. This doesn't mean that everybody should or
will move to .Net. Many people are afraid of change, but that
(unfortunately) works the same way in regards of both .Net and Java . Many
others just don't have the need or resources to do it (time-wise. Spending
375$ to get 5 licenses of the MSDN universal is something most people can
afford so it's definitely not a money problem. Worst case scenario there are
free IDEs out there and the SDK is free too). Some others need to go on
Solaris so that cuts .Net out right away. But you can be sure a *lot* (which
doesn't mean all of course, but IMO most of them as you can gather by the
posts in Delphi newsgroups) of current Delphi and VS6 developers will either
just stay with the tools they have now or move to .Net rather than embrace
Java. I will start considering Java not just a high-end, Enterprise
phenomenon when I will see software like Winzip, ACDsee or those people use
at homes done in Java and not either C++, Delphi or VB. Until that day will
come people will have plenty of good reasons *not* to use Java but use
something else (whatever that is).
My 2c.
--
Best regards,
Alessandro Federici
RemObjects Software, Inc.
www.remobjects.com
 

"Mike Margerum" < XXXX@XXXXX.COM >wrote in message
[..]
It would just be bad business and would immediately dictate the end of the
platform adoption.
 

"Mike Margerum" < XXXX@XXXXX.COM >wrote in message
change the rules at any time and there is nothing anyone can do about it.
They've done it in the past, they probably will again in the future if it
suits their needs.
 

{smallsort}

Mike Margerum wrote:
the emphasis of Java are different. MS intended NET to be mono platform
from the beginning, Sun wanted Java xplatform from the very beginning. Sun
makes less $ off of Java than Borland, BEA, IBM, or Oracle. Unfortubnate
for Sun, to be sure, however, it shows the ubiquity and the direction that
was planned for Java. One common JVM and APIs, many platforms. Net was
intended to be many languages, one and only one OS and platform.
Nothing prevents NET from being Xplatform, but MS. Whether they let Mono
survive or not, is still up in the air. MS could, at any time, cry
"intellectual property rights were violated". They wouldn't do so now,
because it gives hope that NET will be xplatform, which is to MS' advantage
in their fight against Java. I seriously doubt they would win that battle
anytime soon, if ever.
 

"pNichols" < XXXX@XXXXX.COM >wrote in message
[..]
Rotor example and the fact thay didn't go after Ximian when they started
Mono (or later) suggests they are not that against ports IMHO
All the evidence points to an MS that developes just for Windows but is
leaving space (to others) to extend their platform for free (to them) on
other systems. I wouldn't rush judgments on MS' intentions. Many things have
changed in MS during the past few years.
high priority for MS (see DDE, OLE, COM). That by itself is IMO the most
compelling reason to move to the .Net platform but I am talking as a
component vendor here. The cross-language nature of .Net is has positive
side effects for regular Windows developers by giving them a wider choice of
tools compared to what they had before (i.e. Delphi people can now also
choose Infragistics, ComponentOne, etc etc and VB/C# guys can take advantage
of Delphi vendors).
so far which points in a completely different direction.
 

"JQP" < XXXX@XXXXX.COM >wrote in message news: XXXX@XXXXX.COM ...
[..]
confident in putting my future in the hands of a company that is showing
only to be reactive rather than pro-active. It seems that Sun only comes out
with anouncements *after* MS has done something (good or bad). There's at
least 2 years of examples on eWeek.com about this
I cannot stop wondering why, everytime a Sun official is interviewed, he/she
have to mention MS and turn the whole conversation into a comparison. MS:
"we have this "new" cool thing coming out which you can download and see
[bla bla]" Sun: "we have this other cool thing being standardized and
"spec-ed" out which might come out [God knows when] and, by the way, it's
definitely a better answer to people's need than what MS is doing which is
obviously only meant to lock you in and make you pay their tax [<--aka money
*not* going to Sun <G>]". Am I just seeing things or this is how it really
looks? <G>
 

JQP wrote:
This is so dumb to be argued.
If you license your software to someone with the condition that they must
adhere to standards and they take your software proprietize it, and violate
the temrs of the agreement, do you think they should get by with it? Of
course not. yet this is precisely what MS did.
direction of NET but MS. Java allows the JCP to set the standards of Java.
Please know what you are talking about!!
Read this document, and it might enlighten you to the differences
jcp.org/aboutJava/communityprocess/review/jsr215/index.html
 

pNichols < XXXX@XXXXX.COM >wrote in
why Sun did not keep more language-independend. Ok, sure, it's possible
to work-around the limitations a little bit, but that's not the same.
 

"Alessandro Federici" <alef@remobjects[remove-this].com>wrote in
environment.
There is also Wine? Does this turn the Win32-api in a cross-platform
environment? No, it does not. The same is true for mono.
IMO, it's important that the driving power behind a environment develops
it with the intention to be cross-platform. Clones may make software from
another platform usable to some degree, but I would always expect legal
and technical problems.
.NET /may/ turn into a cross-platform environment when some groups agree
on a cross-platform library on top of the standardisized .NET part. I
would not consider WinForms cross-platform, but I might consider some
independend developemnt of XForms, XDB, and so on as usable cross-
platform environment. I hope that such a development will happen, and
that Borland will support it.
 

"JQP" < XXXX@XXXXX.COM >wrote in news: XXXX@XXXXX.COM :
They sued MS because MS because they tried to make their own changes.
 

"Andreas Prucha" < XXXX@XXXXX.COM >wrote in message
 

"pNichols" < XXXX@XXXXX.COM >wrote in message
The 3rd line in the document that defines the Java Community Process is:
"copyright(c) 1996-2003 Sun Microsystems".
Sun wrote it, Sun controls it, Sun owns it and they can change it any time
they want.
Sun decides who participates in the "Java Community Process". And just to
be sure there is no mis-understanding, Sun requires anyone wanting to
participate in the JCP to sign a number of legal agreements to this effect
and these agreements must be renewed on an annual a basis, which again is at
Sun's discretion.
 

free/open when Sun can at any time decide to start charging for it and
revoke licensing. Doesn't the fact that supposedly 75% of enterprise
coding is being done in an environment that is owned by one company
who is clearly on the decline and will be looking for new revenue
sources?
At least m$ opened up the CLR and C#. You can create your own
implementation of these and m$ cant ever come after you.
 

"Mike Margerum" < XXXX@XXXXX.COM >wrote in message
For example, Sun most likely gets a piece of every copy of JBuilder that is
sold. The only people who know the exact terms are Borland and Sun.
Revealing the terms would probably revoke Borland's license.
 

"Andreas Prucha" < XXXX@XXXXX.COM >wrote in message
nowhere near the extent Java is, but cross-platform nontheless).
anything Borland does anyways (for cross-platform *outside* the Java scope),
expecially after the CLX fiasco. In between the non-so-reliable options we
have, it is (IMO and at the moment) the most reliable one.
Keep in mind that Mono doesn't really need WinForms too much. Not many
people don't use Linux or .Net for desktop apps, so as long as it supports
ASP.Net, ADO.Net and the server side stuff (which does now), it's gone as
far as it is useful for being usable.