There are a number of issues which need to be addresses around this, but lets look at this one: barrier to entry.
On the cost front, the barrier to entry is very low - every one can afford gEDA. Then you have a couple of other issues, which, to me, are all lumped together in a new users mind, like environment, UI, and usage style. In my (limited) experience all EDA/CAD users are working in a Windows environment. This means that not only are they beginning with a new programme, but they are also beginning with a new environment. Often people go on courses just to start using a CAD package, the environment is not an issue. Now when someone moves over to gEDA after using a Windows based CAD programme, they don't differentiate between the environment and the CAD programme. They are not sitting there going, "Oh, I don't know how scripting works in Linux", they are thinking, "How to I create a new footprint? How do I generate a netlist? Where is the button to do this?" The immediate effect of this is that the barrier to entry is significantly raised. Jumping over the technical hurdles means that significant time and effort will be expended *just to get started.* What has previously been intuitive is now much more complex. Then the question of "real" cost starts to arise in the users mind, "Oh bugger, if I don't get this design done by the end of the month I'm in big trouble - let me go back to the CAD package I know, or find one that I can afford, it will be quicker." The sooner a new user grasps the concept of the design flow, the sooner they will embrace the product. If they are unable to achieve this within their own desired time frame they will move on to another product. Free is just not a powerful enough incentive, and won't ever be - the ability to complete the required tasks is. _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
