== but for RAD 3-tier database access applications VB has outdone them all. It's main limitation (for this purpose) is its dependance on the Windows platform. ==
The main limitation for VB is that you can't use the Data Controls. They crash the app and OS occasionally (see VB newsgroups). Delphi Data Controls do not. So unless you actually prefer doing everything with hand coding, use Delphi.
Sorry for the late reply. >I'd just rather that the person reusing >understand exactly what the code does and how. The great thing about Delphi-style components is that the source code can be provided with the components if the creator so desires. Thus, if the user so desires, they can follow the code to discover exactly how the component works. It isn't like VB where any VC++ created components are black boxes.
Other magazines have taken over for PCMag and Byte in the code talk department. As for my last post, I was just pointing out that component developers do most of their work through old fashioned coding, though they can speed things up by having their component inherit from a component that comes closest in ability to what they are attempting. Good to Great programmers can distill their knowledge into self-sufficent components and earn money from and/or the thanks of lesser programmers.
== Maybe I'm just old fashioned, but I like to write code, not fill in forms. What do you think?== Great! You may have a lucrative future as a Kylix component developer.
Check out http://www.balticsolutions.com/bwd/ when it comes back on-line. It has references and links to lots of software and components that have been built through Delphi or C++ Builder.
One example can be found at http://www.ageofwonders.com
As far as system programming goes, Delphi can't really help. But it can help a lot of non-visual programs because it has lots of non-visual components that can speed up the programming of programs never meant to be seen.
Slashdot Mirror
== but for RAD 3-tier database access applications VB has outdone them all. It's main limitation (for this purpose) is its dependance on the Windows platform. == The main limitation for VB is that you can't use the Data Controls. They crash the app and OS occasionally (see VB newsgroups). Delphi Data Controls do not. So unless you actually prefer doing everything with hand coding, use Delphi.
Sorry for the late reply. >I'd just rather that the person reusing >understand exactly what the code does and how. The great thing about Delphi-style components is that the source code can be provided with the components if the creator so desires. Thus, if the user so desires, they can follow the code to discover exactly how the component works. It isn't like VB where any VC++ created components are black boxes.
Other magazines have taken over for PCMag and Byte in the code talk department. As for my last post, I was just pointing out that component developers do most of their work through old fashioned coding, though they can speed things up by having their component inherit from a component that comes closest in ability to what they are attempting. Good to Great programmers can distill their knowledge into self-sufficent components and earn money from and/or the thanks of lesser programmers.
== Maybe I'm just old fashioned, but I like to write code, not fill in forms. What do you think?== Great! You may have a lucrative future as a Kylix component developer.
Check out http://www.balticsolutions.com/bwd/ when it comes back on-line. It has references and links to lots of software and components that have been built through Delphi or C++ Builder.
One example can be found at http://www.ageofwonders.com
As far as system programming goes, Delphi can't really help. But it can help a lot of non-visual programs because it has lots of non-visual components that can speed up the programming of programs never meant to be seen.