Yea - there's no way I'm doing a Term based license. Many others on the forum feel the same way. And Orcad - well ... I have gotten offers for Orcad X at steep discounts that tout "perpetual" multiple times. I'm already an Orcad Pro owner and have been using it for quite a while.
And I just found out that EMA-EDA has dropped the maintenance for the perpetual Pro licence. $1200 buck or so. A fraction of Altium's silly term thing.
In Orcad X 24.1, they now have a docked panel that looks a lot like the rules matrix the Altium is trying to push their users away from in favor of something that is similar to the constraints table that Orcad uses.
There's vid s on Youtube for Orcad X 24.1 that demonstrates it. All they need now is the schematic directives where you can embed rules in the directives. I use this alot.
As an Orcad user and having clients that use Orcad, they're jealous of the way that Altium can drive rules into the PCB from the schematic using graphical directives.
A constraint manager is a bit clunky and an additional step that has to be done to push design intent to the PCB.
For one, directives have a graphical representation - a visual cue if you will - that something is going on with the net on the schematic.
Two, as with directives you don't have to name each little net like you do with Constraint Manager (so you can find it in that huge spreadsheet).
Three, when I copy a section of circuitry with directives - those rules carry over to the new sheet, project, whatever. Esp with simple 2 pin unnamed nets. It just works. I have one design with over 24 power domains - each with their own ferrites, CM chokes, filters, etc.
So lets explore how silly using the Constraint Manager is when trying to reuse circuitry in the same project.
Well, to find every little net in the CM spreadsheet, ya gotta name every little net with some unique identifier. Hmmm. That can be a pain; for instance if you have a lot of power rails that have multiple passives in series with similar topology . For one naming every little 2 pin nets is a pain. Two, when you want to reuse that circuitry, no you have to:
- rename every little net label
- now go and redo all the constraints in the CM for those renamed nets.
Huh... that sounds silly.
So Orcad is trying to woo Altium users, and Altium is trying to woo Orcad users.
Good luck on the later - most large corporations - the one's that Altium is trying to get into - already get Orcad for free
I did work for PADS back in the late 1980's - did most of their stock libraries for a guy named Dave Castine. Funny that he ended up as the Altium regional manager in 2014. In 2015 he called me up and said, "I can't compete with free!!" in reference to his trying to get Altium in the larger corps that he had long term connections with.
They told him that since they buy chip design tools (in the millions of dollars), Cadence gives them full seats of OrCAD/Allegro for free. They said they can't justify buying a tool they get for free.
BTW: He left Altium that year and now works for Cadence.
Most of my commercial clients have gone to Cadence. It's cheaper, it's perpetual (tho dongled) and its an industry standard.
I really don't know what Altium's management is thinking... On one side they got free software that's offering a very affordable Redhat thing (that is perpetual/Free GNU FSF Software), and on the other is an EDA industry behemoth that's offering an equivalent product with Perpetual licenses at less than half the price.
As to the term licenses that Altium is forcing on everyone, well - there's some issues there. For one, I'm not into entering into any "partnership" with a third party so that I can access my intellectual property for perpetuity.
It's my IP - my designs. I don't need a partner.
I can see that if you're a fly-by-night company just trying to get a product out and then sell the company off, or you're a body shop that gets a short term sub contract to support a company that uses Altium, a term thing is probably the way to go.
But for me - I need access to my data - regardless of my relationship with Altium. I've been doing this for over 30 years (before that all tape up and drafting boards) and have gotten screwed before with systems that require interaction with a vendor to install a suite or have to deal with them in anyway.
I have data files for one of my patents I can no longer access. That sucks.
As to Altium and other SaaS suites, I don't know how they can limit liability - since they are construing an implied partnership and forcing a joint development environment... that EULA indemnity statement they all have might just be useless to them.
So Going forward, for us one thing is that since we work offline, we have standalone license. I can reinstall after a hardware failure and NEVER have to deal with them again.
I implore anyone that has a perpetual on demand license to see if they can download their ALF file in the Altium License Manager tab. I've had clients that had perpetual, that were switched to on demand with them knowing about it. That means they still have to engage with Altium to just open the software.
So for me, I can just stay at 24 or 25 and never have to deal with Altium again. In fact, I've done it in the past. I've used it since it was Protel back in the early-mid 90's and have gone years without renewing my license.
I've done over 3,000 designs with it. Most with AD6.9 and AD15-17. When 18,19, and 20 came out I refused to use it since they kinda destroyed a lot of features and functionality.
One project I worked on that was all done 6.9 was a major part of an award winning military system where we delivered the system way ahead of schedule, with more capability than first thought, and at 20% the cost to the US taxpayer (look up Dragon Spear in wiki and the AFSOC site).
So good luck to any Altium user in the future