@Anonymous wrote:
It's that simple. On a bandwidth limited system, you once per two weeks click "go online" and then "go offline", disconnect RJ-45 cable or serial cable if you use TCP/IP over RS-232. It's pretty reasonable, for what it is.
I understand your concerns, but... the software is in a strong and fast development mode now, it needs regular income.
Plus, you can use the 7.7.0 all you want with your old license files... so what's the problem?
I'm going to set you straight a bit here because you are writing without thinking on two very salient points.
#1. In regard to disconnected operation.
Permanent connectivity is a *huge* problem for the small percentage of the user base. I know, because I am in that 1% where I regularly spend 3 months or more in a location where there is *no* connectivity for long periods of time.
Australia has connectivity to 90% of the population ... that is *NOT* 90% of the country. In fact, connectivity in Australia is only around 30% of the total area. If you work in the remote rural areas it is completely normal to be without sort of communication unless you are using 2way radio.
Now .. before some bright spark barks up "Australias NBN" ... yeah ... lets not talk about that ... I have a site which has been offline for a touch over 7 months now so lets not go there.
So ... permanent connectivity is a "big" problem if you are in the 1% group. I am, but I will freely acknowledge that 95% of the Eagle user base is not. So it was a deal breaking issue with us (and I'm sorry but 14 days of "disconnected" use just does not cut it).
#2. I don't think that anyone actually said that subscription is innately bad. What people have been up in arms about is that this particular subscription implementation of the model absolutely stinks.
A model where you stop paying, but can continue to use your existing versions (without any entitlements to updates, etc) is I think perfectly fair, and I haven't heard too many people arguing that point.
To stop paying your subscription and then have the software essentially stop - effectively holding your design to ransom is bad.
I'm sorry but read-only open mode simply does not cut it - that is bad (it's not 100% evil - that is a model where you can't even *view* your files, and I have examples of software companies that have done that as well).
Now you can argue this all you like but it doesn't change the fact that as Autodesk has implemented it, it's an atrocious model for the user. Might be great for them, but as the user ... not so much.
The bit that Autodesk really *really* got wrong with this whole debacle was how they handled it.
They absolutely need to be reamed for not reaching out to their premium paid existing user base and saying "this is what we are doing... you will need to either accept or if this is untenable, you need to migrate off, and here is what we suggest".
Autodesk did *NONE* of these things. Instead they let the user base find out on their own, and that was an absolutely unforgivable sin.
You do *NOT* do that to your professional user base who are relying on a specific behaviour in a toolchain for their livelihood.
It might be legal, but it is unethical and downright slimy.
For people to defend them for this, it means that they are basically condoning this sort of deplorable corporate behaviour. This is *NOT* something one should be supporting in any way, shape or form. Anyone who does, has some serious ethical problems ... probably a lawyer or an MBA ... 🙂
/BGM