Hi @jorge_garcia ,
The cloud aspects of Fusion really are a significant regression from Eagle and Fusion will never be a true replacement for Eagle as long as it is mandatory.
While Fusion might be able to act as a replacement for local revision control, that does not mean it is the best way to do it. If you are using another revision control system for all the other work (software, documentation, etc.), having to use a Fusion's revision management for CAD work makes management more complex. Just because you can do it, doesn't mean you should do it.
Yes, you can always export your schematics, layouts and libraries and then track those in your local revision control system. This is what I do, but it would be better if you could configure this as the default method. Allow Save to be an alias for Export instead of writing to the cloud.
The collaboration aspects of cloud storage aren't really very meaningful. At least not until multiple users can edit the same schematic and layout simultaneously. As long as it is one user at a time, it is not an improvement over doing the same thing will local storage. In fact, it is a bit of a step back since you are now subject to the vagaries of the internet and cloud's operational status.
I've been a paid user of Eagle since at least 2009. Perhaps earlier. I know I was using the free version for a couple years before ponying up for a license. I've been using Fusion since Eagle was absorbed. I like the tools and have a lot of time and knowledge invested in them, yet I fear that I might soon have to throw all that away and learn a new tool just because of the cloud issue (and auto-updates).
I currently work on military projects, though I am not employed by the military myself. While I've been able to get by when it was just me working on designs, we are starting to bring in other people who do work for the military and have their offices on a military base. They can't access the cloud from their regular computers. They have to use special stand-alone computers that are not plugged into the base's network and then use an access point through their phones to get to the cloud. This is obviously not ideal. The same problem applies to the auto-update aspect of Fusion. While I'm dealing with the military in this case, I imagine the same concerns could apply to any company that has strict rules regarding IP and network access.
If Fusion took advantage of GovCloud, that would probably address many of the issues, but from what I understand it is too expensive for Autodesk. It seems a simpler, cleaner solution would be to just make all the cloud stuff optional. Saves become exports and we deal with revision control ourselves. It's not as flashy as assigning a UUID to every revision of every file and storing it all in the cloud, but it is also simpler and easier to manage in many (most?) situations. I'm not suggesting Fusion toss all the cloud stuff completely. Just make it optional for those of us for whom it is not a good fit.
If Fusion is not able to do that and if Eagle is truly EOL (which it appears to be), then maybe the ECAD stuff that came from Eagle could also be integrated into another Autodesk product that does not use the cloud. I don't know anything about it, but perhaps Inventor is such a product.
This ended up being a bit longer than I'd intended to write, but I don't think the cloud concerns are as easily swept away as Autodesk might like and I'm really unhappy with the prospect that I (and all my existing designs) might have to migrate to a competitor's product with the learning curve and loss of productivity that entails.
mike