Slashdot Mirror


Borland Announces the Return of the Turbo Products, with Video

Leonel writes "Borland Software's Developer Tools Group just announced the return of the Turbo line of products. With free and cheap versions, it's aimed at students, hobbyist developers, occupational developers and individual programming professionals. More information is available at the the Turbo Explorer website, including a video of the Adventures of TurboMan."

286 comments

  1. How can I be funny? by Anonymous Coward · · Score: 0, Funny

    How can I be funny on the internet?

    1. Re:How can I be funny? by darth_MALL · · Score: 1, Funny

      Make an obscure sexual reference to Bjarne Strousup.

    2. Re:How can I be funny? by Ignominious+Cow+Herd · · Score: 0, Offtopic

      1) Get on the Internet
      2) Be Funny
      3) Profit!

      --
      Lump lingered last in line for brains, and the ones she got were sorta rotten and insane.
    3. Re:How can I be funny? by iced_773 · · Score: 2, Funny


      Personally, I'd rather be Insightful, because Funny doesn't get you karma.

    4. Re:How can I be funny? by iced_773 · · Score: 1


      Moderation +1
          100% Funny

      Idiot mods. Didn't you read my post? I guess my .sig should be a little more specific. :)

  2. Re:Delphi??? by 0racle · · Score: 1

    Well they have added C# to the family too.

    --
    "I use a Mac because I'm just better than you are."
  3. What age group? by neonprimetime · · Score: 3, Insightful

    it's aimed at students, hobbyist developers, occupational developers and individual programming professionals. More information is available at the the Turbo Explorer website, including a video of the Adventures of TurboMan.

    The adventures of TurboMan? Just to confirm, we are talking about college students, not elementary school, right?

    1. Re:What age group? by Almahtar · · Score: 1

      You could probably get a lot of college CS majors interested if it was the adventures of TurboWoman.

      MMMmmmmm... bitmasks and tights... I'll orient your objects, baby!

    2. Re:What age group? by compuguy84 · · Score: 1

      maybe it's supposed to be stupid-funny for adults? like the adventure of ....(trumpets) TROJAN-MAN!

      ...except for virgins ;)

    3. Re:What age group? by __aaclcg7560 · · Score: 1

      Until the parent/child relationship comes into play. That's always confusing for beginners. :P

    4. Re:What age group? by Razor+Sex · · Score: 0, Redundant

      Marijuana.

    5. Re:What age group? by Your+Pal+Dave · · Score: 1
      The adventures of TurboMan? Just to confirm, we are talking about college students, not elementary school, right?


      Considering that the TurboMan ad campaign was back in 1988, I would say this is an attempt to appeal to people now in their 30s minimum.
    6. Re:What age group? by Anonymous Coward · · Score: 0
      Just to confirm, we are talking about college students, not elementary school, right?
      Contrary to popular belief, schools nowadays dumb you down instead of making you smart. That's their new job.
    7. Re:What age group? by 0racle · · Score: 4, Funny
      we are talking about college students, not elementary school, right?
      What's the difference?
      --
      "I use a Mac because I'm just better than you are."
    8. Re:What age group? by rrohbeck · · Score: 1

      If you look at that funny square thingy he brings you'll know this is aimed at the over-40 crowd.

    9. Re:What age group? by empaler · · Score: 1

      Contrary to popular belief, schools nowadays dumb you down instead of making you smart. That's their new job.

      Yeah. I believe the idea used to be that Primary was to make sure that everyone had at least the same skills. Now it can better be described as making sure that noone has more skills than anyone else.

    10. Re:What age group? by TheDreadSlashdotterD · · Score: 2, Insightful

      The amount of beer at the birthday parties.

      --
      I have nothing to say.
    11. Re:What age group? by Anonymous Coward · · Score: 0

      I used their software for some years.
      With the migration of their talent to fresher pastures (a.k.a Microsoft ), they have been producing buggy, slow rubbish. If you think that Visual Studio is bad, you should try the rubbish that Borland is selling.

      Stay away from this buggy crap.

    12. Re:What age group? by Anonymous Coward · · Score: 0

      Ironically the real "TurboMan" Anders Heilsberg is now working for Microsoft.

  4. Re:Delphi??? by Buelldozer · · Score: 1

    I started with Borland Turbo C++. :-)

  5. Re:Delphi??? by DelphLinux · · Score: 1

    And this is a problem because? Have you seen the current incarnation of the Delphi/Object Pascal language?

  6. Too little too late by Anonymous Coward · · Score: 0

    Borland-Inprise-Borland, had the market and gave it away. I was an avid Turba Pascal user byt with Eclipse, KDevelope and Visual Studio who really cares any more what Borland does...

  7. Hardware requirements? by Rupert_Giles · · Score: 5, Funny

    Do these still need two 5.25" floppy drives to run? I'm not sure I remember where mine are.

    1. Re:Hardware requirements? by XenoPhage · · Score: 1

      Wow.. Karma.. I *just* tossed out the copies of Turbo C++ and Turbo Assembler I had in the garage.. 3.5" disks.. Not sure if I know where the drive for that is anymore either..

      --
      XenoPhage
      Technological Musings
    2. Re:Hardware requirements? by Profane+MuthaFucka · · Score: 1

      You also will need the turbo button on your PC. Compiles will really fly when you crank it up to 8 mhz.

      --
      Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
    3. Re:Hardware requirements? by Sabalon · · Score: 1

      I remember when we got version 3.1 of the Turbo C++ for Windows in (I think that was it). It came on 1 CD, about 10 HD 3.5" floppies, or about 60 standard 5.25 floppies.

      And at the time we made backups of all the disks and worked from those. Ugh.

    4. Re:Hardware requirements? by An+ominous+Cow+art · · Score: 3, Interesting

      Some of the first code I wrote under DOS used Turbo C 1.0. Still have the manuals around here somewhere...

      I still have a soft spot for the Brief editor (which Borland acquired at some point from UnderWare), too. Some of my most productive coding was done under Brief + dBrief...

    5. Re:Hardware requirements? by ifdef · · Score: 1

      Brief and Vedit were the 2 popular editors where I worked, back in those days. I'm still using Vedit, though the Windows XP version has a few more features than the CP/M version did :-)

    6. Re:Hardware requirements? by waterwingz · · Score: 0

      So far nobody has commented on Wizard C - the product Borland bought and called Turbo C 1.0 after they bolted on the Turbo Pascal UI. That might have been okay except that they removed Wizard C's ability to compile ROMable code in the process.

      --
      . waterwingz
    7. Re:Hardware requirements? by Bing+Tsher+E · · Score: 1

      I can look just over on my right, and there's the Turbo Pascal 3.0 manual, where it should be.

      Good times.

    8. Re:Hardware requirements? by cboscari · · Score: 1

      That sounds like Borland C++ 3.1, the bigger version for win32 and DOS development. Turbo C never got that big, at least that I know of.

    9. Re:Hardware requirements? by hunterkll · · Score: 1

      I thought my school had issues...

      ~looks at his complete sets of prolog and pascal 2.0 ... ~

      Gotta love that it took them until 2004 to throw it away..

    10. Re:Hardware requirements? by Raven_Stark · · Score: 1

      "I still have a soft spot for the Brief editor (which Borland acquired at some point from UnderWare), too"

      I wonder if Brief and UnderWare will be replaced by FreeBalling 1.0.0?

      --
      http://www.marxist.com/
    11. Re:Hardware requirements? by XL70E3 · · Score: 0

      You probably don't know much about the borland product line nowadays. To say that and being modded funny, i guess a lot of people don't have a clue of what Borland have been doing for the past few years..

    12. Re:Hardware requirements? by Mysticalfruit · · Score: 1

      Ironically it was Turbo C++ that pushed me to linux.

      It was my freshman year and my parents bought me a new computer (a pentium 166, with *gasp* 64MB of ram) and it was running windows 95.

      I owned a copy of Turbo C++ version 2.5 or 3.0 (don't remember) and it kept crashing right in the middle of compiles.

      A buddy of mine came over and helped me install Slackware on the machine and I never looked back.

      --
      Yes Francis, the world has gone crazy.
    13. Re:Hardware requirements? by strobert · · Score: 1

      ah brief.

      I still recall using the 16-bit OS/2 version under WinNT in order to get long filename support (and have it nto take 100% of the CPU when idle).

      I still lvoe that editor. And although I know I will likely loose some geek cred for syaing it, I still don't think I am as fluid under vi as I was under brief. the multiple files at once (easy and low latency switching) and the keyboard commands just seem very natural.

    14. Re:Hardware requirements? by An+ominous+Cow+art · · Score: 1

      I agree - the default keybindings in Brief were very intuitive. And the column mode was very easy to use.

    15. Re:Hardware requirements? by Sabalon · · Score: 1

      Yeah...that's the one. It's been a couple years plus some :)

  8. That's just wierd by KingDaveRa · · Score: 3, Interesting

    Last night, I was digging around on the Borland site to see if there was such a thing as this, and today they announce it. How's that for a co-incidence!

    I'll certainly be interested to look at these though. Free things are ALWAYS good :)

    1. Re:That's just wierd by bwcarty · · Score: 5, Funny

      Free things are ALWAYS good :)

      Did you live in Troy in a previous life?

    2. Re:That's just wierd by Rob+T+Firefly · · Score: 4, Funny
      Last night, I was digging around on the Borland site to see if there was such a thing as this, and today they announce it. How's that for a co-incidence!
      It's no coincidence. The web guy noticed your digging in the server logs, mumbled in dull surprise at the fact that anyone was still interested, and cut-and-pasted your activities in the logs a few hundred thousand times for a few giggles to break up the monotony.

      This morning happened to be when the bosses glanced at the logs, and once they realized how "popular" this stuff seems to be, they knew beyond the shadow of a doubt that it's time for the return of Turbo.
    3. Re:That's just wierd by KingDaveRa · · Score: 1

      I read an article about Psychokinesis last night too. Maybe that's connected?

    4. Re:That's just wierd by Anonymous Coward · · Score: 0

      Psychokinesis: wow! You can turn sunlight into sugar!!?

    5. Re:That's just wierd by g2devi · · Score: 1

      Of course, if the Trojans had actually bothered to open up the horse (or even poke the horse with a few dozen spears or even burn the horse to sacrifice it to the gods), they might have gotten several *fantastic* free gifts including Odysseus and several of Greek's best soldiers.

      That just goes to show that often it's possible to turn a disadvantage into an advantage.

    6. Re:That's just wierd by R3d+M3rcury · · Score: 2, Funny

      Beware of gifts bearing Greeks.

  9. Turbo C by doti · · Score: 2, Informative

    Me too.
    I still keep a copy of Borland C++ 3.1 (the last DOS version).

    It was an awesome IDE, very productive.
    Good old days.

    (Not that today is less bright, Vim/gcc/gdb has it all, too.)

    --
    factor 966971: 966971
    1. Re:Turbo C by JabberWokky · · Score: 1
      I used the Turbo C 2.0 IDE as my main editing environment for years. Up until I switched over to emacs in the late 90s. Absolutely fantastic system.

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    2. Re:Turbo C by JabberWokky · · Score: 1
      Make that late 80s. Man, I've been doing this too long.

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
  10. Here we go again... by Anonymous Coward · · Score: 5, Funny

    TurboProducts return!

    With 80% more standards non-compliance.

    1. Re:Here we go again... by Schmuckly_McDuckly · · Score: 1, Funny

      Anything to free my mind from the abundance of software with "J" and "Py" prefixes......

    2. Re:Here we go again... by MagikSlinger · · Score: 1

      I was waiting for someone to remember that. :-)

      Ah, the painful memories of a half-assed Turbo Pascal. It didn't quite want to be Object Pascal, didn't quite want to be real Pascal, didn't want to become a modern professional language either.

      --
      The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
    3. Re:Here we go again... by krischik · · Score: 1

      Which is the reason I program Ada nowadays.

    4. Re:Here we go again... by cbacba · · Score: 1

      Gee,

      I wonder if they ever fixed their optimization problem that they injected around c++ 4.0 and refused to address after 4.5. The one with the for() loop that insisted on stomping the Base Pointer register with the final loop value when it was held only as a register. That caused lots of instabilities in early windows programs that were never found.

    5. Re:Here we go again... by Anonymous Coward · · Score: 0

      Professionaly? Lucky bastard.

    6. Re:Here we go again... by Anonymous Coward · · Score: 0

      Well, if we want non-compliance to standards, they can just take out the
      IEEE floating point routines, add a virtual machine, and then we would
      have one of two things:

      BASIC, or...JAVA!

  11. TurboC by WPIDalamar · · Score: 4, Funny

    I learned to program on a dos version of TurboC ... To this day I still prefer the yellow on blue text :)

    1. Re:TurboC by cyfer2000 · · Score: 1

      The manual looks like the old one too. I read the manual when I was a teenager...

      --
      There is a spark in every single flame bait point.
    2. Re:TurboC by Anonymous Coward · · Score: 0

      Just so long as the text isn't red on blue. Then it floats right off the monitor.

    3. Re:TurboC by misleb · · Score: 1

      Same here, but what I DON'T prefer is segmented memory and trying to figure out when to use the small library, the medium, or the large (or whatever it was called). Not that it is Borland's fault. DOS programming sucks ass.

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    4. Re:TurboC by DAharon · · Score: 2, Insightful

      Me too. It would be really nice if they just ported that to Linux. It was the perfect IDE for me. Easy to use. Small and fast, with a shell to test programs.

    5. Re:TurboC by 91degrees · · Score: 2, Insightful

      Yes, but didn't it require a 386 or better to run the IDE, or was that a different version? Always struck me as odd that it had a 32 bit processor requirement but no 32 bit compiler.

      It was nice that you could write a simple single file C application, and compile and run it without any concern over projects and solutions or makefiles. Also nice that it gave a lot of screen real estate to the editor.

    6. Re:TurboC by RuneB · · Score: 4, Informative

      You might want to try SETEDIT or RHIDE. SETEDIT is an editor and RHIDE is an IDE, both written using the Turbo Vision toolkit.

      --
      dtach - A tiny program that emulates the detach feat
    7. Re:TurboC by LWATCDR · · Score: 1

      Nope. I used Turbo Pascal and Turbo C on an 8088. Actually a V-20 that ran at a blazing 8Mhz.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:TurboC by shplorb · · Score: 1

      Heh, you sound like me. I learned C/C++ with TurboC++ and to this day, the first thing I do when using a fresh install of an editor is change all the colours to be as much like TurboC as possible. Quite a few other coders around here do it too.

      I don't know how people can stare at a bright, white background all day.

    9. Re:TurboC by realnowhereman · · Score: 1

      Me too - in case anyone is interested, there is a Borland colour scheme for vim available from http://www.vim.org/scripts/script.php?script_id=92 . I can't live without it.

      --
      Carpe Daemon
  12. Coincidence? by Rob86TA · · Score: 5, Interesting

    Interesting that the Borland tools are being released close to the end of the free year of MS's Express line (ending in Nov. I believe). Could Borland be preparing to take on the MS developer tool chain again?

    Considering that Visual Studio is a highly evolved (I know, this is ALWAYS open for debate on /.) tool chain. It'll be fun to see if Borland can bring anything new and unique to compete with the VS Express Editions.

    1. Re:Coincidence? by Anonymous Coward · · Score: 1, Interesting

      TFA states that Borland wants to sell off its IDE division. This is all about marketing. Give away the free edition to students, and they'll want to use at work. This is buzz for a buyout.

      Personally, I'd buy anything from a man named "Mr. Swindell"! From the article: "Michael Swindell, [is] senior director of product management".

    2. Re:Coincidence? by nuzak · · Score: 4, Informative

      > Interesting that the Borland tools are being released close to the end of the free year of MS's Express line (ending in Nov. I believe).

      Microsoft lifted the end date back in April. It's being offered for free forever. Well, as long as forever goes with Microsoft (The VS2003 toolchain didn't take long to disappear).

      --
      Done with slashdot, done with nerds, getting a life.
    3. Re:Coincidence? by $1uck · · Score: 1

      close to the end of the free year of MS's Express line (ending in Nov. I believe)

      I know this is offtopic, but what does this mean? I downloaded most of the VS express editions. Will they stop working? or will they just not let anyone download them after november?

    4. Re:Coincidence? by pwoon · · Score: 0, Troll

      Visual Studio crashes often, and is still a work in progress. The Borland IDE and compilers leasve the QT and gcc compilers in the dust. For you people who discount the Borland tools, I suggest you take another look. In addition, as a development platform, Windows surpasses Linux.

    5. Re:Coincidence? by jj00 · · Score: 1

      Considering that Visual Studio is a highly evolved (I know, this is ALWAYS open for debate on /.) tool chain. It'll be fun to see if Borland can bring anything new and unique to compete with the VS Express Editions.

      I sure hope they can compete with Microsoft. As it stands now, they have (arguably) the most visible OS, developer platform, database, and office tools in the business arena. The way everything stacks up, and the way that businesses like a simple direct solution, Microsoft basically has to come up with new things in order to keep selling their IDE/OS/DB/etc. It's a twisted cycle that I wouldn't mind seeing broken down.

      It may just be a pipe dream, but theoretically if another company wrote against Microsoft's .Net spec even a year after it was introduced, you would think that product would benefit from it. A business could live in that space - watching what Microsoft introduced that year and then waiting till Borland included it to see if it actually works.

    6. Re:Coincidence? by dhasenan · · Score: 1

      The original deal was, the license is permanent, but new licenses wouldn't be offered after a certain date. So if you got it before the cutoff, you could use it forever.

      Currently, though, there's no cutoff date listed.

    7. Re:Coincidence? by Jeff+DeMaagd · · Score: 1

      The VS2003 toolchain didn't take long to disappear

      Heck, their network drivers didn't take long to disappear after they quit selling their networking products. I had lost my CD for their wireless card and it's not available. This is a significant departure in comparison with many major brand hardware makers where drivers are kept up seemingly indefinitely. For example, old modem drivers are still available on US Robotic's site (or whoever bought them up). Drivers for my eight year old Compaq workatations are still available on HP's site. With Microsoft, it only took them two months to pretend their network products never existed.

    8. Re:Coincidence? by Bing+Tsher+E · · Score: 1

      Only time will tell. 'Drivers' for a Microsoft hardware product can disappear, but support linger on for generations on the OS install CD. I have Microsoft 'Digital Sound System 80' USB speakers and they emit sound right after the OS install is done, though I don't think you can download drivers for them anymore.

      Great speakers, BTW. It has always been cool to not have to install a sound card. They worked 'out of the box' when I tried Mandrake, too.

    9. Re:Coincidence? by Haeleth · · Score: 1

      The VS2003 toolchain didn't take long to disappear

      That's because they decided to make VS2005 Express Edition free forever to replace it, thereby making the VS2003 toolchain obsolete. Microsoft decides to upgrade a free product, and to throw in an IDE for free with it? Sounds good to me.

  13. The times they are a changin' by realnowhereman · · Score: 4, Insightful

    At the time, Borland (or maybe Watcom) had the best C++ compilers. They also had a wonderfully designed library in the form of TurboVision for doing console applications with menus and windows. However, time has passed, GCC is a damned fine compiler and Qt is a superb UI framework (et al). If Borland wanted to join in this game they should have open sourced their compiler a long time ago. Too little, too late I'm afraid.

    It's a shame really, Borland were my favourite company, then Philip Kahn left, they changed their name to Inprise and all their top developers went to Microsoft.

    --
    Carpe Daemon
    1. Re:The times they are a changin' by Helen+O'Boyle · · Score: 1

      At the time, Borland (or maybe Watcom) had the best C++ compilers.

      I'm afraid I have never forgiven Borland for their circa 1992 UI bug (or would that be a deliberate feature in some jokester's eyes?) in which a certain keystroke sequence used to build one's app in the MS IDE caused the Borland IDE to crash without saving the files on which one was working. The deal was that the MS IDE accepted a keystroke sequence of {altdown}{key1}{key2}{altup}, whereas Borland required {altdown}{key1}{altup}{key2}. I think I wasted a few hours of dev time thanks to that (while porting BSD rlogin to a PC, precisely), and it was enough to make me conclude that I could dismiss Borland's products whenever I was working in a shop that did not require me to use them.

    2. Re:The times they are a changin' by colfer · · Score: 1

      Borland C++ 5 was a terrible product. I couldn't believe it came from Borland, since everything else they made since that tiny one-disk Pascal compiler had worked like magic. I was never able to evaluate the C++ 5 compliler because the IDE crashed all the time. So I went back to Delphi for rapid devlopment, and MSVC for macro hell. Anyway, that was all *before* the Inprise name change at Borland. The internet was starting to boom and Inprise decided to make it expensive to get the Winsock TCP/IP components. Using the $99 (or $199 ?) version, you had to download feeware components to do anything over the net.

    3. Re:The times they are a changin' by colfer · · Score: 1

      typo: feeware -> freeware, community stuff. lots of good delphi stuff still available.

    4. Re:The times they are a changin' by hey · · Score: 0, Troll

      If I recall correctly, those top developers didn't just happen to go to Microsoft. Actually
      the evil empire paid extra for them to come over to the dark side to hurt Borland. Of course, as usual, Microsoft couldn't handle the idea of real competition.

      And to make things worse now people like you remember it as bad management on the part of Borland (and in a similar case Netscape) that was the cause of their demise. When it was, in fact, the evilness of the evil empire.

      ps. Thanks for sending your blood money on good causes, Bill.

    5. Re:The times they are a changin' by master_p · · Score: 1

      Since Borland has so much experience in programming languages, I wonder if they has occured to them to make a completely new programming language that incorporates all the latest developments in PL science, and it is distributed right from the start (distributed to the degree that imports are URLs).

    6. Re:The times they are a changin' by marcovje · · Score: 1

      (btw portable versions of the C++ Turbovision is are available for GCC and portable Pascal ones (clones actually, the Pascal version was never PDed) via Free Pascal)

      IMHO the QT designer stuff and IDE can't hold a candle to Delphi.

  14. Turbo C++ by Almahtar · · Score: 3, Insightful

    Could be really nice having another commercial Windows C++ IDE around. At my workplace we really need an alternative to Visual Studio. In a codebase that's nearly 1,000,000 lines intellisense is insanely slow, completely inaccurate, and honestly just plain annoying. Visual studio randomly crashes, etc. We're in the process of switching to CMake so people can use Eclipse or whatever IDE they want, but Eclipse's CDT is still a bit too young for my tastes. Perhaps Borland's IDE will provide a welcome reprieve and nice debugging.

    1. Re:Turbo C++ by Anonymous Coward · · Score: 0

      afaict, all the borland tools are still available for sale. with a million lines codebase I think you could afford to get a couple C++ builder licenses...

    2. Re:Turbo C++ by Jugalator · · Score: 1

      I'm diving straight into technicalities here, but if you're using Visual Studio 2005 and have slowness increasing as code grows in your open documents, you could always try turning off the Navigation Bar (the long horizontal bar just on top of the main code window normally). I never used it anyway, and either something else changed causing it, or I'm seeing quite an increase in basic code navigation speed nowadays. There was a bug related to that one that "should" have been fixed in the betas, but I'm not so sure it was to 100%.

      See more here: Is your Visual Studio 2005 editor extremly slow when you type?

      Another thing that I thought become *more* annoying in 2005 is the Intellisense feature that sometimes kicks in and starts parsing the longest source documents in the most inconvenient moments.

      --
      Beware: In C++, your friends can see your privates!
  15. Twenty years of using borland products by Crashmarik · · Score: 1

    And I still avoid microsofts line like the plague. Its good to see the Turbo brand back.

    1. Re:Twenty years of using borland products by HaMMeReD3 · · Score: 1

      Well those 20 years could have been spent worse, you could have been using codewarrior.

      Last time I compiled "Hello World" in a codewarrior product, it took, uhhh wait, it's still compiling, I'm gonna get some coffee.

  16. Why Switch To Borland's Turbo Line? by Petersko · · Score: 5, Insightful

    I would imagine that Borland hopes to boost sales of its higher end lines by giving away the cheap ones and hooking the developers, but they'd better have some super-sweet bait on the end of the hook. There are tons of powerful IDE's, many free. Unless they bring something to the table that is lacking in other products, I can't see them reaching their business objectives.

    People are beginning to expect the IDE to be free. Oracle knows this, so does Sun.

    Best of luck to Borland. I have fond memories all the way back to Borland C++ 3.x for Windows, and Delphi - ESPECIALLY Delphi.

    1. Re:Why Switch To Borland's Turbo Line? by LiquidCoooled · · Score: 2, Insightful

      I bet they bring one thing thats more powerful than ANYTHING these other IDE's can:

      Age and history, don't forget, most of the managers now were code monkeys back then and a hell of a lot of them used borland.

      --
      liqbase :: faster than paper
    2. Re:Why Switch To Borland's Turbo Line? by pmiller396 · · Score: 1

      n00b! I remember Turbo Pascal 3.0 for DOS. I ran right out and bought Turbo C++ 1.0 when it was new! Aah, those were the days....

    3. Re:Why Switch To Borland's Turbo Line? by Oxygen99 · · Score: 1

      Do they even have any higher end lines any more? As they've already spun off their development tools to an independent company, I suspect they'll be going down the IBM route of services, services, services but quite what they have to offer, I'm not sure. To be honest, I'm not convinced they'll will be with us as independent company for too much longer.

      Shame really, as Delphi rocked.

      --
      I had a dream, bright and carefree, but now there's doubt and gravity
    4. Re:Why Switch To Borland's Turbo Line? by SolomonShort · · Score: 1
      Best of luck to Borland. I have fond memories all the way back to Borland C++ 3.x for Windows
      I also have fond memories of the OWL (Object Windows Library) which, I thought, was better than the MFC back in the Win 3.x days.
      I am currently working on a project where BC++ is the mandatory compiler because it is for a 16 bit (80186) DOS-like embedded system.
      Hopefully they will support 16 bit targets with a decent STL. The STL in BC 5.02 uses a lot of memory (too much for embedded systems IMHO).
    5. Re:Why Switch To Borland's Turbo Line? by markhb · · Score: 1
      They are sticking with the Application Lifecycle product line, so essentially they are getting rid of the pesky developers and selling to their managers instead. The relevant line from the press release on the divestiture is:
      Borland's IDE business requires a distinct business model and focused investments different from our ALM business, which targets the broader software delivery organization.
      --
      Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
  17. Re:Delphi??? by Leonel · · Score: 5, Informative

    Delphi ain't your father's Pascal. It's a modern, object-oriented interoperable language. The main advantage isn't the language itself, but the class library (VCL) and the form designer, which is the best tool around to build user interfaces (ask Skype), while still having the ability of having your code neatly encapsulated in classes separated from the presentation layer.

    Anyway, Delphi is only half of the picture here. There's Turbo C++ and C# offerings along with the native Delphi and Delphi for .Net offerings. if that's your language of choice, you can use C++ with the VCL (or for plain WinAPI applications, if you feel inclined).

    Basically, the explorer versions are advanced IDEs for these languages, free of change, allowing commercial development. There's your motivation.

  18. Turbo Prolog by BackOrder · · Score: 1

    I don't see Turbo Prolog anywhere. Nor Turbo Pascal.
    It's the Turbo line without the Turbo products.

    Is it yet-another-PR-stunt-baby?

    1. Re:Turbo Prolog by Leonel · · Score: 1

      Turbo Delphi is the equivalent of Turbo Pascal, only the language has evolved. As for Prolog, hmm, I don't think that's going to be making a return.

    2. Re:Turbo Prolog by wmeyer · · Score: 1

      Let's see... IIRC, Turbo Prolog was about 1988? With no releases since then?

      And you're disappointed not to see it magically reappear?

      By the way, how many Prolog projects are you currently supporting?

      Delphi is basically Turbo Pascal on steroids, so you can consider that TP is back.

      --
      --- Bill
    3. Re:Turbo Prolog by Ardipithecus · · Score: 2, Informative

      Turbo Prolog was a variation of PDC Prolog, a Danish project. It was a compiled Prolog, and in Prolog fashion taught the user to think backwards, a sometimes useful technique. When Turbo Prolog ended, PDC Prolog continued with the product, later morphing it to Visual Prolog. Somewhere, I have them all. See http://www.visual-prolog.com/ - a new version 7 was coincidentally released a week ago, and a free Personal Edition is available.

    4. Re:Turbo Prolog by LWATCDR · · Score: 1

      What about Turbo Editor Toolbox, Turbo Database Toolbox, and Turbo Communications Toolbox?
      Editor Toolbox was way to useful :)

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  19. Sounds like Coke... by __aaclcg7560 · · Score: 1

    Does the "New Borland" run on Mac OS X? Or do we have to wait for "Borland Classic" to come out?

    1. Re:Sounds like Coke... by Bing+Tsher+E · · Score: 1

      You'll have to install Think Pascal on some sort of compatability sandbox.

      Wasn't MacOS originally written in Pascal?

    2. Re:Sounds like Coke... by __aaclcg7560 · · Score: 1

      It was written mostly in Pascal with a smattering of assembly lanaguage where it was needed.

  20. As much as I hate to say this ... by mingrassia · · Score: 1, Insightful

    Don't get me wrong. I love the Borland of yester-year, but are Borland tools relevant anymore?

    With all the free goodies available, development on most platforms can be done without spending a dime.
    Just off the top of my head, things like GCC, Xcode, and Eclipse come to mind.

    --
    OS X, Linux, Tivo, Amiga, my fascination with cult-like technologies would intrigue any psychiatrist.
  21. Sounds like Express by szhao · · Score: 1

    Sounds like the visual studio express editions, though I am not complaining, visual studio express sukz ass compared to the professional especially for c++.

    1. Re:Sounds like Express by Anonymous Coward · · Score: 0

      >Sounds like the visual studio express editions, though I am not complaining, visual studio express sukz ass compared to the professional especially for c++.

      You sure? Sounds like you are complaining actually.

  22. download by doti · · Score: 1

    Are these available for download?

    I can't see any working download link on the site.
    Or is it a firewall or browser compatibility problem?

    --
    factor 966971: 966971
    1. Re:download by blirp · · Score: 4, Informative

      Are these available for download?

      Well, there's that
          27 days, 9 hrs, 40 mins, 30 secs
          until the Turbo(s) are here!
      timer there. Might explain the missing download links. :*)

    2. Re:download by gstoddart · · Score: 1
      Are these available for download?

      I can't see any working download link on the site.

      Look on the right hand side of the page, near the top. There is a countdown showing that in 27 days, 15 hrs, 41 mins, 45 secs (and counting) these will become available. Your browser could be hiding that part.

      For now, it's a pre-announcement of a product you can't have yet.

      Cheers
      --
      Lost at C:>. Found at C.
    3. Re:download by akunkel · · Score: 0

      If you have the NoScript Firefox Extension installed and have not allowed scripts from turboexplorer.com the countdown is not displayed in which case the missing download links are not explained.

  23. Turbo Pascal was disruptive by Migraineman · · Score: 4, Insightful

    Pascal was/is a great learning language. It's not too difficult to comprehend, but it's strong enough that you don't immediately exceed it's capabilities once you "get it."

    Turbo Pascal was a great because a) it was inexpensive compared to everyone else; and b) it compiled soooo much faster than everyone else. The development environment concept was pretty innovative too, and eliminated much of the command line funkiness. Funny, I didn't Turbo Pascal in the press release - Delphi, C++, C#. I guess you could call Delphi "object Pascal" if you wanted to.

    However, this press release stinks of a marketing cash-grab where they try to make a quick buck by squeezing the legacy heritage of a well-known trademark. I just don't see that they're adding any value to the proposition. Some marketroid probably did the math based on "no new development NRE" and was brimming at the huge potential margins on such a re-release (i.e. Margin := (1 - Expenses / Revenue); ). There's competition now, and most machines owned by hobby-programmers and students will cruise through the compilation process fast enough that the "turbo" brand doesn't offer a compelling solution like it used to. There are OSS solutions available, so the "less expensive" compulsion is gone as well. Back in the day (man, y'all are making me feel old ...) the alternative was the Microsoft compiler that was dog slow and required a manual linking step ... from the command line ... both ways.

    Tell Blaise that I still have fond memories ... now get the hell off my lawn!

  24. Sad, these are Borland's last ideas... by bocsika · · Score: 3, Interesting

    My enterprise was based on Borland C++ in the last 10 years.

    But this seems to be the last desperate ad before the collapse: the feature list contains no news at all - all of it should have been in Borland IDEs years ago.

    Instead of chewing new buzzwords, the daily used tools should have been cleaned up first: Borland C++ Builder 6 behaves terribly even on medium size projects, (crashes, tons of bugs, etc.)
    If Borland had a yearly update, I would be their greatest fun.
    If Kylix would have been developed further, I would pay for it, because we need cross-platform Linux tools...
    So many dead tools...

    Nothing to see here, man, move away... to Qt, for example.
    It is today's Borland. And shines.

    But because it provides a steady release cycle, people will buy it, even if it is pricey.

    1. Re:Sad, these are Borland's last ideas... by Bing+Tsher+E · · Score: 1

      move away... to Qt, for example.
      It is today's Borland. And shines.


      You mean a full version of it comes as a disc shoved in the cover of a paperback manual for like $80, and you can use it for pretty much whatever you like? You can develop commercial aps and sell them for that price?

      Doesn't sound at ALL like the Qt that I've read about...

    2. Re:Sad, these are Borland's last ideas... by Anonymous Coward · · Score: 1, Funny
      If Kylix would have been developed further, I would pay for it
      So you're the one...
    3. Re:Sad, these are Borland's last ideas... by Anonymous Coward · · Score: 0

      ROFL! If I had mod points...

    4. Re:Sad, these are Borland's last ideas... by Anonymous Coward · · Score: 0

      Yeah - Kylix was a nice product..

      However - on modern systems its a pain to get it running (and compiling goes even worse), so I ditched it and switched to free pascal and Lazarus. Free pascal also has cross-platform modules, zo writing something in Linux and running it on Windows is not that hard to do..

      Before anyone nails me down - I' m not a programmer and only write some small apps for personal use. Lazarus/free pascal is enough for me. C(++) programming is done in Kdevelop, so thats is taken care of also...

      It would be interesting to see if Borland will do something for Linux users tough...

  25. Great stuff! But... by blirp · · Score: 2, Informative
    This looks great. It brings back memories of when the IDE was so small and started so fast, I used Turbo Pascal as my editor of choice. Yeah, those glory days in the mid-80's....
    These days Borland Developer Studio gives me time to make some coffee.

    BUT .Net 1.1? Seriously? We've been at 2.0 for some time now, right? Did Borland just miss that announcement?

  26. TurboMan by ackthpt · · Score: 0

    The adventures of TurboMan? Just to confirm, we are talking about college students, not elementary school, right?

    Yes, let's be certain of that age group. More comic books are purchased by adults than elementary school-age children.

    I think it's overdue, the return of the turbo packages. Microsoft's .net suite is a nightmare.

    --

    A feeling of having made the same mistake before: Deja Foobar
  27. This is only to bring up their stock price! by jhfry · · Score: 4, Insightful

    FTA:
    "the company's Developer Tools Group, WHICH IS UP FOR SALE, is scheduled to announce single-language versions of the components of Borland Developer Studio..."

    The "up for sale" bit tells me that what they are doing is trying to drive some good press, boost their stock price a bit, and negotiate a higher selling price.

    Like most has-been corporations, they refuse to accept that they are obsolete and out of the running, so they would rather simply inflate their stock prices artifically so they can walk away with a nice chunk of change ans say, "see we didn't fail!" All I can say is, at least they didn't inflate theirs like SCO did!

    --
    Sometimes the best solution is to stop wasting time looking for an easy solution.
    1. Re:This is only to bring up their stock price! by jouvart · · Score: 1

      Speaking of which, I kinda wish Redhat would come out and buy out Borland's developer tools group. Since Redhat contributes a lot to GCC, hiring some compiler engineers might make sense in their business scheme too. It'd be really cool if Redhat could put their weight behind a robust rapid development platform for Linux too (Delphi for Linux?).

    2. Re:This is only to bring up their stock price! by cboscari · · Score: 1

      Wasn't Kylix(SP) Delphi for Linux? No one wanted it. Which was too bad, because Object Pascal was fun and easy to write in.

    3. Re:This is only to bring up their stock price! by Anonymous Coward · · Score: 2, Interesting

      Here's the deal. Borland dev tool's have been becoming 'has been' for a while, despite generally superior quality, due to years of management fubar's - beginning with Inprise. Borland management's focus is now "ALM" tools, which have been siphoning profits from products like Delphi for at least a couple of years.

      The dev tools division has been up for sale for a while - six months or so. During that time, 'DevCo' has been operating somewhat independently from Borland and has produced a couple of major service packs for Delphi and has been hiring talent. And now has come up with these Turbo tools.

      Most veteran Borland dev tool customers are excited and optimistic about DevCo. 'Turbo' type tools have been something long requested. Updating the VCL and providing a D64 compiler seem to be more than a pipe dream now.

      DevCo had announced that they had a buyer *before* the Turbo tools were announced. According to DevCo staff, an announcement about the buyer is imminent.

      Borland can cater to the ether-land of *ALM*, DevCo will (hopefully) again give attention to Borland's traditional customers who just want kick-ass dev tools.

      More info at the borland.public.delphi.non-technical.

    4. Re:This is only to bring up their stock price! by Halo1 · · Score: 1

      It still is :) And there's a Free alternative to Kylix as well: Lazarus + Free Pascal. The main reason Kylix was not well-received was because it's extremely buggy and slow (the IDE was Wine-based), and it runs on just a few distributions.

      --
      Donate free food here
  28. Filter them out. by Massacrifice · · Score: 1

    Next : World announces to Borland that nobody cares anymore about what they do.

    The Microsoft People have Visual Studio. The Java people have Eclipse/NetBeans. The OSS people have gcc, perl and whatnot.

    Nobody needs Borland anymore.

    --
    -- Home is where you eat your heart out.
    1. Re:Filter them out. by Anonymous Coward · · Score: 0

      The Windows People have Borland. Just because I develop for Windows, does not make me a Visual Studio user.

    2. Re:Filter them out. by whatnow42 · · Score: 2, Funny

      Your right, there is no room for a company that produces fast, native Windows applications any more. Let's all bloat our apps with .NET/Java/etc. Runtime "engines", "frameworks", "environments" etc. are THE way to go. Sheesh, nobody uses Windows anymore--well, except for 90% of the planet.

    3. Re:Filter them out. by PigIronBob · · Score: 1

      Ever used Eclipse Visual Editor, what a joke, I'm still working with Delphi 7, will kick the ars of any Java app when it comes to speed or low level capabilities.
      JVM should read JMV for Java Memory Vortex

      --
      You never catch me alive
    4. Re:Filter them out. by penrodyn · · Score: 1

      I don't understand the vehemency that some people have towards Borland, what did they do to you?

      Besides their products are good, they could be a bit leaner perhaps but otherwise they work well.

  29. Sometimes even free is too expensive by Ptolemy+Too · · Score: 1

    I suppose this is a commendable attempt to turn around a too-long tradition of increasingly high prices for increasingly low-quality products, but it might have been better to release a high-quality product, first. Even Delphi 2006, where they actually took quality seriously for the first time this century, has had two service packs and a double handful of "hot fixes" since it was released.

    But look at what they're giving away, and you may wonder if free is still too expensive. A simple C# "static void Foo()" becomes "class procedure Foo; static;" In the name of not breaking a handful of code (ie, avoiding a modest, one-time pain for that tiny handful of developers who used "static" as an identifier) they inflict on-going pain on all developers. Not a good design decision!

    I wish them luck - they'll need it. Time was when Turbo Pascal and Delphi were real productivity boosters, a Windows programmer's secret weapon. But Delphi stagnated while Borland put all their effort into poorly-executed ports (to Linux, and then to .NET) and now the productivity edge lies with C# and .NET, not Delphi and it's tired old VCL.

    1. Re:Sometimes even free is too expensive by a.stranger · · Score: 1

      They're also giving away a C# / .NET IDE, if you prefer that. To each their own.

    2. Re:Sometimes even free is too expensive by baadger · · Score: 1

      I agree, the last version of Delphi worth using is Delphi 7. The two versions that followed were produced in quick succession and sucked balls. There are still some features of the Delphi/Obj Pascal language I find appealing, but without a good implementation, it's C++ for me.

  30. TurboMan by Numbah+One · · Score: 1

    Sounds like an Arnold Schwarzenegger movie.

  31. Re:Delphi??? by a.stranger · · Score: 1

    (Delphi) Pascal, C++, and C#.

  32. Yawn... by frank_adrian314159 · · Score: 2, Insightful

    Tell me when they bring back TurboProlog...

    --
    That is all.
    1. Re:Yawn... by Bros · · Score: 0

      TurboLISP for me please...

      Cross Platform...
      GUI...
      Debugger...

      ... and vim as editor ;-)

  33. Intellisense by gr8dude · · Score: 2, Informative

    I used Delphi, Builder, and Visual Studio - and I found Borland's intellisense much less responsive than the one in the Microsoft IDE.

    Although I use it with not-that-complex projects, in my case the difference between speed is evident: it takes forever for the list of relevant options to show up in Borland's IDEs, while in VS the speed at which it shows up and can be used is the same, even after the project grows in complexity.

    1. Re:Intellisense by pwoon · · Score: 0

      Have you used Delphi lately? Blows VS away when it comes to speed in code completion.

    2. Re:Intellisense by Anonymous Coward · · Score: 0

      At least for BCB install the speedup tool from Andreas Hausladen (google his name). He single-handedly managed to speedup BCB compiler cca 5x (five times), having just the executable. This speedu has also positive effect on Borland's Intellisense.

  34. What a gigantic fuck-up by melted · · Score: 5, Insightful

    Borland was EXTREMELY popular back in the day. They could have OWNED the dev tools space completely. At some point they got too carried away with MBA-related activities, such as branding, enterprise fads du jour, etc and they lost their userbase and fucked up their products. I have used Delphi and C++ Builder extensively. 6-7 years back there was NO decent RAD alternative. The best thing about them was you could drop all the way to the bare metal at any time if you wanted to and you could have RAD capabilities if you needed to deliver stuff quickly.

    I feel for Borland, but at this point I think they should fold up their tent and die. They're beyond any hope of recovery, thanks to retarded management and marketing.

    1. Re:What a gigantic fuck-up by NavySpy · · Score: 2, Insightful

      Borland is selling their IDE tools. They will be spun out as a separate, standalone company focused entirely on developers, just like "old Borland' was. The Turbo products are an indication of the new focus on Developers in the new company.

    2. Re:What a gigantic fuck-up by mattypants · · Score: 1

      Yup... that's told 'em.

    3. Re:What a gigantic fuck-up by NMerriam · · Score: 2, Interesting

      The think I most fondly remember about Borladn was their no-nonsense user license. Instead of 20 pages of legalspeak, they had two or three paragraphs that said "Don't copy this, don't give it to your friends. you know you want to be nice, but we'd like to stay in business."

      It was very human and gave a good first impression.

      --
      Recursive: Adj. See Recursive.
    4. Re:What a gigantic fuck-up by ayjay29 · · Score: 1

      >>I have used Delphi and C++ Builder extensively. 6-7 years back there was NO decent RAD alternative.

      Well you were lucky, i ad to walk 15 miles to work int snow, then use Turbo Pascal 3, and compile everyting into a 64k COM file, and if it didnt run, my bos used to beat me with a stick.

      --
      Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated up.
    5. Re:What a gigantic fuck-up by TekPolitik · · Score: 1
      if it didnt run, my bos used to beat me with a stick.

      It's nice to know at least one of my former employees is reading Slashdot.

    6. Re:What a gigantic fuck-up by Anonymous Coward · · Score: 0

      Obviously you've never competed against Microsoft head-to-head working for their enemy #1, which Borland was in the early 1990's. Microsoft is absolutely ruthless in this mode and will pull out all the stops, illegal, unethical, bottomless pit of resources, whatsoever. For example, they hired away Borland's top two engineers with huge compensation packages. For another, MFC was yet another Microsoft catch-up effort to neutralize and capture a Borland innovation called OWL (Object Windows library). Of course, coming from Microsoft it became the immediate standard C++ application framework on Windows, because Microsoft controlled the Windows APIs and the OS was incredibly flaky at the time. BTW if you think the "12 principles by which Microsoft lives by" announced by their corporate counsel means anything has changed in this regard, think again. MS just announced they will end scripting support in their Mac versions of Office... now what is the rationale for that?

    7. Re:What a gigantic fuck-up by andersa · · Score: 1

      I feel for Borland, but at this point I think they should fold up their tent and die. They're beyond any hope of recovery, thanks to retarded management and marketing.

      Could you or anyone else please explain to me why Borland should quit when they have a thriving application lifecycle management business?

      What they are trying to do, is to focus their activities on those parts that are most profitable. That means selling off the not nearly as profitable RAD tools. They are doing what many companies that are not making as much money as they should be are doing, which is to concentrate on what they are good at. This makes sound business sence.

      Actually most RAD tool customers are fairly happy that the tools are being sold off. For some time they have not been given all the attention they needed, and the quality of new releases has suffered because of it. They are hoping that new owners will bring the tools more into focus, and get some of the few quirks ironed out.

      My company uses Delphi as the primary development tool. I think its the best product available for Win32 programming. The compiler is insanely fast and efficient, and the IDE is for the most part very easy and logical to work with. Oh.. And btw.. Object Pascal rocks!

      :)

    8. Re:What a gigantic fuck-up by smchris · · Score: 1

      Yes. Management made the moronic decision to voluntarily change their recognized and respected brand name to Inprise -- for a while. I doubt that Microsoft has ever felt a burning need to change its name to "Unprize" or something for better brand recognition. But at that same time they were hit with the curse of Version 4. Like the screw-ups in dBase 4 which tanked that product (that Borland then acquaired incidentally), "Inprise" Delphi 4 went through three revisions that were more like rewrites than patches before they got it right.

      I don't see a lot of management wisdom and vision in bringing back the "Turbo" name either. A lot of people who would get a warm and fuzzy feeling from the name probably aren't programming anymore or have long moved on to other platforms. And it won't mean anything to the kids so why bother? My first reaction was sarcastic. "Gee, they'll have some tough competition from Free Pascal now."

    9. Re:What a gigantic fuck-up by Malc · · Score: 1

      They were dying 10 years ago. I remember when they released Borland C++ v5. It was dreadful, and not a worthy follow-up to the products that preceded it. MSVC was immature back then, but it worked better than buggy BC5. Then Microsoft released MSDev97 (MSVC5) and it was game over. MSVC6 came shortly after and put the nails in the coffin.

    10. Re:What a gigantic fuck-up by Anonymous Coward · · Score: 0

      Incidentally, in chess the term "en prise" basically means you blundered.

  35. motivation? by wmeyer · · Score: 5, Interesting

    Your motivation? How is productivity as a motivation?

    Delphi has been my tool of choice for the last 11 years. It remains the
    most productive development tool I have used.

    Agile processes? Well, the build on a Delphi project is so quick, you
    don't have time to fill your coffee cup, much less drink it. So build/test
    cycles are fast.

    The language is powerful, and a great foundation for those who choose to
    move to C#. The learning curve on C#, coming from Delphi, is pretty shallow.

    But please, stay with your g++, and those glacially slow builds. I don't
    need more competition.

    --
    --- Bill
    1. Re:motivation? by Anonymous Coward · · Score: 0

      Delphi is the best development environment I've ever seen, bar none. Both the build cycle and the end code are lightning fast. I've used all modern languages in projects due to customer specifications but keep coming back to Delphi for those I can spec myself.

    2. Re:motivation? by einar2 · · Score: 1
      I would have agreed with you eight years ago. Delphi was extremly fast to compile, the VCL as a framework set an abstraction on top of the Win32 that made development much more productive.

      However, that was eight years ago. Although Borland did not get worse, Microsoft did get much better.
      • C# builds extremly fast too
      • The .NET framework looks suspiciously similar to the VCL
      • C# got some features that made Delphi as a language special (ex. properties)
      There is no reason (except nostalgia) to choose Borland. MS on the other hand will always have a headstart due to their platform knowledge.
      I seriously wonder what Borland did during the last eight years. Except charging us 2000 USD each year for an upgrade of JBuilder.
    3. Re:motivation? by jma05 · · Score: 1

      > There is no reason (except nostalgia) to choose Borland.

      There is one. Torry.net
      Show me a free component repository that is as comprehensive for .NET and I will leave Delphi.

  36. Wow -- such negativity by NavySpy · · Score: 2, Interesting

    Wow -- what an impressive display of negativity!

    1. Re:Wow -- such negativity by wmeyer · · Score: 1

      It's /.

      What did you expect?

      Most here would hate to be distracted from their beloved gcc.

      --
      --- Bill
    2. Re:Wow -- such negativity by Bing+Tsher+E · · Score: 1

      Uhhh, most here think that it's 'programming' to type: "./configure && make && make install"

    3. Re:Wow -- such negativity by RLiegh · · Score: 1

      These days, we use 'emerge', the truly 1337 make up custom USEFLAGS.

    4. Re:Wow -- such negativity by Reziac · · Score: 1

      Ain't it tho :/

      Personally, I think it's great that Borland makes these products freely available ... and I'm not even a programmer, just an interested bystander.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    5. Re:Wow -- such negativity by Y0tsuya · · Score: 1

      Because most people here feel Borland products are no longer relevant. I haven't used anything from them since Turbo Pascal/C days. These days it's VC++ for PC and gcc for Linux/embedded. There's no reason for me to use a Borland product.

  37. Why use this over Microsoft Visual Studio Express? by kungfuSiR · · Score: 2, Insightful

    I'm sure this product is great, but what is going to attract developers to these IDEs, especially the C# IDE when Microsoft is already giving away Visual Studio Express for free. Although it is lacking some of the features of the full version of Visual Studio for hobbiests and students, the market Borland seems to be trying to attract, these tools are great and free. I think Borland already missed their opportunity here

    --
    I love to deploy my packages
  38. Never mind that shit!! by $RANDOMLUSER · · Score: 3, Insightful

    We want Brief (remember UnderWare?) back!
    The best programmers editor evar! Globsub in a column-marked block? No problemo!
    Open source it!

    --
    No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    1. Re:Never mind that shit!! by Anonymous Coward · · Score: 0

      Yeah, I loved that editor. I used to carry it in a floppy wherever I went ...until I discovered the DOS Vim port.

    2. Re:Never mind that shit!! by BigCheese · · Score: 1

      Well, whoever modded you Flamebait was rude. I know a number of programmers who swear by Brief.
      It's a religious thing like vi or Emacs.

      --
      The obscure we see eventually. The completely obvious, it seems, takes longer. - Edward R. Murrow
    3. Re:Never mind that shit!! by NullProg · · Score: 1

      To Clueless Moderators: Parent post is not flamebait.

      Brief was possibly the best text editor ever made. It was developed by a software company called "UnderWare".

      1983 - BRIEF: The Underware corporation releases the BRIEF
      (='B'asic 'R'econfigurable 'I'nteractive 'E'diting 'F'acility) text
      editor, written by Dave Nanian and Michael Strickman. BRIEF was bought
      by Solution Systems, then bought by Borland.

      http://www.faqts.com/knowledge_base/view.phtml/aid /36113

      Enjoy,

      --
      It's just the normal noises in here.
    4. Re:Never mind that shit!! by An+ominous+Cow+art · · Score: 1

      Indeed. I'm devoted to emacs, but Brief was my first love among editors :-).

    5. Re:Never mind that shit!! by $RANDOMLUSER · · Score: 1

      Sigh. Getting modded "flamebait" for touting Brief on "developers.slashdot.org" - what's this world coming to? But it was my own fault for saying "shit" and referring to a cult editor that hasn't been seen since most of the mods were in diapers. And for assuming people knew that Borland had deep-sixed it.
      Thanks for sticking up for me. Looks like a clueful mod (?!?) gave me an "underrated" to make up.
      Still the best editor ever.

      --
      No folly is more costly than the folly of intolerant idealism. - Winston Churchill
    6. Re:Never mind that shit!! by RevPsycho · · Score: 1

      Delphi (and C++Builder too, I believe) has supported BRIEF emulation for many years. I don't believe it's complete emulation, but you can see some of what it offers here.

    7. Re:Never mind that shit!! by Anonymous Coward · · Score: 0

      They also killed another nice editor - CodeWright. It was a windows app and had an excellent BRIEF emulation.

  39. Re:Why use this over Microsoft Visual Studio Expre by NavySpy · · Score: 1

    Turbo Explorer editions are free, and have a complete, professional level feature set.

  40. "They're not even human!" by payndz · · Score: 1

    Is TurboMan related to Johnny Turbo, by any chance?

    --
    You must think in Russian.
  41. Visual Studio Express is free forever by ragingmime · · Score: 4, Insightful

    I thought that too, but then I double-checked Microsoft's FAQ: Effective April 19th, 2006, all Visual Studio 2005 Express Editions are free permanently. This pricing covers all Visual Studio 2005 Express Editions including Visual Basic, Visual C#, Visual C++, Visual J#, and Visual Web Developer as well as all localized versions of Visual Studio Express.

    We'll see if they ever update it, though.

    But yeah, this sounds like Borland is trying to compete with MS tools. Good for them! I'm all for companies giving a hand to folks who want to learn their tools... especially if we get free stuff out of the deal. :)

    --
    I produce electronic music and write little games. Have a look.
    1. Re:Visual Studio Express is free forever by Anonymous Coward · · Score: 0

      Wow, that's great. I didn't know this. Now, if only they'd ship it with XP. No, I don't expect a compiler to be installed on Ma and Pa's PC, but if you go into Windows Setup, the option to install a compiler should be there.

    2. Re:Visual Studio Express is free forever by serutan · · Score: 1

      Those darn socialist techno-hippies at Microsoft giving away free software will undermine the whole software market, at least according to independent analysts like Steve Ballmer.

  42. Where is "turbo java" by Trieuvan · · Score: 1

    I loved turbo pascal (18 years ago). I wish they have some sort of turbo java.

    1. Re:Where is "turbo java" by DelphLinux · · Score: 1

      You can download the JBuilder Trial that degrades to the JBuilder Foundation Edition at the end of the trial period... which is essentially the same thing as a Turbo Java... Either way, I wouldn't be too surprised if they released a Turbo JBuilder in the coming months. Go here to download the trial.

    2. Re:Where is "turbo java" by horati0 · · Score: 1

      You can download the JBuilder Trial that degrades to the JBuilder Foundation Edition at the end of the trial period... which is essentially the same thing as a Turbo Java... Either way, I wouldn't be too surprised if they released a Turbo JBuilder in the coming months. Go here to download the trial.

      JBuilder 200x is the worst application, IDE or otherwise, I have ever had the misfortune of working with. The Swing interface is so horrendously slow and laggy it makes me physically ill to watch a window redraw when moving a dialog out from in front of it. Navigating folders on a network drive to open a file takes so long that it makes me want choke someone. Anyone. And don't get me started on the app's insistence on asking if you want to save a changed project 40 million fucking times when closing it. Verily:

      Me: [make a trivial change to a project, don't need to save it.] File-->Close Project
      JCrasher:Select Project(s) to close
      Me: [thinking out loud] Hmm, well I only have one project open so there really isnt a choice here, but whatever. Select it, click Close.
      JCrasher:Select Project(s) to save
      Me:[disgruntled sigh] Select "None"-->Click "OK"
      JCrasher:Select Project(s) to save
      Me:[What the fuck.] Select "None"-->Click "OK"
      JCrasher:Select Project(s) to save
      Me:[What the FUCK.] Select "None"-->Click "OK"
      JCrasher:Changes to the selected project(s) have not been saved. Are you sure you do not want to save?
      Me:[FOR THE LOVE OF ALL THINGS HOLY -- AND WHAT THE HELL, ALL THINGS NOT HOLY -- NO NO NO I DO NOT WANT TO SAVE THE FUCKING PROJECT. I JUST WANT THE SCREEN THAT SAYS 'JBUILDER' TO GO AWAY, THAT CANNOT HAPPEN IF I KEEP GETTING ASKED STUPID FUCKING QUESTIONS. UNLESS THIS IS A JOKE AND I AM REALLY RUNNING 'ELIZA'. ] Click "Do Not Save"
      [JCrasher closes]
      [a nanosecond of Zen-like calm]
      Me:I fucking hate computers.


      I feel better.

      --
      The neutrality of this sig is disputed.
  43. Re:Delphi??? by shnar · · Score: 1

    It's not "pascal", it's "Objcet Pascal". Even your link to wikipedia proves this. Major differences between the two (kinda like saying Java is just C). -shnar

  44. Code::Blocks by MatrixCubed · · Score: 0

    "...students, hobbyist developers, occupational developers and individual programming professionals..."

    May I suggest Code::Blocks?

  45. Re:Delphi??? by Local+Loop · · Score: 1

    Has it changed any since version 6? I'm still supporting several apps written in that version, and the VCL libraries are IMHO a complete mess.

    That said, I'm still hooked on it for cost reasons, it is so much faster and cheaper to develop windows apps in Delphi Pascal than in VC++. Of course, these days, I believe the debate has moved on.

    Serious, question, not a troll, is it worth upgrading to the latest?

  46. Don't forget the silly keys by JMZero · · Score: 1

    I still use ctrl-insert and shift-insert for copy and paste. Hard habit to break.

    --
    Let's not stir that bag of worms...
    1. Re:Don't forget the silly keys by Uksi · · Score: 1

      Indeed! More and more software is using Ctrl+C and Ctrl+V these days... but I keep doing Ctrl+Ins and Shift-Ins... it just feels right!

    2. Re:Don't forget the silly keys by Uksi · · Score: 1

      What I meant was "using Ctrl+C and Ctrl+V exclusively"

  47. Re:Delphi??? by drinkypoo · · Score: 1

    Does it still use pascal's weird funky operators chosen simply to be different from other languages?

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  48. Three ways to justify "turbo" by tepples · · Score: 2, Insightful
    There's competition now, and most machines owned by hobby-programmers and students will cruise through the compilation process fast enough that the "turbo" brand doesn't offer a compelling solution like it used to.

    But some improvements could still possibly qualify for the "turbo" moniker:

    1. Borland may have improved its compilers' optimizers, allowing your code's inner loops to go "turbo". G++ leaves a lot of room for improvement.
    2. Incremental compilation and linking as the developer edits the source code, making compilation appear instant.
    3. Borland may have improved the RAD tools, under the notion that if Amdahl's law prohibits significant speedups from compilation, speeding up the human behind the keyboard is the best way to increase net productivity.
    1. Re:Three ways to justify "turbo" by Leonel · · Score: 1
      Incremental compilation and linking as the developer edits the source code, making compilation appear instant.

      Heh. Have you ever compiled Delphi code? It compiles applications with several hundred thousand lines in a few seconds. No time for you to go get some coffee.
    2. Re:Three ways to justify "turbo" by tomstdenis · · Score: 0

      Borland optimizers were always at least 1 or 2 gens behind GCC and the like. Watcom was far superior back in the day in terms of scheduling (which mattered more back in the 586 days). Intel has a decent optimizing compiler but benchmarks like what you linked to are misleading. What is ICC performance on ARM processors? How about MIPS? How about SPARC? Alpha? 68K? etc... The GCC folk have more to worry about than just performance on Intel x86 processors.

      Also as for "instant compilations" it's called a makefile. Build your objects, modify source, rebuild only the modified objects, etc. Nothing to see here, move along.

      That said, Delphi has a decent RAD toolset. Never really got into the whole "platform specific" coding thing but if I had to write a win32 app it'd be a close toss up between VC++ and Delphi. I was a "Turbo Pascal Kid" back in the day (hey, someone should form a TPK group) teaching myself how to write software with TP5 and TP6.

      Tom

      --
      Someday, I'll have a real sig.
    3. Re:Three ways to justify "turbo" by Haeleth · · Score: 1

      Also as for "instant compilations" it's called a makefile. Build your objects, modify source, rebuild only the modified objects, etc. Nothing to see here, move along.

      Except that Delphi does it faster and without needing a makefile. It calculates the dependencies automatically, and compiles whatever needs to be compiled. Instantly, whereas the average C++ compilation takes several seconds for me even with a makefile.

      Of course, the Delphi compiler is so fast that it's as good as instantaneous even if you force it to rebuild absolutely everything.

      It helps that Delphi is properly modular, instead of using C++'s braindead textual inclusion model (even precompiled headers can't make C++ compilation fast).

    4. Re:Three ways to justify "turbo" by tomstdenis · · Score: 0

      You're confusing a language with an implementation. Sure if you include 4M lines of Win32api headers it could be slower to build. But I have yet to see Delphi issue parallel builds. :-)

      I can build my LibTomMath project [~9K lines of source] in 2.3 seconds on my 2P Opteron 285 setup. :-)

      I'd say that's rather quick.

      Tom

      --
      Someday, I'll have a real sig.
    5. Re:Three ways to justify "turbo" by Halo1 · · Score: 1

      I can build my LibTomMath project [~9K lines of source] in 2.3 seconds on my 2P Opteron 285 setup. :-)

      I can compile and link the Free Pascal Compiler (158612 lines of code including comments) using itself in 15.9 seconds on my G5/1.8GHz (using one cpu). That's 9975 loc/s, compared to your 3913 (and you were possibly even using two cpus?).

      And guess what: people still sometimes complain about how "slow" our compiler is compared to Delphi. So don't underestimate Delphi's compilation speed...

      --
      Donate free food here
    6. Re:Three ways to justify "turbo" by tomstdenis · · Score: 1

      *cough* quality *cough*

      I'd say GCC does far more optimizations than FPK or Delphi.

      Honestly, how much time do you spend rebuilding your entire application? Chances are if you have to rebuild a million lines of code when you fix a typo in some function, then you need to really think about factoring your code properly. I can see if we were talking about 1000 loc/min vs. 1000 loc/sec or whatever. But if Delphi's only feature is that the [from the customers point of view] the SINGLE build is fast but the code generated sucks ... then you're stuck.

      Not this is a rag on Delphi. It has features other than the supposed "fast compile time". This isn't 1983 anymore. "slow" compilers typically spend that time on OPTIMIZING THE CODE. Back in the early 80s most commercial compilers performed the same limited subset of optimizations. Basic CSE, no unrolling/inlining, etc... GCC performs a lot of passes on the code to look for ways to optimize the code it produces. I think you should take some non-trivial function, pass it to GCC with "-O3" and then look at the assembly code it produces. You'll be amazed at the complexity of the output.

      Tom

      --
      Someday, I'll have a real sig.
    7. Re:Three ways to justify "turbo" by Halo1 · · Score: 1

      I'd say GCC does far more optimizations than FPK or Delphi

      Even if you turn off all optimizations GCC is still quite slow, in particular when compiling C++ code. Things got a lot better in 4.0 and 4.1, but it still not exactly fast.

      Honestly, how much time do you spend rebuilding your entire application?

      Since you ask: actually, since I work on FPC (not FPK, that name is long gone), I spend a lot of time rebuilding the entire compiler and run time library (often 2 to 3 times in a row, compiling the next iteration with the previous result) as a first quick check against newly introduced code generation or parser bugs.

      Chances are if you have to rebuild a million lines of code when you fix a typo in some function, then you need to really think about factoring your code properly. I can see if we were talking about 1000 loc/min vs. 1000 loc/sec or whatever. But if Delphi's only feature is that the [from the customers point of view] the SINGLE build is fast but the code generated sucks ... then you're stuck.

      As you know (since you mention it below), that isn't Delphi's only feature from the customers point of view. But it's nevertheless extremely convenient when you're used to it. People have been ranting since day one on Apple's Xcode list about the slowness of GCC compared to CodeWarrior (even when comparing a distcc'd build against a single threaded CodeWarrior build), also in debug mode (i.e. no optimizations). Compilation speed is far from a non-issue these days.

      Also, Delphi's code generator doesn't suck, it's just average. Which as it happens didn't matter all that much for x86 until now, since the processor itself optimizes a lot behind the scenes. Also, unless you are building numerical applications or 3D engines, most advanced optimizations such as loop tiling, all sorts of prefetching tricks etc have little impact.

      I took a course 2 weeks ago at a summerschool from David Padua who works a lot on compiler optimizations. His conclusion was all the time that basically all current compilers suck at optimizing, except in very specific cases and often only if you know how to write your code so the compiler recognises what you want to do.

      In my personal experience, a good register allocator and some peephole optimizations can get you a long way with most applications.

      GCC performs a lot of passes on the code to look for ways to optimize the code it produces. I think you should take some non-trivial function, pass it to GCC with "-O3" and then look at the assembly code it produces. You'll be amazed at the complexity of the output.

      I've already spent plenty of time looking at assembly code generated by various compilers, including GCC :)

      --
      Donate free food here
    8. Re:Three ways to justify "turbo" by tomstdenis · · Score: 1

      Even if you turn off all optimizations GCC is still quite slow, in particular when compiling C++ code. Things got a lot better in 4.0 and 4.1, but it still not exactly fast.

      It's not meant for that problem. GCC is meant to be cross-platform highly optimizing standards adhering compiler platform [not just for C but C++, F77, Ada, Java, etc]. If your goal is "lines per second" and not quality of the output use something like LCC.

      As you know (since you mention it below), that isn't Delphi's only feature from the customers point of view. But it's nevertheless extremely convenient when you're used to it. People have been ranting since day one on Apple's Xcode list about the slowness of GCC compared to CodeWarrior (even when comparing a distcc'd build against a single threaded CodeWarrior build), also in debug mode (i.e. no optimizations). Compilation speed is far from a non-issue these days.

      It's far from a non-issue usually because people write SHIT CODE. Then they put zero effort into the build system. GCC, in a single process, compile thousands of lines a second with high optimizations. If you factor your code properly and write a sane build script [e.g. makefile] you can easily perform on the fly adjustments and not waste a lot of time compiling. It's when you get projects that are written by people who think loc counts mean quality and that brute force is the only way to solve problems that you get into issues.

      Look at the Linux Kernel. [2.6 at least]. I can hack a single file and make a new kernel image in a matter of seconds. There are millions of lines in the Kernel [granted, not all of them are quality] and yet with a sane make system you can avoid rebuilding the entire thing. Wow.

      I really truly honestly 100% believe that if you spend too much time building stuff you need to refactor your code. It's really that simple. Keeping single functions per .c file for instance is a quick way to make the code accessible, CVS [etc] ready and keep compile times low.

      If you're the type that puts all of your applications code in one file, you're a nutbag and your opinions don't matter.

      I took a course 2 weeks ago at a summerschool from David Padua who works a lot on compiler optimizations. His conclusion was all the time that basically all current compilers suck at optimizing, except in very specific cases and often only if you know how to write your code so the compiler recognises what you want to do.

      "suck" is subjective. Do you maintain the position that GCC 4.1.1 is no better than GCC v1? Or how about Turbo C++ 3.0?

      I'd say they're far from perfect but they're not sub-ideal. GCC routinely produces output of ideal quality. It often makes use of exotic opcodes [like movzbl] instead of emulating them with more basic opcodes. It knows how to move code blocks around, unroll, inline, CSE, etc.

      Try comparing the time of execution of GCC itself when compiled with -O2 versus say -O0. Tell me that it doesn't optimize.

      Tom

      --
      Someday, I'll have a real sig.
    9. Re:Three ways to justify "turbo" by Halo1 · · Score: 1

      Even if you turn off all optimizations GCC is still quite slow, in particular when compiling C++ code. Things got a lot better in 4.0 and 4.1, but it still not exactly fast.

      It's not meant for that problem. GCC is meant to be cross-platform highly optimizing standards adhering compiler platform [not just for C but C++, F77, Ada, Java, etc]. If your goal is "lines per second" and not quality of the output use something like LCC.

      Just like with all programs, people don't use a compiler just because of one metric (there's always for example the ability to compile your program -- I'm not sure whether LCC can actually compile e.g. the Linux kernel or OpenOffice.org). Apparently for you compilation speed does not matter in any way. And you also seem to look down on anyone who does care about the speed of a compiler. That's all fine. I'm happy for you that this is one thing you do not care about in the least, since that obviously makes it easier to choose a compiler.

      I really truly honestly 100% believe that if you spend too much time building stuff you need to refactor your code. It's really that simple. Keeping single functions per .c file for instance is a quick way to make the code accessible, CVS [etc] ready and keep compile times low.

      If you have to refactor your code down to one function per source file (particularly nice for classes, or for different functions needing access to the same static variable) to keep compilation swift, there's something wrong with the compiler or build system you are using. This practice will also effectively kill any and all auto-inlining most compilers (including GCC) might otherwise do (except for static inline functions declared in header files).

      I took a course 2 weeks ago at a summerschool from David Padua who works a lot on compiler optimizations. His conclusion was all the time that basically all current compilers suck at optimizing, except in very specific cases and often only if you know how to write your code so the compiler recognises what you want to do.

      "suck" is subjective.

      Absolutely.

      Do you maintain the position that GCC 4.1.1 is no better than GCC v1? Or how about Turbo C++ 3.0?

      I'm not sure how I'm supposed to maintain a position I never took.

      I'd say they're far from perfect but they're not sub-ideal. GCC routinely produces output of ideal quality. It often makes use of exotic opcodes [like movzbl] instead of emulating them with more basic opcodes. It knows how to move code blocks around, unroll, inline, CSE, etc.

      movzbl is anything but exotic. You'd really have to do your best not to use that opcode in a code generator.

      Unrolling is still mostly black magic at this time, which is why libraries such as Spiral actually create dozens of differently unrolled and tiled versions of themselves when you install them on your machine, benchmark themselves for different input set sizes and then configure themselves to use the optimal unrolling for each input size and function you call for you particular machine. If you don't perform this sort of exhaustive searching, your unrolling can just as well cause a slowdown rather than a speedup.

      Inlining has a similar problem: apart from inlining calls when the inlined result is smaller than the calling sequence, inlining can also often cause unforeseen slowdowns (mostly because of different alignments caused by inlining, or instruction cache spilling). CSE is nice (and pretty common in contemporary compilers), but only goes so far and most of the time fails as soon as a function call to an external module is involved (really great if you put each and every function in a separate source file). That's why th

      --
      Donate free food here
    10. Re:Three ways to justify "turbo" by tomstdenis · · Score: 1

      That's all fine. I'm happy for you that this is one thing you do not care about in the least, since that obviously makes it easier to choose a compiler.

      I care about speed but I also am realistic. I require a highly optimizing flexible compiler more than I need a pascal compiler for x86. I routinely work on PPC, ARM, x86 [32 and 64-bit] boxes. Show me the copy of Delphi that works on all of those please.

      In the real world, speed is mitigated by properly factoring code. Having 100k lines per file is not "impressive" is poor project design and planning.

      If you have to refactor your code down to one function per source file (particularly nice for classes, or for different functions needing access to the same static variable) to keep compilation swift, there's something wrong with the compiler or build system you are using. This practice will also effectively kill any and all auto-inlining most compilers (including GCC) might otherwise do (except for static inline functions declared in header files).

      Welcome to the real world. If you are working in a team of 30 and you all need concurrent access to the tree putting all your eggs in one basket can make collisions a bitch to work around. Also, functions which are to be inlined are typically small macros which are best suited for a header file. If you are inlining 1000 line routines you need to rethink what you are doing.

      Code factoring has other benefits

      - Keeps the code organized, easier to find things
      - Easier to work in parallel on, fewer cvs/svn/etc collisions
      - Helps keep the build image smaller by avoiding linking objects not used (yes yes, smart linkers do exist but not universally)
      - Keeps build times down
      - Makes the project buildable on platforms with low amounts of memory

      At any rate, compile time matters but quality matters more. Delphi is a fast compiler because

      - It targets x86 only so the entire design is tailored for one cpu. It probably has less overhead because it doesn't have to have structures and routines in place to deal with non-x86 processors

      - It only compiles Delphi. GCC compiles C, C++, Java, Fortran and Ada.

      - It optimizes less than GCC, has fewer passes of optimization, etc.

      So really the comparison is meaningless. Delphi is fast because it DOES LESS than GCC. The speed has nothing to do with the fact it's Pascal derived as there are very fast C compilers out there.

      Tom

      --
      Someday, I'll have a real sig.
    11. Re:Three ways to justify "turbo" by Halo1 · · Score: 1

      I routinely work on PPC, ARM, x86 [32 and 64-bit] boxes. Show me the copy of Delphi that works on all of those please.

      As I mentioned, I work on FPC. We support all of those and more. In fact, we supported Win64 before GCC did. No, I do not think you (or anyone else) should switch to FPC for that reason. But FPC is also multi-processor and multi-platform (not as much as GCC, but it's generic enough to be able to do so without making the compiler any slower). In fact, its code generator is object-oriented and every single opcode which gets emitted requires passing through at least one virtual method call. Yet FPC is much faster than GCC.

      GCC is not a bad compiler compared to the competition (in terms of optimized code quality), but it is slow. It's not because it does more (because also without any optimizations it's slow), it's not only because it supports many platforms (FPC also does), it simply is a slow compiler. That's really all I said in my original post, and I stand by that point. You may think that's not relevant, fine, but other people do (including me, in spite of the fact that I'm not the imaginary person with 100k lines per source file you quoted)

      If you are working in a team of 30 and you all need concurrent access to the tree putting all your eggs in one basket can make collisions a bitch to work around.

      Collisions only occur if you edit the same code (or at least code only a few lines apart). Splitting functions into different source files doesn't change anything about this.

      The speed has nothing to do with the fact it's Pascal derived as there are very fast C compilers out there.

      And although there are much faster C compilers out there than GCC, Pascal compilers tend to be faster in general because Pascal is designed to be parsed in a single pass, while C is designed to be parsed in two passes (preprocessor followed by the regular compiler, although it may be possible to fold both into one pass). And no, this does not mean that Pascal is inherently superior to anything, that GCC is inherently inferior to anything, that you should put all your source code in a single file or that Delphi is the panacea for all development work.

      --
      Donate free food here
    12. Re:Three ways to justify "turbo" by Halo1 · · Score: 1

      Splitting functions into different source files doesn't change anything about this.

      s/Splitting functions into different source files/Putting each function in a different source file/ is what I obviously meant. Refactoring one big function in several smallers ones obviously does reduce potential collisions, but that's independent of whether you put the result in separate files or all in the same file.

      --
      Donate free food here
  49. Zzaapp! by bob7 · · Score: 1

    My RSS reader thinks the title is "Borland Announces the Return of the Turbo Prod." Since when are they in the cattle herding business?

  50. The free version... by advocate_one · · Score: 1

    Can I produce binaries that I can distribute for free, or are we hamstrung and have to purchase the pro version???

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    1. Re:The free version... by Anonymous Coward · · Score: 1, Informative

      Yes, you can.

  51. Fool me once, shame on you, fool me twice by unfortunateson · · Score: 1

    ... shame on me. Third time the charm? Not a chance.

    No way I'm going back to Borland for dev tools.
    In the late 80's, Turbo Pascal for the Mac was bug-ridden and behind on Mac system call support. A tech support call revealed they knew about it, and didn't care. The tech said that their sales were roughly half the number of copies in use, and it didn't pay for them to continue developing.

    In the early 90's, after learning Paradox DOS at a customer request, Paradox Windows came out claiming upward compatibility... but it turned out to be only of the data. Not even a compatibility mode for DOS screens and procedures. Worthless. It was easier to move the customer to Foxpro!

    So what's the benefit of Borland free toolkits?
    I've got GNU C++
    I've got FOSS scripting languages (Perl, Ruby, Python) coming out my ears.
    I've got Microsoft's "Explore" versions of Visual Studio, also free
    I've got Java with lots of free dev tools if I really cared

    No sir, no Borland for me.

    --
    Design for Use, not Construction!
    1. Re:Fool me once, shame on you, fool me twice by Anonymous Coward · · Score: 0

      Actually, it's "fool me once, shame on ... shame on you. It fool me. We can't get fooled again."

  52. Re:Delphi??? by Anonymous Coward · · Score: 2, Informative

    I'm actually a *new* Delphi developer. I've only begun using Delphi within the last 3 months, and I'll be honest, I fought using it tooth and nail. I was so certain that C# was so much better in every situation that I wouldn't even consider Delphi. However, we began doing development for some apps that would be run in WinPE, and I decided to fire up Delphi 2006 and give it a whirl.

    I was blown away. I created my application in less than 3 days (minus user testing) --- but the best part is that my app was *fast*. Nearly as fast as if it was written in C/C++. My app was moderately complex (or at least not of the 'hello world' variety), performing user authentication via SOAP connection, connectivity to SQL database and record inserts, XML parsing, and multiple forms.

    I have to admit, being able to code Win32 with drag/drop components that just work is refreshing. All without a framework or DLL runtime requirement. I am a Delphi convert, and plan to continue using Delphi to develop Win32 apps. However, I'm not a zealot and I know that C# has it's place and I plan to continue using it where it makes sense.

    The more tools that a developer can have in their toolbox, the better.

  53. Re:Delphi??? by Leonel · · Score: 1

    The VCL has evolved a bit, but no major architectural changes. The IDE has evolved a lot, with large changes. At first sight, some people like the new IDE and some people don't - but eventually everyone sees it's a lot better.

    The main enhacements are code productivity tools - refactorings, integrated unit tests, and some new language features. D2006 produces much faster binaries as well.

    I'd say yeah, it's worth upgrading. Try the trial version before to make sure.

  54. Re:Delphi??? by cruachan · · Score: 1

    The Delphi 2006 win32 compiler is an improvement, and the IDE is considerably better than version 6. I upgraded myself and a few months ago for the first time since Delphi 6 and am quite happy with that side of the purchase.

    However the .net support if for version 1.1, which sucks big time. I fail to see any reason to use Borland Studio on an old version of .net when Visual Studio is on 2.0. Indeed I feel more than a little cheated that I had to pay for all the .net stuff to get my hands on the win32 compiler.

    I've used Delphi since version 1.0, and Turbo Pascal before that, so Borland have a long legasy of goodwill from me. However they are in last-chance saloon now. I'll probably upgrade to 2007 when it arrives to get .net 2.0 support, but beyond that, unless NewCo manages to up their game, I suspect I will go elsewhere.

  55. Yay case mods! by 6Yankee · · Score: 1

    Cool! I've missed that Turbo button.

  56. New versus old. I stick with the proven old. by dinther · · Score: 4, Interesting

    I don't get it. Why does everyone want new tools all the time. Windows is still windows, A button is still a button and the communication protocols are supported accross the development platforms.

    I have been working with Delphi since version 3 and still tackle new projects today with Delphi 6 (Don't want the newer and slower Visual Studio lookalike IDE).

    Here at work I am cracking up lauging these days. Most of the dev team have moved to gadget-land using Visual Studio and C#. As a result they need to upgrade all the dev machines (Again) and find out that the resources sucked up by the bloatware .net platform leaves them with very little working power. There all stressed and tearing their hair out when a server spits blood because they can't see inside!

    In the mean time our old and trusty properly hand coded applications keep scaling up on ever more powerful hardware showing there is many more years of use in the old and proven.

    I believe I am more productive using Delphi today than a whole line up of fancy Microsoft fanboy developers because I have access to absolutely amazing free library source code build and refined by users over the years. A massive Delphi and Windows API knowledge base indexed by Google newsgroups, a solid grounded knowledge of my tools and libraries and last but not least a very supportive Delphi user base.

    I hope this Turbo initiative will bring more developers to their senses and start coding again instead of playing with shiny black box Microsoft crap.

    1. Re:New versus old. I stick with the proven old. by Windcatcher · · Score: 1

      Hear, hear. I just bought Delphi 2006 and within four days I was back to my trusty Delphi 6.

      - Delphi 6 has WAY better help (what in God's name were they thinking when they changed it?)
      - The classic MDI interface is easier to work with
      - Being a native Win32 app, the IDE is way faster

      Delphi 6 came out in 2001, and for Win32 development it's just as useful to me as it was when I first bought it. I seriously don't understand the C# zealotry. Delphi is simply killer.

    2. Re:New versus old. I stick with the proven old. by dinther · · Score: 1

      Oh god yeah, I didn't even get started about Delphi 2006. My boss kept suggesting we should "upgrade". As the senior developer (And apperently supposed to be keen for new toys) I finally caved in and let them buy it. Delphi 2006 is now sitting unused in my desk. I tried it. It's IDE is stupid and slow (Like Visula Studio's) because it doesn't let me easily use my multiple monitors. Besides it doesn't offer anything that I want to use.

      The context sensitive help is not so sensitive (Nor sensible) anymore. The old Delphi 6 Help gets right to the point without any fluff or crap. This stupid CHM help is just so slow to load!

      They also made the IDE too "smart" because it thinks it knows what you want to look at which unfortunately is not always what I think I want to see. Did I mention IDE crashes?

      I am still apprehensive about this Turbo delphi though. Hopefully they stick with the old delphi IDE.

      Thing is, why would a skilled carpenter swap his razor sharp old hardened steel chissel for a new fancy unproven one with plastic handle? When you know your skill and tools you can't be beaten.

    3. Re:New versus old. I stick with the proven old. by BubbaJonBoy · · Score: 1

      Glad to see someone else shares my opinions. I always wondered why Borland swapped for a VS type interface when I loved the old SDI IDE. I also use multiple monitors and screen real estate rules when coding. And don't even get me started on the travesty known as CHM.
      Borland used to lead the way and somewhere along the management changes they converted from leaders to copy-cats. What a friggin shame. As an experienced C++, C#, and Pascal guy I always considered Delphi to be the supreme development environment and the VCL a true work of art. Damned shame the only ones with enough sense to realize what a great development environment Delphi was is our Euro brethren. American companies have traded "Buy IBM" for "Buy Microsoft". Bunch of friggin sheep...
      Regards,
      Jon

    4. Re:New versus old. I stick with the proven old. by dudeNumber4 · · Score: 1

      You're all crazy. The delphi compiler has always been fine, but the IDE sucked until BDS 2006. The archaic multiple window scheme in the old versions always drove me crazy; now everything slides in/out when I need it. The refactoring tools aren't as good as the current version of VS, but they still rock. I hate the pascal language with a passion, but this IDE makes it bearable. As for not joining the .net revolution, you're not going to be able to avoid java or .net forever (.net the logical choice because it built on java's mistakes). That "massive Delphi and Windows API knowledge base" is EOL - sooner or later you must move on. Better sooner than later.

    5. Re:New versus old. I stick with the proven old. by dinther · · Score: 1

      Yes, I have heard your arguments many times before. In fact about 7 or 8 years ago everyone jumpend on the Java bandwagon. Even Borland released a Java development environment. I refused and saw the same old mistake all over again. Cross platform compatible code. Trying to build a language that runs on anything and as a result running poorly on everything.

      Jave came and Java went. Man Java even killed some big software products that shifted to Java. In the past they tried it also with home computers. In the early days of home computing (Before PC clones became popular) Phillips and some Japanese companies decided on a computing standard MSX or something like that. "Lowest common denominator" so it sucked.

      Now we do it again with .net. I may be proven wrong if Windows Vista comes out (Don't even dare to say "when") but as things stand now .net is slow too.

      IDE is a pure matter of preference. Many people cringe seeing the many windows I have open but on my dual monitor dev platform but it works wonders for me. I do a lot of custom VCL's stuff to build new UI controls and the ability to see the program painting on one form while having full access to debugging the source is brilliant and impossible on those new fangled IDE's

    6. Re:New versus old. I stick with the proven old. by dudeNumber4 · · Score: 1

      Java came and Java went? Huh? Regardless, the cross platform aspect of Java isn't replicated in .net. .net will probably last alot longer than Java has/will. .net is too slow? For what? Are you writing real time applications? I've seen some amazing applications written in .net and they don't seem slow. The load time is surely slow, but even then there are methods available to minimize that. I remember debugging paint operations. How is that not possible in BDS? Don't you simply need multiple monitors?

    7. Re:New versus old. I stick with the proven old. by dinther · · Score: 1

      I have both Delphi 2006 (VS style IDE) and Delphi 6 at work. I wrote test applications in Delphi using win api, Delphi using .net and Visual Studio .net. Of those Visual Studio was an absolute shocker in terms of application GUI refresh speeds and responsiveness. But I must admit I seem the only one around here who took offence to that but then again I am the only one here that actually cares how well a GUI works for our customers). Delphi .net fared much better but it could not get close to the smooth seamless responsiveness I get out of a Delphi Win api application.

      Wouldn't you think that I would accept working sharp chainsaw instead of a blunt old had saw to cut down the tree? The fact is, the chainsaw has no petrol in it and I can handle the old hand saw just fine.

    8. Re:New versus old. I stick with the proven old. by dudeNumber4 · · Score: 1
      Application responsiveness is no doubt important, but not the most important thing. Most people don't care that an application takes 100ms longer here and there.
      What's more important:
      • Time to market for new features.
      • Robust code that makes for stable applications.
      After a couple weeks using C#, I was far more productive than with years in delphi. The FCL was just as good (not speaking of UI) as the VCL and the JCL together.
      I think you can do more with a little less even in C# 1.0, but there's no doubt you can do more using 2.0 (with generics and, sparingly, anonymous methods).
      And with such a massive user base, C# / .net has far surpassed delphi in terms of sample code, free libraries, etc.
  57. A few kind suggestions: by Ancient_Hacker · · Score: 2, Interesting
    Borland: I've been using your products on and off since Turbo Pascal 1.0. You've had some real winners in there, and a few dogs. For the last decade or so, more woofers than winners. Please take these suggestions in the spirit that they're given:
    • I've seen hundreds of web sites, and yours is way down there around the bottom in terms of usability. I don't think it's changed much in the last ten years. Lots of fancy menus that reflect your corporate structure, not what we're interested in. Your download pages have been mostly unintelligible for almost a decade. Youre delphi download page is complete chaos. To download a trial copy you have to jump thru several hoops, fill out some useless marketing info forms, then separately login to get a key e-mailed to you. It's all too easy to get stuck going around in loops, again and again. Nothing seems to make sense or is integrated with anything else.
    • Your pzatch methodology is the worst I've ever seen, and I've seen Sun's. Patches are supplied in some strange file format, not clearly labeled as being a patch to fix what in what. I've tried several times to patch Delphi 6 and finally gave up, it's just too difficult, somewhat harder than cross-compiling gcc for RISC on a Palm Pilot.
    • Announcing you're "just about sold" is really unprofessional. It might make you feel a little better, but it doesnt reassure the customers. Half the time a company is sold is not for its products, but for its customers. There's a 50% chance we're not going to see great new Borland products, but instead coerced to be herded over to some other more-horrible toolset, like the resurrection of Symantec C.
    • We had some really great times together, but yuou've had a far-away look in your eye for ove a decade now. How about we just call it quits?
    1. Re:A few kind suggestions: by Anonymous Coward · · Score: 0

      Wow - exactly my sentiments. I even complained to Borland about their website (siting almost exactly the same complaints you make above) *5 years ago*, and not a single thing has changed since them. Not that I'd expect my lone voice to make any difference, but I'm sure I wasn't the only person to notice how much of a nose-dive Borland took once they embarked on the looney sidetrack they seemed have gotten wrapped up in.

    2. Re:A few kind suggestions: by pkphilip · · Score: 1

      I have been a long time user of Borland products - Turbo C, Turbo Pascal, Delphi, Borland C++Builder, Borland C++ and now BDS 2006.

      This is a company which has been on the fast track downhill for several years now. The management has been drinking the Application Lifecycle Management Kool-Aid for so long that they are drunk on it and cannot seem to think straight anymore.

      Their development tools are overpriced, their customer service is abysmal.. the list of complaints is long. This is really sad.

      I don't expect Borland to be around for more than 5 years unless something drastic happens (eg: the management team is completely replaced and the company goes back to its roots).

  58. All jokes aside by nurb432 · · Score: 1

    This is a good thing. The 'turbos' were a great learning tool back then, and rather useful too. Now that they are being brought back and updated to more modern systems, all i can say its its nothing but good..

    Many of us first learned 'modern' languages with those products..

    --
    ---- Booth was a patriot ----
    1. Re:All jokes aside by PigIronBob · · Score: 1

      I agree, still have Turbo C version 1. First IDE on the PC as well. AAAAHHHhh the memories.

      --
      You never catch me alive
  59. Worth a shot by Anonymous Coward · · Score: 0

    I've been expecting Borland to go away for years. I was surprised when Metrowerks imploded and got burned there (no good replacement on Mac, still) and I hate to risk it again, but....

    I have C++ Builder 5 & Delphi 6 (the last good versions of both: upgrading was a lot of $ for worthless .NET crap.) CPPB 5 is still a decent system for throwing stuff together quickly. It's quirky & buggy, to say the least, and has the absolute worst text editor I've ever seen, but it built standalones then better than MS can now and decent editors aren't hard to find. This may be a chance to get "modernized" (even if cut down) versions without having to sell a kid or two.

    The (free?) Explorer versions seem only to lack Control creation and IDE extensibility (maybe adding Controls to toolbars?) In my experience w/ CPPB 5:

    - building your own droppable controls is so difficult and so hard to get right (abominably documented and not working at all out of the box: even the wizard code doesn't compile) that I stopped trying: I put placeholders on the forms and create my own controls in code. I won't miss that feature at all.

    - I have no desire to extend any IDE (EMACS is wasted on me) and I really don't care if I can't add 3rd party controls to toolbars (i.e., it's not worth paying for.) VCL controls are much better than ActiveX (which I have totally banned from our products, even if source is available), but it's still rare that they're a real win, once you get them installed and work around the inevitable bugs and missing features.

    Worth a download! VC++ Express is very usable on my XP laptop (2003 won't install at all; Express took 5 tries but works now.) If this works out it will be great for small projects.

  60. My rant... by Yuioup · · Score: 2, Interesting

    I started using Delphi a bit late in the game. A few years ago I chose Delphi 6 because it looked pretty decent and I liked the way it simplified the Win32 API in such a way that we could get to developing software without too much hassle. Delphi 7 came along which I passed over because I wanted to wait for Delphi 8 and jump on the .NET bandwagon. When Delphi 8 came out I bought it...

    ... which was the biggest mistake I ever made. Delphi 8 was a such a POS I was shocked that people actually released software that bad. Like they say in Southpark, "You see, I learned a lesson today..." and boy did I learn it good.

    Ever since then Borland has been spiralling downwards into oblivion. Their best engineers walked out causing them to lag behind never being able to catch up again. Delphi 2005 was a POS and Delphi 2006 needed a couple patches before it actually worked. I never even bothered to upgrade and no I haven't tried the demos and no I don't give a shit.

    I regulary check out the borland.public.delphi.non-technical to see what's going on in Delphiland. Half the comments are from .NET haters who constantly preach about how they don't use dot garbage and claim that native code is the best. My reply to those people is that if you don't understand the advantages of .NET over native code then you have no business writing software.

    The other half of the comments are from the Delphi evangelists clinging on to the vain hope that Delphi will some day come back to its glory days and be the top IDE once more. All I can say to them is... can you feel the water around your ankles yet?

    The only chance that Delphi has is pure and unconditional open source. I've suggested open sourcing Delphi several times but always my suggestions have fallen on deaf ears. I get short-sighted replies such as "and how can Borland earn their money"? and "oooh.. I hope not!". Too bad because it's been proven time and again that money can be made with Open Source and Borland is precisely at the right time at the right place to pull it off. Oh well, I guess they're going to miss the boat ... again.

    END OF RANT

    1. Re:My rant... by Eli+Gottlieb · · Score: 1

      Google "Free Pascal Compiler" and "Lazarus Pascal IDE", minus the quote marks in the latter case.

  61. Re:Why use this over Microsoft Visual Studio Expre by RLiegh · · Score: 1

    You get an IDE? I thought that was with the pro version (and that the pro version cost $$$).

  62. Countdown by ISoldat53 · · Score: 1

    I thought the was the countdown to the next update.

    1. Re:Countdown by Bing+Tsher+E · · Score: 2, Funny

      It's the countdown to t_time overflow. (it's a 7-bit product)

  63. Re:Delphi??? by NavySpy · · Score: 1

    You are the man! Welcome to the club!

  64. Turbo Bullshit by fm6 · · Score: 5, Insightful

    No, they're not bringing back Turbo Pascal. They're just rebranding Delphi and Delphi-based products as "Turbo".

    Hearken, ye, to a Borland survior. (I wrote a good chunk of the API documentation in Delphi, C++Builder, and Kylix.) Borland somehow has always been run by people who know jack about managing other people. They can't implement the most basic corporate policies, like making people work on the stuff they were actually assigned to work on. So they fall back on Stupid Executive Tricks that they picked up at some seminar somewhere. When I was there, management was in love with "lifecycle management" tools, and actually acquired two vendors of them, neither of which actually had a usable product. But most often, the SET consists of simple-minded rebranding. Usually, it's just pointless, like bringing back "Turbo". But sometimes, they really screw up, like when they renamed the company "Inprise".

    Hate to say it, but Borland's pretty much irrelevent. Their last serious achievement was Kylix, which took too long to get out the door, and which targeted a market (Linux desktop developers) that turned out to be nonexistant. And that was 5 years ago! Since then, most of their key people have moved on, and their tools group has stagnated. The fact that management thinks they can sell it just shows how clueless they are.

    Delphi is still my favorite development environment. Or rather it would be, if I could bear to use it. Which I can't — it's just too depressing.

    1. Re:Turbo Bullshit by NavySpy · · Score: 1

      Dude --

      No need to be depressed. Delphi will soon be spun out of Borland and in the hands of folks that are totally dedicated to it. Borland spinning out the Developer Tools Group is the best thing that has happened to Delphi since it was launched 11 years ago.

    2. Re:Turbo Bullshit by Anonymous Coward · · Score: 0

      So Isaac are you the one who - having written "a good chunk of the API documentation" - was responsible for putting the phrase "Does something" into the API docs? Yes, and when the build guy was tasked with removing all the instances of "does something", which you never got around to fixing, you cleverly broke his script by using the phrase "does something else" instead.

      I hear the pubs department is running pretty lean over there these days, but lots of ex-Borlanders are coming back. You should send them your resume dogg. Tweedle-dee and Tweedle-dum both stayed with Borland after decimating the pubs department; they won't be working for DevCo, unless Tweedle-dum makes a last minute jump.

      I assume you can figure out who Tweedle-dee and Tweedle-dum are.

      PS- I always thought "does something" was hilarious.

      [irony of the century - verification word: "bridging"]

    3. Re:Turbo Bullshit by fm6 · · Score: 1

      Sorry, you're wrong. What's there to sell? Like I said, the key people are gone. That leaves the source code, and unless you're willing to spend a lot of money on good people to figure it out, that's worthless. There isn't enough money to be made from this product to justify that kind of expense.

      Selling the tools is just an executive fantasy. It was pretty near impossible when they first decided to do it. It will just get harder as time goes on.

    4. Re:Turbo Bullshit by Anonymous Coward · · Score: 0

      Their last serious achievement was Kylix, which took too long to get out the door, and which targeted a market (Linux desktop developers) that turned out to be nonexistant.

      Not nonexistent, it's just that Kylix 1.0 was a $paid-for beta that had horrible stability issues, and there was no cheap upgrade path to 2.0 and 3.0 (I think there was a 3.0). I wasn't going to gamble another $129 or $199 again. Instead I used C++, KDevelop and QT Designer which were solid, are even better today and still alive and well, and are free. Ditto with Eclipse.
      To compete, commercial IDEs (other than MS VS.Net, which has a locked-in market) will need to be so far advanced over the free IDEs that they will practically need to write perfect, clean code in response to your gestures in a 3D VR environment. I'd pay for that.

    5. Re:Turbo Bullshit by cachimaster · · Score: 1

      Isaac, here in Argentina Delphi is used a LOT. I myself have worked the past 3 years with delphi 6, with no plans of upgrade because it works great.
      And depressing why? you have read the MFC documentation? that's not depressing is maddening!
      The VCL help is great, and it has made my a lot of money.
      So, Thanks!

    6. Re:Turbo Bullshit by fm6 · · Score: 1
      Yes, I know how popular Delphi is in Argentina. And Poland. And the Czech Republic. And Russia. And Nigeria. And New Zealand. I sat through all the marketing spiels when I was at Borland. And, although its nice that folks like you can make money using Delphi to write software. But all the revenue from all those countries don't add up to enough to keep the product going.

      Yes, the MFC documentation sucks. (Of course, MFC has been replaced by .NET, but that documentation sucks too.) So what? Microsoft manages to dominate the marketplace anyway. And Delphi has long since blown its last chance to provide an alternative.

  65. Re:Why use this over Microsoft Visual Studio Expre by PigIronBob · · Score: 1

    Any IDE is but a clone of the old Turbo line. full stop end of argument...

    --
    You never catch me alive
  66. Re:Delphi??? by Haeleth · · Score: 2, Informative

    Does it still use pascal's weird funky operators chosen simply to be different from other languages?

    Sorry, I don't have a clue what you're referring to. Delphi uses Pascal's perfectly commonplace operators chosen to be similar to myriad other Algol-derived or -inspired languages.

    Just because you've never dared stray from braces languages doesn't mean that any other convention is "weird", "funky", or deliberately contrary, you know.

  67. Re:Delphi??? by DelphLinux · · Score: 1, Informative

    You mean like +, -, *, /? What about 'and', 'or', 'xor', 'div', or 'mod'? How are those "funky" compared to '==' '&&' '||' '^'? They seem pretty clear and descriptive to me. Perhaps you are referring to APL ;-)? Operator precidence is slightly different than C/C++, C# or Java... but not cripplingly so. In all fairness, Pascal does tend to be a little more verbose, but that is intentional in the design in order to encourage better self-documentation (yes, you should still comment your code!). Other differences include: The semi-colon, ';', is statement separator not a terminator, so there are a few places where it is optional and at least one place where it is illegal. The compiler is single-pass recursive descent. It is blazingly fast (on the order of >1M lines of code/minute on today's hardware). As a matter of fact, we find that the bottle-neck in the compiler is more on the I/O side than the actual compiling/codegen side. The produced code is very well optimized(yes, it *could* be better, but there are time/value tradeoffs being made).

    As I write this, work is proceeding to add new language features such as generics (parameterized types), partial classes (class fragments), and some other items considered very "modern" by today's language standards. The Delphi language offers a significant level of source compatibility between the native Win32/ia32 compiler version and the .NET/IL compiler version.

  68. I grew up with TurboPascal by Colin+Smith · · Score: 1

    Fantastic bit of kit, I wish I still had a similar environment. i've looked for years but nothing's quite the same, including the clones. Man I could develop quickly with that stuff. Look, no mouse! Mmmm TurboRuby...

    --
    Deleted
  69. Compete with M$ by Edward+Teach · · Score: 2, Informative

    I'm not sure how Borland will compete with Micro$oft for the student market. Students whose departments participate in the Microsoft Distribution Network Academic Alliance, get free versions of Visual Studio 2005 Professional, along with loads of other M$ software. Granted, it is for non-commercial use but they are full, un-crippled versions. I know, some would say that all M$ software is crippled, but you know what I mean.

    My students are instructed to bring CD-R's the first week of class so they can get their free VS 2005 Pro. I used to use Borland's Turbo products, many years ago when I was first starting out in college. I don't remember how much I payed for them but I do remember them being student friendly.

    How is Borland going to compete when college departments can pay $799 for the first year and $399 for each additional year of the MSDNAA and be able to give their students thousands of dollars worth of free software as well as install that software for free in their labs?

    --

    Setting his threshold to 5, Sparky eliminated most of the trolls on /.

  70. They might not have been able to. by Anonymous Coward · · Score: 0

    If I'm not mistaken, some of the more recent versions of their C++ compiler use the EDG C++ front end. It is very doubtful that they are able to release that code at all, let alone under an open source license.

    The front end is often the most complex and also must necessary part of a C++ compiler. As shown by GCC and other compilers, a common back end can be used. So if they couldn't release the C++ front end of their compiler, open sourcing it would be of limited value.

  71. Borland's antique software available by whitefox · · Score: 3, Interesting
    For those nostalgic types, Borland released "antique" versions of their software years ago: http://bdn.borland.com/museum/antiquesoftware/. The list includes
    • Turbo Pascal v1.0
    • Turbo Pascal v3.02
    • Turbo Pascal v5.5
    • Turbo C version 2.01
    • Turbo C++ version 1.01

    FWIW, I was a college freshman and my first programming class was "Programming Concepts Using Pascal". Rather than use the university's mini-computer (horrible edit and compile environment), I wanted something I could use on a PC. Other Pascal compilers at that time were prohibitively priced for a student at hundreds/thousands of dollars. A friend pointed me to Turbo Pascal and I bought my own copy at Egghead for under $90. My very first software purchase by the way. I was a loyal fan following the product line from TP3->TP4->TC1->TC2->TP5->TC++1->BC++2->BC++4->BC5+ +.

    With every iteration, they got a little more expensive even for loyal customers. Then they brought out the "Professional" versions and wanted more money - so I stopped.

    How does this relate? TP3 let me do everything and anything I wanted (no-nonsense license) at an expensive (for me) but reasonable price. For the hobbyist or beginner, they will get frustated very quickly with the limitations imposed by the free editions but balk at paying $500 for a professional license. Offer them the professional level software with a no-nonsense license for $99 and Borland may see things turn around.

  72. Borland is confused! by ikhalil · · Score: 2, Insightful

    Apparently Borland is a company that doesn't really know what they want and are with a blurred strategy! At some point in time they decide to wash away the name they built and their long lasting achievements. And a couple of years later they are longing to the return of the very old days! They are in the business of building excellent (really excellent) development environments and gaining enormous acceptance and market share and then abandoning their products/names as if it has never bee theirs!!!

  73. always was, borland mba humour below by sjwest · · Score: 1

    I've a copy of professional jbuilder 4 somewhere, some smart marketing executive thought i'd cough up $2000 usd for version five, i declined, along with version 6, they gave up postal marketing me after that.

    Borland was always famous for its employee cockups

    in a prior crisis they employeed too people called 'smith' the bright mbas in the hr dept sacked the smith that worked on products, but kept the mail room employee called smith on. Pink slip smith was invited to work at microsoft, he was not due to be fired but was.

    It made the it press then it was humourous - it flagged them for me as a screwed up it firm back then.

  74. class1.o class2.o class3.o class4.o: class4.h by tepples · · Score: 1
    What is ICC performance on ARM processors? How about MIPS? How about SPARC? Alpha? 68K? etc...

    Offtopic unless Borland cares about those markets. If Borland software can beat G++ even if not Intel's compiler, it has a market. Even if Borland software can compile C++ faster at low optimization levels, it has a market.

    Also as for "instant compilations" it's called a makefile. Build your objects, modify source, rebuild only the modified objects, etc. Nothing to see here, move along.

    You mean like this?

    class1.o class2.o class3.o class4.o: class4.h
    If I change a C++ class's header file, watch all source code files that #include that header file get recompiled from scratch. But if the object files were changed incrementally as soon as I typed that semicolon to add one field or method, that would appear "turbo".
  75. Re:Delphi??? by soren42 · · Score: 1

    Thank you - I didn't mean my original post as a troll.... I seriously didn't see the value of Pascal (a lá Delphi).

    The Skype bit was an apt illustration of your point, however.

    --

    "Adventure? Excitement? A Jedi craves not these things."
  76. Optimization & fun with assembly by HaMMeReD3 · · Score: 1

    I also have fond memories of programming in turbo products, turbo pascal for dos was my second point of entry into programming, the first was quickbasic, then turbo pascal, turbo c++ etc. Turbo products used to be amazing for there time, they really helped get the job done, and write fast efficient code. I really liked how you could embed assembly into your code directly to create super-efficient subroutines and such. Nowadays, your lucky if your compiler even compiles into machine code and not into some bytecode that gets interepretted by 2 virtual machines and a scripting engine before before any machine level code is generated. I miss the ability to perform low level optimizations on my code. Shameless Plug, my site, link in the footer, friendly link/no ad's or popups. The site also adopts somewhat of a turbo product color scheme, I think the influence was on a subconscious level though.

  77. 1985 Trying to use Microsoft Pascal by Jimhotep · · Score: 1

    In 1985 I was using Microsoft pascal. 15 minutes to compile.

    Along comes Turbo pascal, 20 seconds.

    It was instant love.

  78. Re:Why use this over Microsoft Visual Studio Expre by DragonWriter · · Score: 1
    I'm sure this product is great, but what is going to attract developers to these IDEs, especially the C# IDE when Microsoft is already giving away Visual Studio Express for free.

    Well, Borland's giving their own "Explorer" versions for free, too; I suspect some people will experiment with both free IDE's, and, when given a choice, chose to pay for the more advanced version of whichever suits them better.

    There are some interesting features on the feature lists that may be competitive advantages compared to Microsoft's offerings.

  79. I'd try it by LesPaul75 · · Score: 1

    At this point, I'd be ready for just about anything that let me get away from Visual Studio. I've used it since it was 16-bit, and I've even tolerated all the weird interface changes they've made to the IDE over the years. Through version 7.0, it was pretty much just a matter of re-learning where the things I needed were, which sucks, but whatever. It wasn't a big enough productivity sink to justify switching to something else. But with version 8.0 (a.k.a. Visual Studio 2005), Microsoft has officially lost their minds. They're so determined to push ".NET" and "managed" code down our throats that they've ruined what used to be a really solid development environment. Going into the details of why it sucks so bad would be too far off-topic, and lots of other web pages have already summed it up nicely. But sweet Jeebus, does it ever suck.

    So bring on the Borland Turbo C++... There's never been a better timing opportunity.

    1. Re:I'd try it by Mongoose+Disciple · · Score: 1

      At this point, I'd be ready for just about anything that let me get away from Visual Studio. I've used it since it was 16-bit, and I've even tolerated all the weird interface changes they've made to the IDE over the years. Through version 7.0, it was pretty much just a matter of re-learning where the things I needed were, which sucks, but whatever. It wasn't a big enough productivity sink to justify switching to something else. But with version 8.0 (a.k.a. Visual Studio 2005), Microsoft has officially lost their minds. They're so determined to push ".NET" and "managed" code down our throats that they've ruined what used to be a really solid development environment.

      I don't know, man. It depends on what you're trying to do.

      I haven't had cause to write something in C++ since the 1900s. I wouldn't be surprised if VS2005 is ass for the needs of C++ development. If someone took a survey of what people are using VS for, I'm guessing C++ would be less than 10%. There are always going to be projects that demand the speed and power only a language like C++ can provide, but as time goes on I'd bet they're less and less of the big picture.

      It's safe to say VS2005 is geared towards .NET and managed code because that's where more of the demand is. For the kinds of projects I've worked on in the last year, it's been a great IDE.

    2. Re:I'd try it by LesPaul75 · · Score: 1
      I haven't had cause to write something in C++ since the 1900s. I wouldn't be surprised if VS2005 is ass for the needs of C++ development. If someone took a survey of what people are using VS for, I'm guessing C++ would be less than 10%.
      Not a chance. C++ is still the language used to get things done. I'm a game developer, and games are pretty much 100% developed in C++. Well, unless you count Flash and Java type stuff on the web, but that's all still very young technology. I've seen "Runescape," which is actually a decent 3D RPG, and I believe it's all done in Java. It runs entirely in a web browser. But in order to make that feasible, the 3D graphics have to be scaled down to a bare minimum. There's just too much overhead using an interpreted language to do serious work.

      The game industry is still what drives the entire computer industry, and C and C++ are still the only languages that are useable for developing (real) games. Things like .NET and Java are great for things where performance isn't really an issue, like web-based business and e-commerce and all that. But no one runs out and buys a $700 video card and a 4 GHz CPU so that Internet Explorer runs faster. Games are where the money is -- the game industry is now bigger than the movie industry -- and they're all done in C++. And a big portion of everything else continues to be written in C++, like the web servers that serve up those Java applets and .NET crap, the browsers that display them, and the operating systems that run them.

      Believe me, I'm no C/C++ zealot... There are tons of things I don't like about it. If something better came along, I would jump on it. But there just isn't any other choice for developing processing-intensive or graphics-intensive applications.
  80. Borland IDE's by euice · · Score: 1

    Last time I checked they were about to sell their ide business.

    Although I love object pascal, I have been forced to switch to other languages. They build great ide's but delphi 6 was the last really stable and perfoming version. My guess is that borland never recovered the loss of some key developers to Microsoft. (Anders Hejlsberg for example). The .net framework classes are just an improved version of the VCL. Every delphi developper immediately sees the similarities between system.windows.forms and Delphi's VCL.

    And even worse: They discontinued kylix, so object pascal currently only runs on windows.
    And Visual Studio.Net (along with 3rd party plugins like resharper) has pretty much anything you need for smaller projects (if it has to be windows), so there is no obvious reason to buy an ide from borland. (i count together as a modeling tool )

    This is so sad, but true

    1. Re:Borland IDE's by tlacuache · · Score: 2, Informative
      so object pascal currently only runs on windows.


      No, I use it in Linux all the time. FreePascal and Lazarus are being actively developed and are very powerful. Most code you wrote in Delphi/Kylix can be compiled (most of the time with little or no changes) with FPC with the delphi mode compiler directive turned on.
  81. TASM by KC1P · · Score: 1

    How about Turbo Assembler? Actually they still have it on the price list, but it's been frozen at V5.0 for many years. It would be nice to see this one brought back to life, I still use it (V5.0) every day, but when the day comes that I get forced to port all my stuff to x86-64, TASM will have to go.

    1. Re:TASM by Anonymous Coward · · Score: 0

      And for your next trick, porting x86 assembler to PowerPC?

    2. Re:TASM by KC1P · · Score: 1

      Somehow I doubt that porting my stuff from IA32 to x86-64 will be worse than the port from real mode to mixed 16:16/16:32 prot mode was, or the much more involved port from there to flat 0:32 386 world was (but even those ports were mostly rote, a few editor macros made a huge difference to the 99% of code that doesn't care about word size). Anyway it's funny that vendors that used to be satisfied with a large percentage of a tiny market (early 80s PC programmers), won't bother to lift a finger for a tiny percentage of an unbelievably huge market (present day PC programmers). One programmer (plus maybe one part-time tech writer) could maintain TASM (yes I'm offering!), but no. It's like Intel leaving the embedded microcontroller market, apparently having one division make a bazillion dollars a year from a stable market isn't worth their time when they could be a in a price war with AMD.

  82. .NET 1.1 by DragonWriter · · Score: 1

    Others have pointed out that a big point of this is likely to attract buyers for their IDE group which is up for sale. As I recall, the "released" version of Mono is an open source, cross-platform .NET 1.1 (+some later features) implementation that Novell has invested heavily in; a set of commercial development tools that target .NET 1.1 might be particularly interesting to Novell.

  83. You, sir are living in utopia by aoven · · Score: 1
    The only chance that Delphi has is pure and unconditional open source.
    As soon as Borland (or, to be precise, "DevCo", the new IDE business owner) did that, a bunch of open source enthusiasts would tear the code apart and Delphi as we know it would die.

    As a matter of fact, it is my opinion that proprietary projects migrate to open source mostly to die a slow death. At best, any reasonably complex project that forgoes this transition is at high risk of being mutilated.

    Yes, Interbase 6.5 did eventually spawn the Firebird project. But a db engine is quite different beast than a full blown development IDE with its own runtime and component library, so forgive me for being a skeptic in this case. Hell, just take a look at what JEDI project has become! And that's only the "component library" part of Delphi!

    Feel free to mod me down, but I'm honestly tired of listening to these "Free Delphi!" campaigns. Free it from what?
    So Borland made some terrible mistakes when trying to converge Win32 development with the new .NET paradigm. Delphi 8 and partially BDS 2005 were far from great, nobody is denying that. But the latest BDS 2006 really shows that they've learned from their mistakes. I'm sure soon-to-be-released BDS 2007 will be even better!

    Would you honestly want them to throw all this hard learned experience away and leave Delphi's future in the "capable" hands of the open source community?
    1. Re:You, sir are living in utopia by dbcad7 · · Score: 1

      I think when a project has a decent framework to build on, open source does pretty well with it.. ie OpenOffice and Firefox. Since I run Linux, I am probably a little biased considering everything I use is open sourced.

      --
      waiting for ad.doubleclick.net
  84. Re:Delphi??? by penrodyn · · Score: 1

    Funcky? I'm not sure what you mean? Do you mean things like 'not', 'or', 'and', 'xor' etc, I'm not sure I would class them as funcky, they're pretty obvious to me.

  85. Why no Turbo J? by GamerGeek · · Score: 1

    What about Borland JBuilder? No Turbo version of that?

  86. Offering $1m/year salaries by alexhmit01 · · Score: 2, Interesting

    Microsoft started offering top people $1m/year salaries to snag them. While this seems like the market working, it's not quite real when Microsoft can use its massive cash reserves to cripple a company. Basically, if Microsoft can offer 20 key people $1m/year over market salaries, then the competition is either bled for $20m/year, which can destroy smaller competition, and hasn't cost Microsoft a dollar, or they spend $20m to put a competitor out of business by stealing key people and use their cash to establish a monopoly position.

    This is blatantly anti-trust in the case of a monopolist, and was a lawsuit that I believe Microsoft settled.

    Borland made some boneheaded management maneuvers, but this was after Microsoft crippled the company, and Borland made a desperate effort to recover.

    Alex

  87. Sad really by sproketboy · · Score: 1

    Why don't they buy back dBASE and re-release dBASE III+? Yeah, that's the ticket!

  88. Delphi compile speed by Latent+Heat · · Score: 1
    The whole C/C++/Java culture is so ingrained that you just can't communicate to people about Delphi compile speed. There is nothing like it out there, and part of it has to be the Object Pascal language -- the Pascal language was originally invented for teaching yes, but also to make for a one-pass compiler back when passes meant something in the type of memory and file models in use. There was once an industrial buzzword of design-for-manufacturing -- you design a consumer product, not just with the consumer in mind but with pounding it out at low cost.

    The other part of it could be the Anders Heljsberg is an evil genius who just knew how to craft parsers and compilers better than anyone else. The evil part is that a claim has been made in these parts that the actual Delphi Object Pascal grammer doesn't have a spec the way the original Wirthian railroad tracks Pascal grammer did -- the Delphi grammer is supposedly proprietary and a trade secret, and that no one else can build a parser that handles all of the corner cases -- you might want a parser, not to build a competing Delphi but to build a smart editor, use Object Pascal has a kind of description language, etc.

    But if you think Anders Heljsberg a genius, evil or otherwise, how come C++ Builder is dog slow on compiles in comparison. There has to be something to the Pascal language.

    I am kinda switching over to Java Swing for the GUI, C++ through the JNI for the hardcore numeric stuff -- a person sees the handwriting on the wall about Borland longevity. I kinda want to get off Windows by the time Vista, Aero, and whatever Windows-specific GUI gobbeldygook takes hold, and Java looks attractive to me. It is easy to get spoiled by GC and some other Java hacks, but I miss the fast compiles -- javac is dog slow.

    It seemed that Eclipse has a lightning-fast Java compiler in it -- someone told that it doesn't use javac but uses some hot-rodded IBM thingy. Eclipse, on the other hand, is still something I am struggling with -- it is IBMish in its weirdness about a whole bunch of stuff -- how do you just take a bunch of .java files in a directory and call it a project? It doesn't like a directory that is already there, and it wants to create some other directory in some standard location instead of where you want it. Still working on that one. So even Java needs "make files" of some kind of external metadata to organize multi-file source codes. Object Pascal famously has all of the dependencies specified in source code as a feature of the language.

    If there are two features, no, make that three features! that make Delphi problematic for the future, they are 1) Delphi has some real solid Windows lock-in, especially since Kylix didn't go anywhere -- the Delphi extension to Pascal are quite Windows-specific even if you are not doing GUI programming, 2) while Delphi is great and everything, it is behind the times with collection classes and other library richness of everything from Java to Python -- what collection classes are there are also tied into the VCL and bloat non-GUI or GUI-non-VCL programs, and 3) well, Borland and the fact that everyone seems to be jumping off the Borland ship.

    1. Re:Delphi compile speed by Halo1 · · Score: 1

      the Delphi grammer is supposedly proprietary and a trade secret, and that no one else can build a parser that handles all of the corner cases

      Of course it's possible to build a parser which handles all corner cases, be it not in one shot since there is indeed no design document to base yourself on. But by now at least we (the Free Pascal Compiler) do support most of it.

      I am kinda switching over to Java Swing for the GUI, C++ through the JNI for the hardcore numeric stuff -- a person sees the handwriting on the wall about Borland longevity. I kinda want to get off Windows by the time Vista, Aero, and whatever Windows-specific GUI gobbeldygook takes hold, and Java looks attractive to me. It is easy to get spoiled by GC and some other Java hacks, but I miss the fast compiles -- javac is dog slow.

      You might want to have a look at Lazarus. Although the underlying Free Pascal Compiler is not as fast as Delphi, it's a lot faster than most other compilers (and javac). Have a look here for a small unscientific test. Can't compare to Delphi, because the compiler itself is not written in a Delphi-compilable way.

      For Java, try using IBM's jikes compiler instead (not to be confused with the JikesRVM -- jikes is simply a Java compiler, not a whole virtual machine).

      Eclipse, on the other hand, is still something I am struggling with -- it is IBMish in its weirdness about a whole bunch of stuff -- how do you just take a bunch of .java files in a directory and call it a project? It doesn't like a directory that is already there, and it wants to create some other directory in some standard location instead of where you want it. Still working on that one. So even Java needs "make files" of some kind of external metadata to organize multi-file source codes. Object Pascal famously has all of the dependencies specified in source code as a feature of the language.

      Java does specify the dependencies in the source as part of the language. You have to "import" all packages you need, much like a uses clause (and it allows for both more fine-grained and coarse-grained control regarding what you want to import).

      The only difference is indeed, as you mentioned, that packages should recide in a directory called the same (or in a jar file). This organisation however avoids problems you can have in Pascal if you e.g. have multiple units with the same name in different directories. It does not necessitate the use of "makefiles of some kind of external metadata" in any way though (unless you consider directories falling under that).

      If there are two features, no, make that three features! that make Delphi problematic for the future, they are 1) Delphi has some real solid Windows lock-in, especially since Kylix didn't go anywhere -- the Delphi extension to Pascal are quite Windows-specific even if you are not doing GUI programming,

      Most Delphi extensions can be perfectly ported to other platforms. FPC runs on Dos, Windows, Linux, Mac OS X, FreeBSD, Solaris, Gameboy Advance, ... and the supported basic features are the same everywhere (except for threading, which is not supported on Dos and some other lightweight platforms).

      2) while Delphi is great and everything, it is behind the times with collection classes and other library richness of everything from Java to Python -- what collection classes are there are also tied into the VCL and bloat non-GUI or GUI-non-VCL programs,

      I do agree with you here (in spite of the fact that there are some third party container collections for Delphi).

      --
      Donate free food here
    2. Re:Delphi compile speed by tomstdenis · · Score: 1

      Back in the DOS days I was using a compiler called Micro-C which was a "single pass" compiler as well and on a 33Mhz 486 I was compiling 10K/lines a second. The difference between Micro-C and GCC [for instance] is that GCC performs a hell of a lot more optimization passes.

      Borland C is neither a good C compiler [in terms of speed and standards compliance] or efficiency of code generated. It's a bad example to use.

      If you really want a contest you should do this

      1. Take equivalent algorithms [storage/size/speed]
      2. Take Delphi and GCC 4.1.1 and build the programs
      3. Measure the output size and time their executions.

      No customer cares if your program was built in 1s versus 10s. They only care if the program fits in their platform, does what they want and does it fast. Besides, with proper refactoring you can mitigate build times to a moot point.

      For instance, when I work on my projects I often build the entire tree once, then work on the file I want [I have one function per file so it's easy to isolate]. Then when I want to test it, I take a whopping 5s or so to build and link the test program. I certainly spend more than 5s auditing the code and working with the debugger so it's not a bottleneck in the process.

      Tom

      --
      Someday, I'll have a real sig.
  89. pascal by Mike_ya · · Score: 1

    No Turbo Pascal for .Net?

    so depressing

    1. Re:pascal by Anonymous Coward · · Score: 0

      What makes you think you think that? Turbo Delphi for .Net is what you are looking for.

  90. The latter part of the parent is silly. by tshak · · Score: 1

    Well, as long as forever goes with Microsoft (The VS2003 toolchain didn't take long to disappear).

    I wasn't aware that releasing a new version of a tool meant that the tool "disappeared".

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    1. Re:The latter part of the parent is silly. by LunaticTippy · · Score: 1

      If a shop inherited a vs2003 project and wanted to make a change to it, there is no legal way to get a vs2003 compiler. You can port to 2005, but that isn't always easy. We have a VB6 application we can't touch for just this reason. VB6 won't upgrade to anything.

      Some companies have a rule about using supported products only. If no more updates come out for vs2003 that'd mean such companies would be forced to port.

      Developing in a specific version of a tool is an investment. Being forced (for whatever reason) to upgrade, even for free, has a cost.

      --
      Man, you really need that seminar!
    2. Re:The latter part of the parent is silly. by nuzak · · Score: 1

      I didn't mean to imply that MS was going to renege, but they are rather known for being a flavor-of-the-month sort of outfit, and they might simply forget about it when another shiny toolchain comes around. This being visual studio, that seems less likely, but you never know. Just keep those iso's burnt to physical media just in case, and hope they still work on the next OS release.

      --
      Done with slashdot, done with nerds, getting a life.
  91. Please Mr Turbotwaddler, bring back Brief by mnemotronic · · Score: 1

    Codewright is dead. I'd like to say "bring back the Brief editor" which, as I recall, was owned by Borland. I'd like to, but now I'm using vslick. Your time, Borland, has come and gone. You tubed the products I used, so I had to find others. Now I like the replacements, so why change back? If we're talking TurboPython or TurboRuby, you might get my attention, but it had better be juicy enough to lure me away from the open-source alternatives.

    --
    The Russians have won. They have made the world a cesspool of distrust, greed, fear and hate.
  92. Why, It Was A POS by Anonymous Coward · · Score: 0

    It was memory limited, wasn't standard Prolog and in general was a bad hack. Why would anyone be interested?

  93. Off Topic by Brandybuck · · Score: 1

    "...including a video of the Adventures of TurboMan."

    Oh great. Yet another proprietary Windows/Mac/Linux only video. Remember last year when people actually used to curse Flash? Today it's the only format anyone will use. Why is no one concerned that Macromedia has a near total lock on online videos?

    --
    Don't blame me, I didn't vote for either of them!
  94. I remember when everything was Turbo by serutan · · Score: 1

    Back in the eighties it was Turbo this, Turbo that, everywhere you looked. Then in the nineties everything was Extreme, which got old pretty fast. Most recently a lot of things have been "On Steroids," which wore out even faster. It's kind of like the evolution of credit cards from Gold to Platinum to Titanium. I'm expecting a Plutonium card someday. Anyway, if we're going to resurrect Turbo then I think it's also time to bring back "o-matic."

  95. All we need now is by clickclickdrone · · Score: 1

    Phillipe Khan back and some more copies of his CD of 'sax music' and we're really going places. Will they relaunch Sidekick too?
    It will be interesting to see how this pans out though as on the face of it, this sounds like a seriously good move. Back in the day, many, many PC developers learnt their skills on Borland's cheap tools providing a ready market for the pricier 'pro' stuff. Obviously this time round they have MS's free dev tools to deal with so this will be an interesting battle for the hearts & minds of hobbyists and newbies.

    --
    I want a list of atrocities done in your name - Recoil
  96. Open Source Killed Borland. by seanyboy · · Score: 1

    Turbo Pascal was my first proper hobby programming language, the first programming language I bought myself. I had (have) a lot of love for Borland, and still remember the excitement of version 1 Delphi.

    Borland produced great hobbyist languages, and some of us hobbyists pulled those Borland products into the enterprise. Borland messed up a couple of times, made a few bad products and basically lost their shine. If I had the same choices I had back in 1990 that I have now, I'd still be pushing the Borland route.

    Unfortunately for them, hobbyists will now use one of the countless free & fun programming languages that are easy to use and install. Languages like Ruby or PHP. When they've cut thier teeth, they'll go get job in enterprises that insist on a proper programming language (microsoft, apparently). Borland have been cut out of the loop.

    This is not a moan at open source, but I can't help but wonder if Microsoft's best programming language competitor is being killed by the Open Source movemement & if open source languages effectively allow Microsoft to maintain a monopoly in this area.

    --
    Training monkeys for world domination since 1439
  97. Re:Delphi??? by scottprice · · Score: 1

    I am glad that you find it a helpful tool, as I do. It is nice and clean to read, and handy to be able to compile the same, or very similar code, in both Win32 and .net :)

    Just FYI the guys behind the FCL also were the ones behind the Delphi VCL, so the two frameworks may have a very similar feel when you are using Delphi and C# :)

  98. qt designer qmake assistant etc. by Anonymous Coward · · Score: 0

    with just a little web searching it's fairly easy to create a make-based build tree that uses g++ and qt's qmake. the qt book is full of example trees.

    use qt designer for RAD gui building (the gui is just am XML file) and finally cruft some help pages together and shove it into qt's assistant using a "-profile" DCF definition.

    now upload the whole mess into a backed up CVS server and ba-da-bing, runs like stink.

    this is the most productive set of development tools i've ever used, bar none, and it comes free on almost every linux platform...as long as you develop free software.

  99. Re:Delphi??? by chthonicdaemon · · Score: 1

    Pascal is a very well-designed language that features some really fast compilers. It may not be ideal for lower-level coding (the kind of thing you would use C for), but as a workhorse to solve numeric problems or for useful applications, it is really quite good. Some of the newer compilers also generate very efficient code. You can say what you want about Wirth languages, but the man knew something about them.

    Anyway -- I never really understood why people were so down on Pascal. It's legible (if a bit verbose) and has nice support for modules and the like. Perhaps you have no motivation to move away from the language you are currently using, but people using Pascal (or Delphi) may have no motivation to move away from them either.

    --
    Languages aren't inherently fast -- implementations are efficient
  100. Ahh, nostalgia by asteinmetz · · Score: 1

    PROCEDURE Beep; BEGIN Sound(880); Delay(250); NoSound; END; [Sigh] Life used to be so simple. I don't know how DevCo makes much money but I am happy to see the word "hobbyist" used again. The ubiquity of the internet has driven the focus of the hacker community to web-this and web-that. Back in my day the focus was on elegant algorithms. Byte and Dr. Dobbs introduced me to disciplines I never would have seen through code. Fractal Geometry, Cartography, Langugage Processing, Queuing Theory, Ray Tracing, usw. Now, what? Google Maps mashups? Bah! Kids today...[shuffling off to Amiga, grumbling, drooling, smelling badly]

  101. Re:Delphi??? by Anonymous Coward · · Score: 0

    //
    I was blown away. I created my application in less than 3 days (minus user testing) --- but the best part is that my app was *fast*. Nearly as fast as if it was written in C/C++. My app was moderately complex (or at least not of the 'hello world' variety), performing user authentication via SOAP connection, connectivity to SQL database and record inserts, XML parsing, and multiple forms. //

    Hmmm... pretty cool as for the novice. If this is truth then respect!

  102. 500 bucks? by CrankyWorm · · Score: 1

    500 bucks for a professional version?
    Comics as a promotional ad?
    .NET and C## oriented?

    All right, high school and college kids under stolen XP, knock yourself out...

  103. Re:Delphi??? by marcovje · · Score: 1

    It can be worthwhile for performance reasons. They made a whole bunch of minor enhancements (like function inlining across units (D2005) and redoing all the assembler and memory manager (D2006). (and of course they merged some horrible Delphi.NET language abhorrations back into D2005/6 but you don't HAVE to use them).

    If you do a lot of string processing, some more functions got standarised in strutils. Minor stuff, but hard to miss if you get used to it.

    I was maintaining an realtime image recognition program, and it allowed me to squeeze one more camera using the same software per stock box that we deploy. (+/- 30% increase) However I still work with D7, I only compile releases with D2006. The new IDE is dog slow.

  104. All this is part of Borland's struggle to get rid by Anonymous Coward · · Score: 0

    ... of the IDE tools.

    A few months ago in every occasion Borland was mentioning Delphi as a little cash cow, trying to attract the interest of possible buyers.
    Later they announced the price range by means of a little theater, one of their investors offered to buy Delphi for $100 M, but Borland turned down the offer.
    Finally they officially announced that the IDE tools are for sale because they can't focus on ALM tools while the IDE tools are round, LOL. IMO at least they should've thought of a little more convincing reason.
    When after 6 months they realized that noboby is crazy enough to buy the IDE tools they began these hopeless tricks.

    In other words Borland is saying: Delphi is a cash cow that we didn't sell even for $100M. However we want to sell it now, not that it's an old and overpriced piece of software that is bringing less and less money by every quarter, but simply because now we want to focus on ALM tools and we lose our concentration and if you don't believe us take a look at all this Turbo things and other activity.

  105. Re:Delphi??? by civilizedINTENSITY · · Score: 1

    Seems like there are a lot of people who followed .net to version 1.1 and stayed there. Is this perhaps like those corporations who stayed with NT for so long? It worked well enough? Or did 2.0 make mistakes?