3 ms·
They seem to have become what Borland should have.
by Roboprog 10y ago
They seem to have become what Borland should have.
- vintagedave 10y agoEmbarcadero has those tools now, and those tools are very alive and kicking. Have you looked at them recently? (Except JBuilder, the Java IDE. Did you use it back in the day? What did you think of it?)
- Roboprog 10y agoI haven't used Borland's stuff (Turbo Pascal, Turbo C++, TP-Windows, Debugger) since the early 90s. I bought a copy of Delphi around 96, but never really used it, as my late 90s job was more off in the unix side of things by then (Linux at home, but IRIX/AIX at work). No employer wants Borland's languages now. I suspect Kotlin will suffer the same fate. When I first started doing ANSI C work in the early 90s (several platforms, including non POSIX), it was helpful to be able to use Turbo C[++] / Turbo Debugger to work on an otherwise standardized language. That seems to be what JetBrains is doing best, now.
- Roboprog 10y agoI have not used Embarcadero's Delphi, just their database client. I have used Free Pascal, though. Interesting, but no demand for it :-( The whole 90s C/C++ thing was such a debacle. Running C for app work in the internet era reminded me of "Hunt for Red October" - "Next, he'll be removing the safeties from his torpedos" - "you arrogant ass, now you have killed us!". Widespread internet adoption was the "extinction level event" for C/C++ apps. (along with faster processors and garbage collection) Anyway, if more companies had used an Algol descended language that actually did bounds checking, and made less use of points constantly, the crisis that forced Java adoption could have been avoided.
- Roboprog 10y agoThere are good high level languages out there that use automatic memory management. Java (language) just isn't high up that list. If I'm going to pay for a garbage collector, I want to do functional programming, NOT mutable OOP.