Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
News

Inprise/Borland Developers Conference Linux Nuggets 147

ghjm writes "I just got back from the Inprise/Borland Developers Conference in Philadelpha, where some results from the recent survey--as well as some actual products--were announced." Click below to read ghjm's full report on the results of their surveys, the performance of their C compiler vs GCC and more.

Inprise has offered Interbase for Linux for over a year now, which is very much worth looking at--but the problem is, the Linux version is only 5.1, where the NT, Solaris and HP/UX versions are all at 5.5, so there's been some question about Inprise's commitment to Linux. At the conference, they announced that Linux development is still going strong, and that while Interbase 6.0 would be released for NT first, its Linux release would be in the following quarter. The NT release is currently planned for mid-2000.

Inprise also announced JBuilder for Solaris and JBuilder for Linux. This is based on what they call "JBuilder PrimeTime" which is JBuilder in Java. Apparently JBuilder was originally written in Delphi, and over time they have been porting pieces of JBuilder to run natively in Java. The currently shipping JBuilder 3, which is only for Windows, is not yet 100% Java; however, JBuilder for Solaris, which will ship by the end of the year, will be. It will be followed up in short order by JBuilder for Linux in early 2000. There are strong rumors that JBuilder for Solaris was moved up at Sun's request, because they want a better development tool on Solaris than Java Workshop to prop up their hardware sales in the developer market.

With all this Linux stuff going on, there were a dozen or more Linux-oriented sessions at the conference; quite a change from last year. And of course, the Delphi team had to get their hand in. They did not make any announcements; in fact, they made it quite clear that they have not yet decided what to do. However, they did give out some results from the developer survey: The most interest is in Delphi, followed closely by C++Builder; the vast majority want a full RAD environment, not just traditional tools; native GUI support is by far the winner (as opposed to Motif or [shudder] WINE), with KDE preferred over Gnome by a small margin--though it goes unsaid that if you could have chosen more than one, everybody would have picked both. They have had 16,000 responses since the survey went on-line, which they consider an excellent turnout.

Following these announcements, they did a demo of what they've been working on so far. As many of you know, the back-end compiler is the same between Delphi and C++Builder, as of Delphi 3/C++Builder 2. What they showed was bcc running on Linux (specifically, Red Hat 6.0 using Gnome). They compiled Xgalaga with both gcc and bcc, with bcc getting the job done in a little less than half the time that gcc took. They then ran the resulting binary to show that it was real, working code. Watching the demo closely, it was also possible to see that the binary that resulted from bcc was smaller than the one gcc produced, though there's no way of telling whether this was due to smaller code or just different debugger settings. And of course the real interest is in the RAD environment, which they did not demo; the question of whether Delphi for Linux will include the VCL is yet to be answered. But it's clear that work is ongoing, and if they've already invested enough time to get bcc running, it seems quite likely that a product release will actually happen someday.

Of course, Inprise/Borland is not an open source company and all these products will be commercialware, and there are still issues to be resolved concerning how quickly they will support new kernels, libcs and distros; how nicely they will play with the other kids; how the community will react to the concept of for-pay, closed-source development tools; whether their licensing will permit you to build open source projects using Borland tools; etc; etc. There are many ways they could screw things up, and even if they do everything right, it is not at all clear that a large market exists for for-pay development tools, in the presence of really quite good free ones. However, I think the "linux market" and the "linux community" are increasingly divergent concepts, and there may well be room for Delphi somewhere in the market--if perhaps not so much in the community itself. "

This discussion has been archived. No new comments can be posted.

Inprise/Borland Developers Conference Linux Nuggets

Comments Filter:
  • by Anonymous Coward
    Would I use commercial software? depends how good it is and how good are the opensource counterparts...
    Actually, there is one commercial software I use under Linux, it's idl (www.rsinc.com)

    However, IDL's performance sucks compared to Win, probably because they use gcc as their compiler. Only this year has RSI started to use glibc2! (they were using redhat 4.x to compile idl for a lonnnnng time). Commercial software just lags behind,,, but the point is, if a compagny wants to make money out of commercial software, pleaaase, stay tuned to some of the issues in the Linux world! (like freshmeat, slashdot, whatever, pay a geek to monitor those sites for you 8-) For instance, in IDL, use bcc and intel's fast math libraries and give us something worth the 2000$ per licence we pay for it.

    Of course, I'm just dreaming, this is never going to happen.

    ---
    What have you given back to the community?

  • by Anonymous Coward
    In the not-too-distant future:

    To: Borland Guys
    From: Guy who payed for your compiler
    Subject: broken compiler

    your compiler is broken. I payed good money for it, and then tried to compile my copy of splizquux on the new IBM/motorola/digital/amd/transmeta chip (which linux has been available on for 18 months now), and it didn't work. upon disassembling the code I found that it was incorrect assembly being emitted from your compiler. Furthermore the exception handling was broken and it wasn't threadsafe. here's a detailed report on how to do these things correctly on that CPU... blah blah


    To: Lower Life Form
    From: Borland Bottom-Line Supremacy Department
    Subject: sorry

    That CPU is not really our number one unit-selling platform. It's not worth the money for us to fix it. I'm afraid it'll be a while before you'll be able to see that bug fixed, if ever. Furthermore by disassembling our emitted code, you have violated your license agreement (you must dispose of the compiler immediately) and the WIPO 2003 "Digital Consumer Protection Act". We are now going to sue you for reverse engineering. You may never use a compiler again. Have a nice day, and remember to "Buy Borland, Cause our Compiler is 0.2% faster than the Red Menace GCC!!!"

  • by Anonymous Coward
    First - the legalese : I'm an employee of Borland / Inprise but I'm writing this in strictly personal and entirely unoffical capacity. Everything I say here is completely devoid of any offical status.

    That said;-

    Yes, we are serious about Linux. We're a commercial company so we have to find some way to coexist with Open Source to our mutual benifit.

    We think we can do that and offer useful products to Linux developers and commercial users of the OS.

    As to the products; I have the Java release of JBuilder running on my Linux machine right now; and it is awesome

    I also have the tech-demo of IBM's Linux Visual Age for Java and that, too, is excellent. Which one you prefer comes down to the RAD paradigm you like most.

    Linux JBuilder needs JDK1.2 to run. VAJ is (mainly) native binaries but the two IDEs seem to run at the same speed. The JBuilder team did an excellent job of getting JB to run very fast and stable.

    As noted, our port of bcc to Linux compiles about twice as fast as does gcc. I do not have direct experience of the compilation times at present but I am informed that it does indeed run faster and produces smaller binaries. The exact gains depend on the compiler options selected.

    We also have a bunch of other stuff poised in the wings awaiting offical release...

    Cheers,
    Linc.
  • I hope Borland succeds with its development tools. Competing with Microsoft on such a fundamental product must be hell.

    Overall, I think the Microsoft Developer Conference [min.net] was a bit more lively, though. (:

  • GNU C(and friends) make fantastic embedded cross-compilers. I love them but...

    Borland make the worlds fastest compiler. There's been a lot of talk about bcc being faster than gcc but you people forget that C++ is just an addon. The real compiler is the Object Pascal one that forms the core of Delphi. Some basic experiments I have done indicate that it is 10-20 times faster than bcc.

    I can build the current system I'm working on (50k lines in 5 or so EXEs) in under 40 seconds on a PII-233. An equivalent sized(in LOC) C++ program takes somewhere between 5-10 mins to compile. This is before you see that it usually takes 5 lines of C++ where 1 line of Pascal would do...
  • by pb ( 1020 )
    Whatever, dude. It's a hash collision, and adding more letters won't help when you already have popular letters. You could also capitalize the B, under UNIX, (or is it Unix? :) or use longer names, but don't you think a better long-term solution would be to try not to use names that are already taken?

    After all, we have cc, bcc, gcc, lcc, and probably a few others, why have another bcc when you could have icc, or vcc, or cb or something. I'm sure the marketing people just spend all day thinking up better names, anyhow, put them to use for once. :)
  • by pb ( 1020 )
    In Unix, bcc is a GPL'ed compiler for producing 386 binaries. I realize that bcc has been the 'Borland C Compiler', but we really don't need more than one C Compiler on the same platform, with the same name. That's just trouble waiting to happen.
  • by BadlandZ ( 1725 ) on Monday July 26, 1999 @10:22AM (#1783243) Journal
    Even gcc and it's branches give a broad range of results [206.28.198.198], so it Borland's defence I guess, it's a hard thing to compare. How can you compare?

    The only way would be to find the best possable flags for that specific system, for that specific code (in the above case, a benchmark itself written in C). And the results would still be suspect because it would only show the results for that specific hardware, and that specific code.

    In my mind, my solution is this, if/when I want a new compiler, I realize that I have got by with gcc/egcs for such a long time, I'll find the person who is working on the code specific to the hardware I am running, and donate money or equiptment directly to that person. Only other choice would be to pay for something that is "closed" and hope they did a good job, and hope it was a value. ;-) So...

    gcc/egcs isn't perfect, and has a ways to go, but it sure is a dang good value, and I believe it will get better. When open source comes up, I belive gcc/egcs is a better success story than Linux, FreeBSD, or any other piece of software, because without the compiler, the software would never be were it is today.

  • Don't forget the impending gcc 2.95 release. I would like borland to use g++ so that it would be link compatible with linux c++ libs like mico/TAO etc.

    Remember c++ compilers are not link compatible. If you've ever tried to link to a MS c++ lib on NT from borland you will know that.
  • The VCL is a rather complex wrapper around windows common controls. I really believe that it would be possible to modify VCL to wrap around GNOME or KDE controls. Thus you could use the "C++ Builder for Linux" with either widget set.

    I've actually considered writing something like this for my own use. (IE could pretty easily port my windoze apps over to KDE or GNOME)

    Most of the code in my stuff is standard C++ and the only problems I've had porting the stuff is GUI development. I'd really like to be able to drag and drop GUI widgets in the manner Builder does it on Windows.


    Ex-Nt-User
  • Why should a KDE/Gnome VCL do Win32's right thing?

    Honestly, programmer lazyness... I'd prefer to be able to just do a recompile between a Windoze version and Linux version.

    If making a source compatible VCL for GNOME/KDE would indeed be a hack (and not "The Right Thing") I could do with some incompatibilities. Especially on new projects where I could do the #ifdef thing. And have the incompatibilities on my mind when writing the code.

    With old projects it's a different story, I have at least 6 apps that would be worth porting. But I wouldn't have the time to invest in modifing them to compile for Linux. Thus the usefulness of such a tool would decline for me.

    Ex-Nt-User
    ps. Just for the record I would prefer a VCL that would do the right thing.

  • I'm stuck writing code for NT at work. I'm working on some Linux code but it's not officially sanctioned. I'm doing it to prove to management it can be done and work as well if not better then NT.

    Most of the code is done in C++ Builder because the GUI development is extremely fast and flexible. If Borland would release source compatible VCL and C++ Builder for Linux I don't think my management could argue againts doing everything in Linux. On top of that I could just re-compile all my apps to Linux in not time.

    Ex-Nt-User
  • Edit-and-continue is indeed a feature of VC++ 6.0, but it does its magic by including empty space in the executable and using this space to patch the .EXE. (See patch space in the Jargon File.) Hence, it's precisely equivalent to VB, where its edit-and-continue comes as a virtue of it being an interpereted language; not only that, but edit-and-continute is not going an option for a release build. I find that gcc's "-O2 -g" gives a reasonable compromise for testing new code.

    Edit-and-continue is all very well, but in my experience with VB (admittedly not extensive) in about 50-70% of cases where I make a change to a running program, it needed to be restarted. The kinds of errors you tend to make will dictate how useful edit-and-continue is to you. For instance, if you alter a template definition, it's likely that a rebuild will be needed.

    As for me, I tend to build about once an hour or so when I am writing and debugging extensively. Otherwise, I try to write the entire class or module and understand that it is correct before I build it.

    Excuse me if this is slightly confused; I'm a tad tired.

    Paul.
  • OK, so bcc compiles twice as fast as gcc for their tests I wonder how long they took to find something (xgalaga) that gave them the results they wanted? Either way, quite a gain, although I suspect it'll be closer to ~30% faster for real life projects.

    However, compilation times and executable size are nice, but the real test will be runtime performance. Unless it produces faster code, no-one will use it...

  • Would I use commercial software?

    Sure, I don't mind using (and paying good money for) commercial software... as long as it comes with source-code. I strongly prefer an open-source licence, but I do understand there are buisness constrainst that come into play. I'm happy as long as the terms of the licence are flexible enough to allow posting small chuncks of questionable code for review, discuss possible changes with other users/developers, post patches to the code to fix probelms and add features, and to be able to (at my discression) submit those patches to the company for possible inclusion. Buisness don't seem to see that there is demand for commercial applications with source code.

    If you don't let me see the source code, you don't trust me. If you don't trust me, why should I trust you. If I don't trust you, why should I trust that the code you write does what you say it does, and doesn't (by design or by accident) reek havock on my machine. If I don't have confidence that your software won't trash my system why should I pay you money for it.

    I was listening to an audio coulmn on KNX radio yesterday by Michael Josephson [charactercounts.org] called "Character Counts" [charactercounts.org]. In yestedays column (which is not on his website yet) he reported (unhappily) about a buisnessman at one of his seminars who (when he brought up the topic of keeping promises) described the decision whether a buisness should keep a promise (such as what a software package will do... and not do) as purely a cost-benifit analysis of the costs of keeping the promise vs. the cost of breaching it. With ethics like this floating around the buisness world, it is not reasonable for me to trust that what a software company says it's products do is, in fact what they do. According to this buisnessman's arguemnt, if his company deemed that it would make them more money to have their software cause a problem on my system (unbeknownst to me) so that I would need to buy another of thier products to fix it, then they would do this.

    I spend alot of money on my machine each year, but it's not worth my time to spend any of my money on commercial software if it doesn't come with source code, although I'm more than willing to spend good money on commercial software, that I believe I would find useful, if it includes source-code.

    Software isn't software without source code. -- NASA
  • Just for the record, I had to mine the majority of this message out of /proc/kcore because netscape hung on me just before I was about to submit it. Thanks to jeff on #slashdot (slashNET) for help on that.

    See what I mean about closed-source software... (in this case Netscape...) You can't trust it.

  • And I don't think they're really trying to put down gcc

    That was not the intention, we are tring to add value to our products and speed, both compilation speed and speed of the executable, is generaly very important to compiler users.

    Just my, very personal, $0.2.

    --Paolo
  • Comment removed based on user account deletion
  • I wonder if it will compile the kernel. I am curious as to the difference in size and speed of a gcc-compiled and bcc-compiled linux kernel.

    Is the kernel gcc-specific?

    It would be interesting to try on things like X11 and window managers; things of that sort.

    -Gabriel
  • I personally think that any figures this early in the dev cycle would be silly.

    much better to wait and compare two release compilers :)
  • lazarus is aiming to produce a delphi like environment (not there yet but they're moving fast).
    It's available here [pcpros.net].

    It's using Free Pascal [kuleuven.ac.be] as its base.
  • "you can stop at a breakpoint, change the code and carry on running "
    "Would I want to see it in Delphi or C?"

    FYI, edit-and-continue is a feature MS VC++ 6.0.
  • I fail to see what the winblows API has to do
    with a bcc working under Linux.

    I would think of the borland compiler much
    like the dos or OS/2 compilers. They are
    tailored for the particular environment.

    I've always like the Turbo and Borland products
    can't wait to get my hands of their Linux
    versions.
  • No. The demo was on the big screen at the convention center ballroom. There was no opportunity to inspect the setup or see much of what was going on.

    Remember, it's very early in the development cycle. Who knows what kind of jury-rigging was used to get it to work at all. And I don't think they're really trying to put down gcc. They just want to show that they have a compiler and it has strengths. We'll have to wait for an actual product before we can really see what the deal is.

    -Graham
  • by ghjm ( 8918 )
    Borland's compilers have been called bcc for longer than the GPL'ed bcc has existed. If someone has to change their name, shouldn't priority go to the older usage?
  • by ghjm ( 8918 )
    Me too, actually. And while I was never an OS/2 fan, a lot of OS/2 people are quite unhappy about the way Borland dropped that platform. It's true that Borland could burn a lot of people by shipping a Linux product and then dropping it later. But the interesting thing is, they will then have done a lot of work teaching us (the community) why a RAD tool is useful, how it should work, etc, etc. If they release and then drop a Delphi-for-Linux, they'll have done a great deal towards the free Delphi-clone-for-Linux project that will result. Nothing like a huge number of frustrated developers with an itch to scratch...
  • For one, I'll walk over hot coals for a linux compiler that will do Object Pascal. I've got about 100K lines of code, all of which is back-end business logic for massive multi-dimensional data processing, and I want to run it on Linux BAAAD.

    I don't care about UI's and widget sets. We're going to wrap a Java/Web interface around it anyway.

    I'll probably get flamed for this, but I personally think that Object Pascal is a better OO language than even Java. (Damn sure it's better than C++) One word: Properties. I _miss_ properties when I'm programming in Java. I shouldn't have to care whether I'm assigning a value to a variable or calling a setter method. That peculiarity of the implementation should be hidden from me, goddamit! Ok, maybe Delphi need's 'interfaces' the same way Java has them, but Java needs Properties.

    I truly hope Borland commits to Linux. They've been building the best PC compiler tools for at least a decade, and there's a lot of good code written in their tools that it would be good to port.

  • bugbear 3001 wrote:
    ...111...
    111?

    I don't understand.

  • Nice story. Had me fooled for a few seconds.

    D

    ----
  • ..on a big projet, where one developer has his libraries on a different drive? That damn project files insist on hard coding paths. VERY annoying. Even after switching to CVS for code management this behaviour is still a problem.

    Now, go try a mixed language project with VS - when you want, say, your Java and C code browsed. Does not work right, does not it? Go try Source Navigator for that - just don't use the default editor - link it to x/emacs. Now that an IDE.


  • emacs is the best IDE for C/C++ development. Emacs gives me syntax highlighting, auto-formats code, can do recursive file searches for #define's, variables, and function definitions (etags are the best), it can jump blocks of code, match parins, match #define's and #end's, etc. I used to use VC++ and Borland C++ editors - I just have no need to any more. I can do everything in emacs (including compile, and debug using gdb) just as well and I don't have to deal with awfull project files and auto-generated 10K makefiles that are anything but usable.


  • Relax, everyone knows that AOL ripped off IBM's innovative OS/2 SHIFT+INSERT technology, which failed only due to POOR IBM MARKETING!!!!

    I'm sure Apple is somehow to blame too.

    --
  • I noticed one of the options on the developer survery asked whether there was any preference for using existing open source tools.

    IMHO it would be very nice if Borland/Inprise used GCC and the other GNU tools as a backend (and submitted improvements to their code bases as needed!) while using their IDE and RAD tools on top. I think people would pay for this, the community would benefit from some source improvements, and there would not be the overhead of supporting another compiler. Metrowerks seems to be doing this with their Codewarrior "GNU edition." Does anyone know how well this works?

    Borland would have to be careful not to violate the open source tool's licensing, but this shouldn't be impossible.

    -OT
  • This is definitely a step in the right direction. We need more RAD tools for Linux, especially if we want it to grow effectively. There's Appgen, which I've never tried, but Appgen seems to be pretty much proprietary (use Appgen-developed apps with Appgen developed DBs). There's Glade, and KDevelop, but I don't think you can really consider those to be enterprise level applications.

    What would be nice also, is if Sybase could port Powerbuilder over to run/compile on Linux. It is, to me, unrivaled as a GUI application development environment.

    Kudos to Borl--Inprise, and hopefully they run ahead of schedule. I'm sure there will be a very nice market for commercial development apps, plus it will add a bit of diversity to the compiler world for Linux. Just because it's not free, doesn't make it bad...

  • My PB 6.0 Professional was only $100. Not sure why you would need to pay $3000 for a $100 product.
  • by Me2v ( 12239 ) on Monday July 26, 1999 @08:36AM (#1783271) Homepage
    Not to burst your bubble, but... I spent all last semester deep under the waves of the raging ocean known as VC++ 6.0. I was beset on all sides by hordes of MFCs, each one trying to suck the life out of my slowly dying body. My attempts to write embedded SQL were thwarted at every turn by unnecessary and overly complicated layering and so-called 'encapsulation' (is it really necessary to split a SQL statement into ten different parts, each with it's own function, and then join them together at some unforeseen juncture in time and code, yet hiding that juncture deep in the bowels of some dll where even a deep-code diver is afraid to go??). I've had gray hairs popping up all over simply because of that one development environment. Trying to get the code to behave as I wanted was next to impossible. Plus, excepting a $1000 library, there wasn't any way to manipulate (store, save, view) image files other than MS formats.

    As for GUI development, VC++ is really not any good in that environment. After having use Powerbuilder and (shudder) Visual Basic, I can't see any reason at all to use VC++ for GUI development. And now you have an interface that mimics VC++?? For shame!! Everyone is entitled to use what pleases them, of courses, which is one of the guiding principles behind Linux, but what we need is not imitations of life-sucking programs which Microsoft foists on the public, but innovative new programs which foster RAD, or for companies to port existing excellent software over to Linux, like Inprise is doing.

    That being said, let me qualify by saying that I've never tried Kdevelop, and probably won't ever, because it requires Qt/KDE, and I have enough libraries without adding another set + desktop environment.

    Still, anything that reminds me of Microsoft on my Linux machine is summarily deleted.

  • Regarding the bcc name clash:
    Most of the java compilers I see are called javac. There are other examples of name clashes out there that I'm too lazy to dig up. It's just an executable name, not a product name. If you develop regularly with both the Borland C Compiler and this 16-bit compiler, you might have to go out of your way. The rest of us can set a link to the one we use and forget about it.
  • People seem to view Windows-style development tools as one of the better aspects of Windows. But I suspect they are actually at the heart of what has made Windows such a mess.

    Windows-style development tools allow both the API designers and the application programmers to delay facing up to, and fixing, serious design problems with their systems.

    For example, the MFC class libraries have serious problems in their inheritance hierarchy, but rather than fixing them, Microsoft just adds a bunch of wizards to their development tool to do manual delegation.

    Similarly, the VC++ GUI design tools result in GUIs that, for the most part, use fixed layouts that don't work well at different resolutions, and they generate code that is difficult to maintain.

    To me, Windows-style development tools give the appearance of making development easier, but in the long run they have a negative impact on the quality of both the OS and the application code.

    Bringing a lot of the Windows development tools to Windows risks bringing Linux down to the same level as Windows. I hope that the traditional Linux community will be strong enough to keep those kinds of influences from doing real damage.

    Linux development tools aren't perfect, of course, but I think Windows-style development tools are the wrong place to look for improvements. We don't need more windows or buttons, we need better tools support for specifying, composing, analyzing, and verifying large software systems.

    (In case you are wondering, yes, I have developed in VC++, Borland, and UNIX, and I'm currently a full MSDN subscriber.)

  • by jabber ( 13196 ) on Monday July 26, 1999 @06:48AM (#1783274) Homepage
    Has anyone tried FreeBuilder (www.freebuilder.org)? How does it compare to JBuilder? It's supposed to be pure Java, and running on Linux now...
  • Don't. Last thing you need is wondering if it was your fault or your IDEs ( specially, when trying to learn something)
  • That isn't even that funny ...

    ( by the way, gcc also has bugs ...and is much much slower than your average comercial compiler)
  • VC IDE is very nice to develop with... I have talk with many people and they agree, it is just about best IDE for C++ available ( MFC is a different story)
  • From what I have heard, under certain circumstances, it is not uncommon for a company to use one compiler for development and another one to produce production builds (internal releases, betas, final releases, etc.). You pick the compiler that gives you the fastest compilation time for development and the one that produces the smallest, fastest code for the final thing. Of course, in this day of wholly incompatible compilers and ultrafast desktop machines, this isn't so common any more, since you would spend more time making the code compile on two compilers (at least as far as windows is concerned) than you would save.
  • yes it would be cool to see Powerbuilder on Linux, but hte license for NT is already $3000, could any linux user really affor this or woudl they be willing to shell out the bucks?
  • --but the problem is, the Linux version is only 5.1, where the NT, Solaris and HP/UX versions are all at 5.5, so there's been some question about Inprise's commitment to Linux.

    IIRC from discussions at news://forums.inprise.com/interbas e.public.linux [inprise.com] and news://forums.inprise.com/interb ase.public.general [inprise.com], InterBase 5.6 -- and that would be final release of 5.x codebase -- should be released for NT and Linux at the same time.

    If this rumours happen to be true, this release would be any DBA's dream -- imagine a product with feature set freezed, and bug set seriously restricted.

    All in all, one can hardly question Inprise/Borland commitment to Linux after all this.

  • Why on earth not? Compiledd languages frequently also have good Interpreters. (It's also true that some interpreted languages can't be compiled... but that's different, and sometimes they are good choices too, depending on what you do)
  • Anybody else notice that this is the first wide-spread survey regarding developer mindshare of GNOME and KDE? Seems they're about even, which I suppose is a good thing. Sure, the statistics are probably biased (maybe one group hates Inprise or commercial software more than the other; maybe one group hates surveys), but it is neat to see.
  • You heard correctly. The ANSI standard does not specify a format.

    SOS : Standards Often Suck
  • Yes, the VCL is key, but as C++ Builder also parses and compiles Object Pascal, the real issue is replicating the functionality on top of GTK or some other widget set.
  • Inprise/Borland is about 4 miles from here as the crow flies -- 10 miles for my aging Volvo. I was there a couple of weeks ago for a visit, and got the grand tour, besides.

    There's quite a lot left of Borland, and it is very much alive and well. I have used their stuff since Turbo Pascal 1.0 on CP/M, and have made my living using their tools for about 16 years now.

    Imagine how long it will take me to decide to purchase Delphi for Linux!
  • Yes they are, and I can hardly wait. As to Java, however, I must disagree with you. Coming from the Windows side of things, emacs is as arcane an approach to editing as I have ever seen, and frankly, my habits in editing are so entrenched that I will simply NOT change editors now, other than to something simple and transparent.

    Linux lacks a good RAD tool, and is woefully lacking in thorough docs for developers. True, the source is all there, but people, I am not looking for a hobby -- I'm moving to Linux to develop apps. And if I must invest months in understanding the platform, then I'll switch to BeOS instead.

    Case in point: the serial programming HOWTO is weak, hasn't been updated in 18 months, and is acknowledged by its author to fall short of the mark. I use serial I/O in all of the apps which generate my livelihood, so imagine how happy I am to see that.

    On the other hand, I have an excellent serial I/O component in Delphi, and I look forward to seeing it ported to Linux.

    I'm not here to develop tools, but to develop apps. To do that, I need reliable and mature tools. Delphi is one such which serves me well under Windows. I will race to buy it on Linux!
  • Just to keep it simple: VC++ sucks. And it has since 1.0.

    Delphi has been intuitive since 1.0.

    VC++ is like a drug habit: debilitating.
  • Components which are wrappers to Windows controls will have to become wrappers to widgets under Linux. Components included with Delphi will have correspondence to elements of most, if not all, GUIs.
  • commercial bad

    free good

    As one who has observed Borland since their beginnings, I can happily state that I trust their work, their eithics, and their concerns for quality. I have used more high quality products from Borland than from any other vendor.
  • I not only don't want to have to cross compiler brands, I'd very much prefer a good compiler which is controlled by a single vendor. No committees, no camels. Delphi is my tool of choice. Lean, mean, and very capable. Well designed, well supported, and well documented.
  • I've thought along those lines, too, but then we would be asking Borland to a) abandon their already excellent and carefully honed compiler, and b) undertake to base their corporate success in Linux on a compiler they will first require months to analyze.

    Borland has a responsibility (whether or not the open source radical fringe can appreciate it) to preserve the value of the company to its shareholders. That's not a policy; it's a law.

    Besides, I fully expect the Borland compiler backend to perform as well as, or better than, gcc. Borland has had to keep tuning in the unending battle with M$.
  • by wmeyer ( 17620 ) on Monday July 26, 1999 @01:31PM (#1783292)
    Borland has a strong compiler, which has always done well in performance, both compile time and run time. It has also done well in ANSI compliance, and as it has been the common back end for Delphi and C++ Builder, Borland's commitment to making it good is the at the core of their business.

    Borland also has, in Delphi and C++ Builder, strong RAD tools which will make it very easy for thousands of Windows programmers to move apps to Linux, furthering the growth of the Linux community.

    The range of their questions in the survey, and their willingness to publish preliminary findings shows that they are committed to delivering what the market seeks.

    As to commercial software, I welcome paying for a great tool, rather than getting a good one for "free". My time is worth much more than I will pay for the tool, and my experience with Borland tools gives me confidence that lack of source access is not an issue.

    Borland's VCL has not been open source, though developers do have source access to most of it. There are patent issues involved, and I would expect to see the source access to the VCL remain much the same under Linux.

    I have already invested thousands of dollars of my time in Linux, and am not yet ready to try to ship a product. If I had Delphi, or C++ Builder, I would have reduced that investment by an order of magnitude, and would be hard at work on my applications.

    Please, Borland, move with all possible speed!
  • There is one thing that your report does not mention about the gcc vs. bcc comparison: was there any way to compare the speed of the compiled code?

    It is nice to know that bcc compiles faster than gcc. This is interesting for those of us who are writing code and compiling all day. But when the end users install the software on their machines, they mostly care about the speed of the executable (compilation time does not matter much).

  • by Arandir ( 19206 ) on Monday July 26, 1999 @07:01AM (#1783294) Homepage Journal
    I don't see a huge difference between the linux market and the linux community. They are mostly one and the same. There will be some people who aren't in the market, refusing to buy anything, and downloading everything. These people are rare (even 1.89$ for a distro disk counts as a purchase). Then there will be the truly clueless who buy JBuilder for Linux to run on their WinBox. Everyone else is both using Linux and buying stuff for Linux.

    Yes, there are hardcore Linux users and lightweight, parttime Linux users. But they are both part of the community.
  • Ok, this is probably off topic but it could be useful if someone is wondering whether to love or to hate Borland.

    They had an excellent TUI complete with buttons, windows, pop down menus, radio and check boxes, text editing, etc. It was extremely well thought out and unbeatable for C++ development/learning in text mode. Worked both with mouse and keyboard.

    They now distribute it freely. I couldn't find a complete license agreement but you should be able to develop BSD style licensed programs with it blazingly fast (at least the UI when you become acquainted). It is now ported to Linux though I haven't had a chance or trying it but you can download it here: [unc.edu]

    Even in DOS days when I bought BC++ 3.10, TVision came with its complete source code. I made a database program combining it with Paradox Engine. The whole thing worked flawlessly without a memory manager, i.e. with less than 640 kB. I plan to do the same thing with some free SQL in Linux one day.

  • There's a lot of issues that come up when a commericial compiler will be available that is likely to become very popular. I'm willing to bet that lots of people would buy Delphi for Linux (including myself). But, I want the apps that I write to be runnable on alphas, sparcs, ppc, as well as x86. Normally, with gcc, this isn't a problem -- you simply distribute the source with your app and let them compile it... or get a friend to do it if you're weird. There's one thing that you CAN assume -- that almost every Linux user will be able to use your app... because almost everyone has gcc.

    Now, with Delphi I don't think you could do this. I don't know how I'd be able to ensure that Linux/Alpha users would be able to use something I programmed in Delphi. So, I came up with one idea.

    What if Borland freely distributed their compiler that handled Delphi source code, for all Linux platforms? Maybe they're already planning on doing this, but I'm not sure. Anyways, they could still sell the RAD environment and the tools. This way, you could even write open source Delphi applications.

    One problem with this is that people would be able to code without the RAD environment, and just edit the source files.. and thus not needing to buy Delphi. But I'm sure Borland could figure a way around this.

    So, to conclude, I guess what I'm trying to say is that Borland should seriously consider the ability to produce applications that can be ran on all Linux platforms, not just x86 / glibc2 / qt / whatever.
  • Unfortunately, it's not quite there yet. Even more unfortunately, I haven't seen any change in their web site in months. It doesn't have a class parser/class browser, which is really the key thing that I need in an IDE. The stub code is there for it to be added in, but the project seems a little stalled.
    Check out www.netbeans.com. They have a pure Java IDE that's actually quite good. Also free for non-commercial use and/or trial.
    --JZ
  • I use KDevelop almost exclusively now. There are maybe 2 or three crashing bugs that I've seen, but most of those are rare and/or fixed in CVS versions. It is by far the best way to learn about KDE/Qt programming, because it includes great documentation and an AppWizard to get you started.
    Needless to say, I'm a big fan.
    --JZ
  • I really wish the guys at Troll-Tech could work out a licensing agreement to make a version of Qt price-competitive with commercial Motif. I mean a Unix-only version exactly like Qt-free, but with a license to let you produce commercial software with it. It's an amazing product, and we could see Borland QtDelphi and C++-builder with Qt-GUI. Mmm...
    Commercial and free development can, indeed must, exist side-by-side.

    BTW: Whoever mentioned that they like Visual C++ should check out KDevelop (www.kdevelop.org). Its interface is basically identical to VC++.
    --JZ
  • Probably. Of course, getting $125,000,000 from Microsoft (see Inprise's press release [borland.com]) probably didn't hurt, either.
  • 30%? Wooh, I'd gladly pay for that!
    Borland's products don't cost so bloody
    much around here (Dublin) - around £100-130
    for Delphi or C++ Builder.

    Now, if they could release bcc with a perfect
    clone of libc, we'd get a pretty nice, fast
    kernel, too ;)
  • While I like text-mode editing (emacs, vi, pico, "cat>prog.c", whatever) as much as the next guy, something they all lack is "GUI GUI designers". That is, a GUI designer that is itself a GUI. That is where Borland's C++Builder leaves traditional text-mode editors in the dust. Designing a GUI form using the keyboard makes as much sense as writting code using the mouse.

    Of course, while Borland's IDE's text editor isn't bad, I do wish I had the power of emacs in there at times.
  • I heard that c++ doesn't have a standard for name mangling. Does bcc use the same name mangling as gcc?

    If I have, for instance, a qt shared library compiled with gcc can I use it with a program compiled with bcc?

  • Has anyone spent a little time with this program? The screenshots look nice and people seem to have favorable things to say about it, but I was wondering just how stable it is at this point (0.4, I think), and how many features are implemented. I would really like to use this program to help teach myself QT.
  • Correct me if I'm wrong, but does Microsoft charge you for using MFC/Win32API to deploy commercial applications ?
  • maybe now we'll see some other movement from other company's to port development tools to linux...as much as I hate to say it, microsoft's VC++ actully has a nice interface.
  • I don't know the exact number, but there are over 40,000 commonly used characters.

    anyway, there are several free letters in english, they could use tcc, since a lot of there stuff starts with 't' for 'turbo' all of there windows encapsulaton classes back with borland C++ 4 were 't' somthing
    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"
  • by delmoi ( 26744 )
    um, you did you know you can get rid of all that crome, right? all of those toolbars can be removed, and the individual buttons can be put wherever you want. so you can make one toolbar just for yourself.

    I've removed everything but the menubar (and I put 3 buttons on it, fullscreen, save all, and the button that shows/hides the output screen).

    but I can understand why you wouldn't know that, it's so hard *right click in the work space* and all.


    "Subtle mind control? Why do all these HTML buttons say 'Submit' ?"
  • it's refreshing to see yet another compiler for c/c++ out there. I hope people don't start thinking it's an intrusion in the unix world to have a commercial compiler.

    it seems to be that it is no longer a commercial environment with little patches of freeness such as linux and *bsd (most of at least) but a free world with some great commercial products out there as well as great fre ones.
  • I will believe it when I see it. I have a full page ad for TurboPascal for the Amiga in my library.
  • I find the best way to cope with VC is to use VC
    to knock up a project via drag 'n drop and then
    use a converter (email me for details) to convert
    the dsw/dsp files into a platform generic makefile.

    In the process it replaces the absolute path with relative paths and cleans out all the junk. To see how inefficent it is look at the dsw / dsp files in notepad.

    The other advantage in doing this is that I can automagically retarget for ming, cywgin or VC for those without VC.
  • Its nice to see that my favorite compiler-producing company is coming to the unix world. The sexiest thing that would make their products an instant sell for me is a well done RAD environment (I haven't managed to find a freeware one, and am more than happy to lay down the cash for a good commercial product).

    Its somewhat of a pity (though understandable) that they are headed to Linux instead of FreeBSD, but maybe with linux emu and a little bit of luck I can get their products running on my FreeBSD box as well.

    Hmmm. Happy days ahead.
  • The most salient question, of course, is how the binaries produced by gcc compare to those produced by bcc in terms of speed. Does anyone have any figures?
  • Further, it would be nice to know what switches were used with each compiler. Any compiler should be able to beat gcc -O6 in compile time.

  • I would agree, the VC IDE is quite fine to develop in...it has a decent feature set...but it is tough to manage larger projects with it, especially in the areas of path flexibility, components, etc.

    The libraries with VC suck for the most part. MFC is a pigdog, ATL lacks features (and neither are really portable)...and STL support is crippled with the stream libs.

    One old borland feature I do miss is syntax highlighted printouts...something which ms has left out of vc for too long.

  • You're also expressing a concern for a lot of us. As much as I would like to so Delphi for Linux, I would like to see it run on non-Intel platforms also (at least for Linux). Borland for whatever reason has never ported over to the Alpha platform (they claim not enough market for it). MS VC does Alpha and as far as I know also does PPC for MAC.

    An Intel only compiler for Linux would only be a partial and frustrating solution. 80% market share notwithstanding.
  • They'd have to release Delphi for Linux first if they were to release source compatible VCL, especially considering the fact that the VCL is basically 100% Object Pascal code.

    And if that were the case, they'd have to produce a superset ANSI-C++ compiler, because they had to hack the hell out of C++B's compiler to get it to handle Object Pascal constructs.

    But we shall see. I'd rather they just use Qt, the benefit, of course being that it already compiles/runs on Linux and Windows, and provides a similar framework to the VCL.
  • VC++ has a nice interface ?
    The Borland C++ 5.02 (I use it in college) is so much better - Clean , uncluttered and only a minimal interface.
    VC++ has to put everything on the screen, only a quarter of my screen is usually available, half at max.
  • Any word on porting visibroker/c++ ? This would be the next to last step in fully replicating my company's standard solaris environment!

    So far, they seem much more interested in convincing us to (a) switch to NT and use their builder products for visibroker devlopment or (b) switch all development to java and use their builder products for development. :-/
  • Compilers always juggle two speeds:

    1) Speed of compilation during development to make the programmer's (code-compile-debug) loop as tight as possible. Speed/size of the exe (within reason) is not an issue with these builds.

    2) Then there is the release build. On this build, speed/size of the final executable is all. Speed of compilation (within reason) is not an issue.

    One suggested tactic is to optimise both simulataneusly is to have 2 compilers - for dev and for release. But most vendors just use compiler switches to change from Debug to Release builds.

    Borland has typically been very good in both compiler speed departments.

    Thier promo material tends to emphasise the quick debug builds, but that is because Delphi has for a long time competed against MS's Visual Basic, which being an interpreted language has a compile time of zero - you can stop at a breakpoint, change the code and carry on running .
    IMHO this is one of the few nice features of VB. Would I want to see it in Delphi or C? No way.

  • > I really believe that it would be possible to modify VCL to wrap around GNOME or KDE controls.
    > Thus you could use the "C++ Builder for Linux" with either widget set

    As someone else noted, The Delphi/CB VCL may be written in OP, but it is really just a wrapper for the windows API, which relies heavily on sending messages all over the place.

    A VCL that runs under a completely different OS and UI toolkit, and tries to maintain compatible public interfaces with the Win32 VCL may be possible, but will likely be as ugly as heck & generally be the Wrong Thing (tm).

    I love VCL, it makes Win32 bearable because it does the right thing to it.

    I'm all in favour of a similar library for Unix (less learing curve for me & my cohorts) - but why must it be identical?

    Why should a KDE/Gnome VCL do Win32's right thing? Ok, I mean aside from that pesky source compatibility trip.

  • FWIW, I think bcc is a Borland trademark. If it isn't, I'd bet Borland will assign a different name to the compiler. What they showed at the conference was proof that their compiler works under Linux...not what the untimate marketed package will be called.

    gut tells me that Borland doesn't want to piss of the Linux folks, but rather complement what they already use and give them better tools when possible.
  • by Ronin Developer ( 67677 ) on Monday July 26, 1999 @07:17AM (#1783323)
    That wasn't demonstrated. In fact, showing bcc was just a teaser to whet our appetites for anything Linux. But, both executables ran identically.

    As for the "Primetime" (JBuilder in pure Java). There were quite a few discussions and demonstrations. The one thing they did demonstrate was running the same Primetime for Solaris under Linux. What's holding back Primetime for Linux is that the Blackdown JDK still has too many bugs (heck's that's why it's prerelease).

    I asked about whether Borland was contributing to the Blackdown project and was assured that they were. Also, Borland demonstrated their Java JIT compiler. This made Primetime perform like a native binary rather than an VM'd app.

    Borland is also said convincingly that they will not develop their own VM. Instead, they said they will develop for the one in most common usaga on the Linux platform - Blackdown.

    Among the other things demonstrated were:

    DataStore - An object oriented persistent model for Java.

    Delphi CORBA going against a Linux based CORBA server. They also demonstrated a preliminary IDL compiler that worked with Delphi code.

    The commitment from Borland appears to be there. It won't be long before their tools will be among those of choice -- especially in a corporate setting.
  • I don't know if the folks at Borland realised this, but 'bcc' is the name of a 16-bit compiler for linux. Check out your local Debian package catalogue and you'll find it.

    Jeff

  • I even want to pay MORE for delphi under linux as I pay for the windows version.

    if it can do anything it is able to do under windows.
  • I must beg to differ with you on this one. Borland C++ 5.0 was a piece of crap. As a commercial software developer, I found it all but useless for creating even the most rudimentary of Win32 GUI apps. Yes, some of these compiler issues were fixed in later patches, but I had deadlines to meet. It was too little, too late for a $500 product.
  • Hehe... He was so possessed that he couldn't keep the shift key down...

    The ability to copy an insane fascist ranting and hold down CTRL+V won't get you much respect around here, bugbear.......
    Perhaps he belongs on cooksey.net/thndx.htm instead?
    I think you can figure out how to email me ;)
  • That's an interesting question. Will it be more or less GCC-compatible? Or will it be similar to their DOS/WinDoze compilers?
    I think you can figure out how to email me ;)
  • Talking about what OS will be the leading one in 6-10 years is like telling what the weather is going to be in the year 2013 - impossible.

    I most probably wount run Linux in 6-10 years, I will migrate to a much more modern OS - probably GNU/Hurd.
  • Considering the ANSI C++ standard also fails to define standard static object creation, you probably don't want your libraries compiled by different compilers to link!

"Nuclear war can ruin your whole compile." -- Karl Lehenbauer

Working...