there are plenty of good reasons to not move a specific component to a later rev) nor a way to handle merging parameters that might be in conflict. You can't open a design and get a report of where the design database and library databases are out of sync, nor any intelligent way to decide what should be synced (i.e. Absolutely no useful library revision control.(For him the lack of built in 3D output in PADS has him looking for a better option, as well as he felt that since the sale of Mentor that PADS is being under-invested in/left to die a quiet death.certainly CS 3D output is killer, but I can't argue against under-investment.)įor me, the three things that I really would like to see get addressed soon are: I would have liked to promote CS as a solid offering with a bright future for someone doing non-complex designs on non-daily basis, but really couldn't do that given the uncertainty. Those stagnant sales numbers then become the 'proof' that there's no market here and all of us that did buy into CS in the past will be tossed in the bin. I suspect at this point that many people that would consider switching to CS won't because of fear of spending time on a dead-end tool. It's going to become a self-fulfilling prophecy that it fails in the marketplace. IMHO Altium is shooting themselves in the foot (feet?) badly with no solid roadmap plans and no apparent commitment to a mid-level product. Only because I just had lunch with a friend today that's looking to move off PADS and thought CS might be a good fit and was asking me questions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |