I found the dependencies in Visual Studio took some getting used to but that's a design issue, not a stability issue.
Some might find that a "convenient" reclassification to support your prior statements.
. I used MAKE until Visual Studio 5.0 because the IDE was useless for anything but a stand-alone EXE or DLL.
Okay, things become clearer. When using 20-year old technology of Microsoft, it works fine, but using anything in the last decade, certain products are "useless".
Then there was Borland's String class wherein the designers apparently didn't know what operator overloading was: no operator=() on the String class.
I'm sorry, Rod, but this is a really weak example. It isn't a bug (design issue) and it certainly doesn't persist.
I think you are quick to criticize, but when pressed, you simply don't have the details to back up your statements. Of course, I knew that three years ago.
Unfortunately, a lot of people read what you write and soak it up, because it DOES sound believable. But how about admitting it -- you don't know anything about Delphi or BCB because you haven't used them. I'm not even sure you've used Jbuilder, even though you are the Java Expert. |
