Using Components and Support for Future Releases of the IDE!!!
-
Hello everybody, I like to use external components in our projects, I tend to look for the positive points in using them, but my boss prefered that I use only what IDE provides, his reason for that: Next Relaeases of the IDE, he is afraid that these components maybe not be supported well in future releases of the IDE, we use Delphi programming language, I think this problem is not a big deal in C#, what do you think about using externals components in Software Projects ? Thanks everybody!!!
-
Hello everybody, I like to use external components in our projects, I tend to look for the positive points in using them, but my boss prefered that I use only what IDE provides, his reason for that: Next Relaeases of the IDE, he is afraid that these components maybe not be supported well in future releases of the IDE, we use Delphi programming language, I think this problem is not a big deal in C#, what do you think about using externals components in Software Projects ? Thanks everybody!!!
can't speak for Delphi; however, I'll wager that he has NEVER encountered a support problem. How do I know this? I was in his shoes once. I suspect that someone tossed him some FUD. I recommend that you start with something simple (in terms of 3rd party controls). Minimize the risk. Tell him you'll buy dinner the first time there is a compatibility issue ;) Heh - forgot to mention - USE THE COMPONENTS when useful. I mean, don't do it just because you can - keep your brain engaged. But, you can save sooo much time.
Charlie Gilley You're going to tell me what I want to know, or I'm going to beat you to death in your own house. "Where liberty dwells, there is my country." B. Franklin, 1783
-
Hello everybody, I like to use external components in our projects, I tend to look for the positive points in using them, but my boss prefered that I use only what IDE provides, his reason for that: Next Relaeases of the IDE, he is afraid that these components maybe not be supported well in future releases of the IDE, we use Delphi programming language, I think this problem is not a big deal in C#, what do you think about using externals components in Software Projects ? Thanks everybody!!!
A lot depends on where you get them. Open source stuff is often not reliably maintained across releases. Commercial 3rd party stuff varies, some companies are here to stay and will support their stuff for many releases to come. Others seem to be in business to be bought out, once that happens, their products may or may not get supported. A little research goes a long way here: take the time to know who you're buying from, and what kind of experience others have had with them.
-
Hello everybody, I like to use external components in our projects, I tend to look for the positive points in using them, but my boss prefered that I use only what IDE provides, his reason for that: Next Relaeases of the IDE, he is afraid that these components maybe not be supported well in future releases of the IDE, we use Delphi programming language, I think this problem is not a big deal in C#, what do you think about using externals components in Software Projects ? Thanks everybody!!!
Well I agree with your boss, keep inside the standard product range wherever possible. While this is not an unbreakable rule in our teams it is a very strong one. We use Infragistics but ONLY the bits we REALLY need to achieve a goal. We NEVER allow open source tools to be used, if it goes wrong I want someone to yell at and get it fixed! Support costs are by far the largest expense with software, getting support resources (people) with specific tool experience or training them in the tool is a PITA.
Never underestimate the power of human stupidity RAH
-
Hello everybody, I like to use external components in our projects, I tend to look for the positive points in using them, but my boss prefered that I use only what IDE provides, his reason for that: Next Relaeases of the IDE, he is afraid that these components maybe not be supported well in future releases of the IDE, we use Delphi programming language, I think this problem is not a big deal in C#, what do you think about using externals components in Software Projects ? Thanks everybody!!!
Your boss' concerns are serious. Would you risk a slip on the flagships schedule, because those fancy extended drop down boxes just don't work on Windows 9? While your competition provides the vital support for those skin-implanted memory strips we'll have by then? I won't give you arguments "for" or "against", so that they can battle it out and the one with the most teeth wins. Rather, I will give you my guidelines when to buy and when to write your own. They come with reasons. Rule of thumb: If it's core to why customers by your product instead of from the competition, do it yourself. If it's what everyone has, buy it.
Other things: Need: Does the 3rd party component add significant value - e.g. does the UI become much easier to use? Buying a component to make things "look posh" might help in saturated consumer markets, nor for customers that pick you becasue of trhe funcitonality you offer. Time: Given enough time, all projects die. You don't want to support a dead UI component while you are still growing. Your risk is higher with longer-lived projects, when buying from smaller companies, and with uncommon libraries. Time, again: How long does it take you to throw out their component, and replace with something else? Choice: How many products of that type are on the market, and how many of them match your requirements? Choice it's good when it's not limited by needs. If of a dozen offers, only one makes it for the final decision, and this component wouldn't be your first choice for other reasons, hands away. Brazil[^]: If there's a large market for your particular needs, and your provider goes belly up, there is a good chance someone else will offer a way out, either buying the remains, or easing migration to their product. This is usually not permanent, but gives you time for your "exit strategy". Source code: There is a reason this one comes last. It is the ultimate protection against a 3rd party library going belly-up, but it is also your last line of defense, and a sirens lure. There are, basically, two approaches: 1. Make sure you can build them, and link against your build, and the application runs. Then, put the sources into a vault. When there is an upgrade to the component, or you make significant changes to yo
-
Hello everybody, I like to use external components in our projects, I tend to look for the positive points in using them, but my boss prefered that I use only what IDE provides, his reason for that: Next Relaeases of the IDE, he is afraid that these components maybe not be supported well in future releases of the IDE, we use Delphi programming language, I think this problem is not a big deal in C#, what do you think about using externals components in Software Projects ? Thanks everybody!!!
