Slashdot Mirror


Borland Delphi and CBuilder for Linux.

jelwell writes "Borland has announced Linux support for Delphi and CBuilder. The tools are scheduled for a mid-2000 release. I wonder if they plan on integrating their products with any window managers/distributions?" Infoworld has the story - which also says, "To seed interest in the Java-on-Linux movement, Inprise this week will provide a free, downloadable preview of the JBuilder just-in-time compiler for Linux that supports many Java 2 Enterprise Edition specifications."

32 of 227 comments (clear)

  1. Source Level Compatibility with Win32.. by Thomas+Charron · · Score: 2

    All I can say is.. WOW. This will be SO nice. Finally, a relatively easy way for applications to run under *nix and Win32. Just a simple recompile..

    I know, I know, GNU tools on Win32 work, but not in the graphical interface area. I've always stuck by Visual C++ for Win32 development, but this is DEFINATLY a good reason to check out borlands products..

    --
    -- I'm the root of all that's evil, but you can call me cookie..
  2. I don't think it's a good thing at all. by Kaz+Kylheku · · Score: 4

    Nor a bad thing. It's just another piece of proprietary software that I'm not interested in running on my freedom platform. I hope you won't be seduced either.

    Linux hasn't needed Borland since the day it became powerful enough to run GCC and serve as its own development platform.

    Some of you are euphoric every time some commercial vendor offers a piece of ``support'' for Linux, because it means that the popularity of your favorite operating system is increasing. So you rejoice at the popularity increase even if you don't plan to use the newly ported product.

    Some, like me, would use a freedom platform even if it wasn't popular, and would use freedom software even if it wasn't as good as a proprietary alternative in terms of convenience or performance or other measures. How about you?

    1. Re:I don't think it's a good thing at all. by Dalavon · · Score: 2

      Also now we will have literaly thousands of apps written in Delph that can now be made available for the Linux platform (good thing in of it's self). Now instead of starting form scratch a software shop can jump in the Linux sandbox.(A dephi shop I mean.) And I suspect slowly some of these apps will become Open Source, and as we suspect these will rise to the top.

    2. Re:I don't think it's a good thing at all. by robinjo · · Score: 3

      I always love it when people demand you to do as they want while talking about freedom :-)

      New software is great news for Linux. Sure, it's commercial but who forces you to use it? You can continue your free life but let other people also have the freedom to choose.

      From my point of news Delphi for Linux is the best thing since sliced bread. I've been developing a big application on Delphi for a while. Thanks to Inprise I can also make a Linux-version of it and give my customers the freedom to choose between NT and Linux.

    3. Re:I don't think it's a good thing at all. by pgm · · Score: 3
      Nor a bad thing. It's just another piece of proprietary software that I'm not interested in running on my freedom platform. I hope you won't be seduced either.

      I think the BIG thing that kaz is overlooking here are people like me who develop commerical software that is marketed to people inside of large corporations and such. Selling software is my business, and while I RUN a linux server here at our office, I don't have the desire (nor the business model) right now to give my packages away.

      Sure, I've written a few free utilities for 32 bit Windows and they are available for free on my webpage. (http://www.buffnet.net/~millard) However, the fact of the matter is, that there are thousands of small shops just like ours that aren't prepared to give their products away! Having development tools like those that we are used to for the Win32 platform makes is beyond simple to jump into the Linux ballgame.

      Some immediate benefits I see are:

      1. More developers using Linux. This is a good thing for the OS and will eventually help all sorts of "mainstream" projects like KDE, Gnome, etc.
      2. More Corporations using Linux. This is also a good thing. A larger installed base always help to find bugs, not to mention the benefits for hardware support. More corporations asking hardware vendors for Linux device drivers will at some point actually mean something to hw manufaturers...they will eventually catch the drift.
      3. More freeware. Sure the development tools might be closed, but that doesn't mean that the utilities and applications that people develop with these tools won't be freeware. Look at all the utils and stuff available for Win32.
      4. Credibility for the Linux OS as a "big player". There are a LOT of corporations and IT departments that use Borland tools already. (We use Delphi almost exclusively here). By producing a Linux version of these products, it will force some people to sit up and take notice. "Well if Borland has tools, there must be something to this OS".

        All in all, this is some of the most exciting news (as a developer) that I've heard in a long time as far as Linux goes. I can't wait.

    4. Re:I don't think it's a good thing at all. by BillEGoat · · Score: 2

      Some of the biggest personal income in the development realm comes from custom applications. Just look at all the e-commerce startups that are out there making buckets on small custom apps for specific projects. This is the type of application that makes Delphi shine.

      Sure, it's not *great* for huge projects, and it's pretty poor for the typical Open Source app, but for throwing together rapid apps for minor database access and such, it's perfect.

      I can't wait. :)

    5. Re:I don't think it's a good thing at all. by harmonica · · Score: 2

      The good thing is that many Windows applications written in Delphi can be simply recompiled (well, at least in theory) and then run on Linux. That's a good thing (tm) because it makes Linux more attractive - the more applications available the better.

      Delphi developers can offer their customers a new platform without doing too much - they will be glad about this, they might sell more copies of their software.

      Linux gets another popularity boost from the well-known effect of 'wow - the xyz enterprise which is pretty important in the business has Linux support now'.

      And about the 'Linux doesn't need Borland' - there still is no RAD tool that matches Borland's products. Period. Clicking together apps may not be the most sophisticated thing to do, but that's what they need out there in the real world - sometimes.

    6. Re:I don't think it's a good thing at all. by emerson · · Score: 2

      The reason the GNU project exists is because there were proprietary compilers available. Without them, there would have been no way to develop gcc and binutils to the point of being self-hosting.

      It's easy to snub proprietary compilers, but they played (and continue to play) an important part in the the history of free/Open Source software.




      --

  3. A giant step closer to world domination for linux. by Anonymous Coward · · Score: 3
    Excellent. Now that Delphi is almost here for Linux, I will be able to make a better case for the software development at our company to move over to linux-only. Right now, the only realy push in the software department is coming from the firmware engineers, who vastly prefer the linux development environment.

    Many of the company's other products, however, are produced using Delphi, which is currently only available for the Win* OSes. With the addition of an awesome programming language (Delphi), together with another cool development tool (C++ builder), linux has indeed taken a big step closer to world domination.

    Why? Everything is a circle. Developers attract users, users attract developers. Eventually, you reach a critical mass, and the two groups will automatically begin attracting each other, even if the underlying product is shitty (ala windows). For OSes that have not reached this point, its critical that simple to use development tools are made available. If my past experiences with Borland are any indication, we are up for quite a treat.

  4. I wish there were more details. by Amphigory · · Score: 4
    I just wish they had posted more details. For example:
    • Is their port going to be native widgets, or WINE based?
    • If native widgets, what is the toolkit? QT? GTK? Dare I hope both?
    • Any desktop environments?
    • Are they going to port their compiler technology (which is quite good) or just lam off of gcc and free pascal?
    • How 'bout OWL? There are still quite a few OWL apps out there, and C++ Builder includes OWL. Are they going to support it?
    • Is the Java release they are doing this week going to be just the JVM (good) or the JVM plus JBuilder (great)?


    Just a few things that came to mind. I /like/ C++ Builder -- it's VB the way it should have been.
    --
    -- Slashdot sucks.
    1. Re:I wish there were more details. by DragonHawk · · Score: 2

      I wish there were more details, too. But I have a few insights to add.

      On the GUI front, I see three choices:

      1. Use WINElib to make existing their Windows code work.

      I find this unlikely. For one, Borland generally does not take cheap short-cuts. For another, I know Borland has cross-platform experience: Delphi is available for IBM's OS/400, which is not like UNIX or Windows, AFAIK. Lastly, if Borland pays any attention to the poll they ran, they will see most of their users who knew anything were against WINElib. (Nothing against the WINE folks here; I think it just means Windoze is a pain. We knew that.)

      2. Wrap the VCL around GTK, Qt, or some other existing toolkit.

      This seems likely. It would make Borland's job a lot easier. As a guess, I would say they would pick Qt. It is more like Windoze then GTK, by design, and Delphi is a Windoze product. Qt is also a little more OOPish then GTK, since Qt uses C++ while GTK uses C. Then again, the free (beer) license of GTK may be appealing.

      I doubt we will see more then one toolkit used. It would only make everyone's job harder. Borland's, because they would have to do twice as much work; developers', because they would have to deal with two sets of quirks rather then one; users, because they have twice as many runtime libraries that might be needed.

      The VCL is fairly good at abstracting away most of Windows. Sure, there are ways to get at the Windows internals directly. You will find that in any good abstraction (e.g., the C standard library). Borland knows that sometimes you have to go down a level or two. But, properly written code should minimize the number of places that has to be done, or not need to do it at all.

      3. Write their own X widget set

      There are already too many to count. What difference does one more make?

      Compilers

      They have already ported their compiler technology, at least in part. A Borland guy mentioned awhile back that they had the Delphi/Builder back-end compiler working on Linux already. Compared to GCC, it has both strengths and weaknesses. I think it is a fair bet they will do their own compiler; that is Borland's bread-and-butter, after all.

      OWL

      I do not know about OWL. C++Builder does include OWL libraries, headers, and source. The problem is, OWL is just as dependent on Windoze as VCL is, and I doubt Borland is going to port two libraries if they can help it.

      (For those who are wondering: OWL is the Object Windows Library, a OOP GUI framework for Windows back when MFC was still a gleam in Microsoft's eye. VCL is the Visual Component Library, the successor to OWL. VCL is even more OOPish then OWL was, and makes Windoze programming doable.)

      JVM or JBuilder?

      It appears to be just the JVM. Borland has been promising JBuilder for Linux for a few months now, though, so I think we can expect to see a commercial Linux product there soon. Prolly the Solaris port will have to come out first; does anyone know the status of JBuilder on Solaris?

      --

      dragonhawk@iname.microsoft.com
      I do not like Microsoft. Remove them from my email address.
    2. Re:I wish there were more details. by DragonHawk · · Score: 2

      Borland extended the Pascal language with a specific contruct to handle Windows messages (the message keyword), so in this sense, even the language itself is Windows-oriented.

      You've got a good point, but, to be fair, the MESSAGE keyword is (or should be) used only when implementing wrapper code for Windoze events. In other words, if you're hacking Windoze, that keyword makes your job easier. If you are writting a portable application, you don't touch it.

      It is similar (but not the same, I know) to the C standard library's strong resemblence to the UNIX system call API. Of source, the C standard library is not part of the C language proper, which is a key difference. The MESSAGE keyword is indeed rather a nasty wart in an otherwise fairly elegant language.

      The VCL of course it full of code that calls the Win API, and is therefore quite specific to that API.

      Now that is immaterial. Yes, the VCL is full of Win32 API calls on Windows. On OS/400, it would be full of OS/400 calls instead. The VCL interface remains reasonably constant accross implementations.

      To continue the comparison with C, a C standard library implementation will be full of platform-specific code as well. However, the interface defined by the headers is the same. That is the whole point of a standard library, after all: To abstract away platform differences.

      VCL is Object Pascal's standard library, and while not as pure as C's, it does a pretty good job. IMNSHO. :-)

      --

      dragonhawk@iname.microsoft.com
      I do not like Microsoft. Remove them from my email address.
    3. Re:I wish there were more details. by DragonHawk · · Score: 2

      They said a mid 2000 release date, which means its basically got to be working in 6 months (with extra time for QA/manuals/etc.).

      First, Borland has been working on this for awhile, so we cannot assume they have only six months to pull it off.

      Second, the VCL has already been ported to IBM's OS/400 platform, so Borland already has some knowledge of cross-platform VCL implementations.

      Third, when was the last time a non-trivial software product shipped on time? ;-)

      They could also build a bigger VCL framework which encapsulates all the functions you would use in a program thus making those programs cross-platform.

      AFAIK, they have already done pretty well in that department. If you are writting a generic (i.e., does not depend on goofy Microsoft services) program, your code can get away with pretty much just the VCL and Object Pascal. I/O, memory management, screen draw, can all be done within the framework of the VCL. The only major exception is getting the contents of a directory programmatically; you're still stuck with DOS/Windows FINDFIRST/FINDNEXT calls. Blech. :(

      --

      dragonhawk@iname.microsoft.com
      I do not like Microsoft. Remove them from my email address.
  5. The JIT is available NOW ! by ZioPino · · Score: 3

    And you can download it for free from here

  6. Why JBuilder first? by minority · · Score: 2

    I'm so happy for the coming release of Delphi and C++ Builder for Linux. But I don't understand why Imprise take JBuilder for Linux as more important.

    If Java is really "Write Once, Run Anywhere", it is not so urgent for Java Programmer to write java under Linux.

    What linux is really lack of, is the RAD tools, especailly for in-house development. If we want the company replace all the win9x inside the Desktop, Delphi or C++ Builder should release first.

    1. Re:Why JBuilder first? by ZioPino · · Score: 2

      It's not a matter of importance, for us all our products are important, we are not language bigots and that's why we support Pascal, C++ and Java. The point is that the current development version of JBuilder is written 100% in Java so we can release it to Linux as soon as there is a JDK for this platform and we finished writing and testing the program. It's also important for a lot of people to have a tool that runs on the platform of choice. Being forced to use another OS than the one you are targeting is not much fun.
      Sure you can use today's versions of JBuilder on Windows and deploy on Linux but being able to do all your development in Linux is another story altogether.

      Delphi and CBuilder are native applications and so they require more work to be ported. It's just like this.

      Take care,

      Paolo Ciccone
      JBuilder dev. team.

    2. Re:Why JBuilder first? by ZioPino · · Score: 2

      Is the recent licensing announcement with Microsoft going to affect Delphi & CB on Linux wrt MFC?

      The MS Borland license issue doesn't affect the Linux projects as we said at the time of the announcement.

  7. Can I write free software in it? by Zachary+Kessin · · Score: 3

    If there is a way that I can use it to write
    free software I am interested. If you need a copy of Delphi to compile it the resulting code is not
    free software. Maybe they can offer a runtime lib as free software so you can't use the real nice desing tools without paying for them, but anyone can re-compile apps.

    On the other hand for "In House" apps it will be nice.

    --
    Erlang Developer and podcaster
  8. It's a first step by Le+douanier · · Score: 3


    You may not want to trade your liberty for a good software but they are a lot of people that are bound to closed software right now. This is the first step to allow them to expand their view to free software as well.

    To paraphrase RMS, it is better to have closed applications on a free OS than free applications on a closed OS. With Linux (and *BSD) we control the foundations to build free applications on and these are strong foundations. RMS did the right thing by beginning to create a free OS rather than free applications .Ok, he began with Emacs but this was necessary to the creation of a free OS whereas a word processor or a spreadsheet would have been useless for this purpose.

    --
    "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  9. Re:This is a Good Thing (tm) by bmetzler · · Score: 3
    This is definitely a chink in Microsoft's armor. One less reason to stay with Windows.

    Yes. In fact many developers who like RAD tools and are afraid to get their feet wet in real programming have stuck with Windows for just this reason. There was no "easy" development tools for Linux. But now there is.

    In a year, we should be seeing a lot of development going on in Linux. Helped, of course, by the fact that the code will be cross platform compilable. That's important too. Not just the tools on Linux, but the ability to compile the code you developed for Windows on Linux. "When Kylix is released, virtually overnight there will be hundreds of thousands of applications available on the Linux platform, and many will be ports from Windows,"

    I can't wait for the preview...

    -Brent
    --
  10. Why this is a good thing. by Pont · · Score: 2

    It is important to realize that Delphi is much different than Visual Basic. Delphi is pretty much identical to C++ Builder (actually CB is based on Delphi). Delphi does not use an interpreted language like most RAD tools do. It generates native code.

    The major benefit to using Delphi is that you can just plop down a **very** nice gui and have it work with no bugs. That lets you focus on the guts of your project. I don't know how many times I've used a GUI app on Linux that does it's job well, but has a crash/core dump bug when you pull down the wrong menu and click in the wrong place.

    Delphi being released Open Source? Never going to happen. If Borland is smart, they'll release a free (at least as in beer) command line compiler so that people can compile projects written in Delphi. If you take the open source away from linux, you have nothing. Therefore, if your development tool is too expensive to be used for open source projects, the project leads will stay away from it.

  11. For the OSS-people... by robinjo · · Score: 3

    Many of you don't like Delphi for Linux because it'll probably be commercial and closed source. You are totally free to have that opinion but how about putting your programming where your mouth is and contributing to the Lazarus project?

    Lazarus is the class libraries for Free Pascal that emulate Delphi. They are also making and IDE. So check what you could do.

  12. Re:Good news, bad news by DragonHawk · · Score: 2

    I have my doubts that it would be an open-source compiler.

    Of course it is not going to be an open source compiler. Not everyone cares. Me, I would be willing to pay for a quality RAD tool for Linux. RMS does not like it; that is his prerogative. So far, Borland's tools have done me well. If they stop doing that, then maybe I will start campaining for an OSS GUI IDE.

    CBuilder is not that great of a product. [...] More often than not, the "reqirements" for CB4 to make and run my program get in the way of the actual design of what I want. It is not for the faint of heart users.

    I am curious as to what the problem is.

    If you are looking to build a traditional C/C++ program, then you are better off with the command-line C++Builder compiler, BCC32.EXE. Treat it like GCC and you'll be in good shape. Be sure to specify the "target" as a "Console" app, or it will not work. (This is the fault of Windows, which does not provide main(), amoung other things.)

    If that is not the problem, what is? Let me know, I may be able to help.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  13. Some thoughts, open and closed by evilpenguin · · Score: 3

    I tend to think that programmers, for the good of all programmers, should stick to 100% open tools built using GPL'ed tools and libraries because I believe in and hope for an evolution of programming into a true profession like medicince and law where all the code (laws, medical techniques) is (are) open and more or less freely available and it is skilled people who are valuable. Software is only valuable as a product because compilation is, in effect, encryption that hides technique. It makes programmers into manufacturers, wholly dependent on their salaries from companies owned by people who can't code at all. In a world where software is difficult and expensive to distribute, this was natural (and perfectly okay in my book -- I'm not a socialist).

    We are now, however, moving into a world where software is easy and almost free to distribute. The software "industry" is no longer economically necessary. In fact, I think its a dinosaur. An antique. I truly believe that we will all be more productive (and rich) when all software is free because programmers will become people valued for their skill and productivity alone. We will all be able to use one another's knowledge (just as doctors and lawyers do now) so we can spend less time doing the same things over and over again. The pace of programming innovation will accelerate dramatically and the economic benefits of computing (faster business cycles and lower costs) will be magnified by that amount of time we no longer spend building the same basics at every employer and we instead concentrate on making existing software fit the local need.

    All of that said, that is not yet the world we live in. While I want us all to be using open tools, a lot of businesses have a heavy investment in specific "enterprise" technologies such as Delphi and C++ Builder. I for one welcome these tools on the Linux platform. I'll prbably use them in my workplace.

    The software I develop for the open source world will still use the GNU tools and be GPL'ed and use automake/autoconf and be written for maximum portability.

    I also look forward to seeing tools like Kdevelop continue to mature.

    While the software industry lives, let the commercial vendors come. Just try to keep your skills up in the open tools too.

    This is what makes free software unstoppable. The commercial interests can take over the business market through the gullibility of the PHBs, but no one can take away your gcc, or stop you from giving away your own code.

    I believe all software will one day be free and that it will be considered fiduciary misconduct to buy an operating system, but until that day, there really is room enough for us all.

  14. Closed Source Is Good For Unix by LHOOQtius_ov_Borg · · Score: 3

    This is a great announcement. Borland's tools are great, and in a cross-platform development house like ours, it'll be great to eventually have people on multiple platforms using at least some of the same tools (if only we could get Solaris versions). People here who are familiar with Windows environments only may be convinced to move over to Linux as more tools *they are already familiar with* get ported to Linux. This is a Good Thing (tm).

    If we could move 50% or more of our developers to Linux or Solaris, I'd be very happy. I'd like to see managers like myself be able to make the transition also. Such a transition, though, would require the availability of necessary evil tools such as project management software available on UNIX/Linux (and with the same level of functionality as, say, Microsoft Project and Rational Requisite Pro).

    Whether or not these tools are open source is irrelevant to my bosses, who are making business decisions, not community outreach decisions. Our technical department actually does support Open Source software, but we also know that when a job needs to be done, if the best tool is not open source, then get the closed source tool...

    What really matters is not the licensing model of the tools, but their availability on the platform. Businesses are used to having to decide whether or not to accept stupid licensing terms, but they like to have the right tools to choose from. Lots of developers use Delphi on Windows, and if they use it on Linux, also, that is good for Linux, whether or not their software is open source.

    It would be nice if all software could be open source, but that is not the reality of our current marketplace, and so if Linux wants to continue to expand its user base, this is indeed good news.

    Maybe Borland/Inprise will even change some of their licensing to allow free software developers to redistribute Borland runtimes libraries with freely redistributable software, and to allow open source distribution of code generated using their code generation tools. Incidentally, Frameworks generated by, say, C++ builder, should already be open sourcable since a developer will add and modify it enough to create most programs to make the copyright their own - though I haven't looked into the fine print on the Borland/Inprise licenses in the last 5 years...


    --
    o/~ we are pissed, we are pissed, we have to resist... o/~ - ec8or
  15. Re:OWL included w/ C++ Builder? by Amphigory · · Score: 2

    IIRC (it's been a while) it's only included in the professional editions and is not installed by default.

    OWL is wonderful if you already have code written in it that you want to port. (I occasionally see an app with the giveaway OWL "check" button)


    --
    -- Slashdot sucks.
  16. Re:Good news? Isn't this the beginning of the end? by aphrael · · Score: 2

    You raise some interesting points, which I (perhaps incorrectly) summarize as follows:

    (1) High-level development environments help non-programmers pretend to be programmers and so are bad (in the sense that many of the problems with commercially available software are due to "programming" by these "programmers").

    (2) Proprietary software is of its nature untrustworthy as it is impossible to tell whether or not what is actually being done and what is claimed to be done are in sync.

    (3) The use of proprietary high-level development software on Linux will destroy the advantages that Linux has over Windows.

    None of these are particularly new arguments, and I have sympathy on some levels for them. But I submit that you have overstated your case:

    (1) Even if RAD enpowers poor programmers to write bad programs more quickly, the logic of open source overcomes it: in an open-source environment, programs developed via RAD will be just as open to review and fixes by other programmers. In fact, arguably open-source communities should be immune to this particular danger --- the more seasoned developers in the community will fix the mistakes of the newbies, who should learn from it.

    (2) Proprietary software may require a higher level of scrutiny than non-proprietary software. But as long as the tools to analyse the software exist and are reliable and trusted, this shouldn't be a problem. [You say: "can someone also tell me what this Delphi release -really- puts into the binary?" ... But that should be verifiable via other tools on the market.]

    Now, granted, there is a greater _time_ investment in running such verifications. But, for the average programmer, the time hit is no greater than that involved in reading the source code to their development tool --- moreover, the average programmer doesn't do that anyway, they just go off of the reputation of the tool. (That's true even now; the days when every linux programmer was a kernel hacker are behind us).

    (3) The advantages Linux has over Windows are largely in server software and the kernel, not in client-side user software. That's beginning to change, but remains largely true. Even if all of the things you fear about proprietary RAD tools were true, their use in client-side software would hardly destroy the advantages Linux has over Windows; moreover, such tools won't be used in kernel development _until the parts of the community responsible for such development believe in their efficiency_. In other words: they'll only get the chance to destroy Linux's advantages if they work well enough to be given that chance, in which case it's unlikely that they'll actually do it.

    Badly implemented proprietary RAD software could easily have the unfortunate effect of splitting the Linux community into multiple camps: old-school programmers focusing on the kernel, system-level software, and server-side software, and RAD programmers focusing on client-side end-user software. That would be bad, as it would encourage the two communities to grow in different directions and result in a dichotomous view of what the OS should be ... but it would hardly be the vision of the future you appear to be worried about.

  17. Re:Theres a difference. by Daniel · · Score: 2

    Linux can live without GNU.

    su -c 'rm -f /bin/* /lib/libc.*'

    Daniel

    --
    Hurry up and jump on the individualist bandwagon!
  18. The BDE is much better these days by DragonHawk · · Score: 2

    ...the BDE is buggy as hell...

    While past versions of the BDE have been rather unstable, newer releases are much better. I had no problems at all with BDE V5 (Delphi/Builder V4).

    It's the main reason my company switched over to C++.

    The BDE (Borland Database Engine, for those who don't know) is a library. It is independent of language and compiler. Object Pascal or C++, it does not matter.

    Now, if you mean that your company switched to MS Visual C++ and DAO, fine, but say so. (Although I find the idea of switch to DAO to avoid bugs hilarious.) :-)

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  19. Re:A giant step closer to world domination for lin by IntlHarvester · · Score: 2

    I think you hit the nail on the head.

    One can imagine a future where a free software platform of Linux, KDE and/or Gnome, KOffice, etc. could actually be considered a competitive business desktop to Windows/Office for $500 cheaper. The big hitch is the inevitable in-house corporate applications written with VisualBasic, Delphi, VC, DBase, Lotus Notes, etc. Wine might be an answer, but obviously, the Delphi people are now in the best position to save some money on desktop software when the time comes.

    Products like this, while not "free" are a critical piece of the free softwar puzzle simply because they open the door for migration.

    Furthermore, my guess is that Linux support will appeal enough to IT managers that this move will increase Borland's Windows product sales, just so shops can hedge their long term bets against a Windows desktop.

    --
    Business. Numbers. Money. People. Computer World.
  20. Different goals for different people by jflynn · · Score: 3

    You seem to be interested in developing on a completely free platform as an expression of idealism. Noble enough goal and I can see how Delphi wouldn't impress you.

    Others are interested in the actual capturing of majority or total market share by open source software. This is a different goal, it tolerates the expediency of closed software for a later good or special circumstance, but still maintains open is always better when possible. For these folks, Delphi is expedient, get a lot of converts to an open OS now, replace Delphi with completely free tools later.

    For some, open software fits some needs, closed software fits others. They may be strong Linux advocates, but they are neutrals in the proprietary/open source/free software war. These people may be looking forward to Delphi as a long term tool, or at least until something better for their purpose is written.

    The Linux commercial interests are mostly closed/open/free agnostic, they need help for their bottom line now, and never mind how. They will be very pleased by Delphi for Linux, because it means they have a tool as good or better than VB for quick in-house programming by high level programmers. This covers a lot of business programming. This might help GM believe that their VB apps might port in reasonable time for example.

    Then there is Microsoft, who will not be pleased at all. One of their biggest problems right now is loss of developers, and having Delphi and C++ Builder waiting will mean that developers can switch to Linux, or *BSD probably and be productive immediately thru RAD development.

    I don't think of any of these being "wrong" just different approaches to meet different goals.

    Personally, it's my belief that open software is a scaling phenomenon. It works better the more people are involved with it. Makes for more testing, shallower bugs, more new ideas, more developers working at once, more common software to draw on, and better ability to beg driver support for new hardware. So I'm in the camp that is wanting to expand open software's marketshare, even if it takes closed software to do it. When you've got positive feedback on your side, you need to take advantage of it, not hold back waiting. There are elements out there who are actively trying to shut down open software, or ridicule it into oblivion. Time matters, unfortunately.

  21. New Information! by DragonHawk · · Score: 2

    Okay, this post is partly off-topic for this sub-thread, but I wanted to get it in near the top of the discussion when sorting by Score.

    Linux Today has more information about this, including:

    This is not a port of Delphi or C++Builder, but rather, a completely new product.

    Read the details about "Kylix" at Linux Today!

    (I would post a complete copy, but that would be stealing from LT. Don't wanna do that.)

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.