Hi Folks!
Let me just be sure and set the record straight on a few items then Ill go back to building awesomeness (ie electronics design, mfg, sim, 3D modeling, surface modeling, thermal analysis, generative design). What @macegr said doesnt accurately represent the opinions or views of Autodesk or our (read: my) overall product strategy or vision. I just want to take the high road here and at the risk of feeding the trolls, ensure I clarify a few important questions that are coming from people's genuine uncertainty or concern...And @macegr I welcome your feedback anytime. I just dont want to tip this in the direction of opinions == fact.
Firstly, we have gone to great lengths to ensure that the EAGLE XML files are actually still accessible however with any application that stores versions of files / data anywhere other than your desktop, we zip them. The FBRD, FSCH, FLBR files that fusion uses internally and which can be saved locally are zip files (raw eagle XML files can be exported to your desktop using the File->Export command). Rename them and unzip them and eagle XML is inside. We do this for speed in transferring the files to the web. Smaller file, smaller payload, faster performance. That's all. Nothing magical or sinister in there. But it also enables us to bundle a thumbnail so they show on the web as they do on the desktop.
We are not going to do away with this as there is no performance benefit to obfuscating what's inside. I would emphasize that virtually all other tools aside from EAGLE / Fusion360 electronics are indeed obfuscating the data (whether deliberately or not, I am not going to speculate) and we have taken- and continue to take a different path. ULPs still work in the new environment. SCR files (generally) continue to work but where they dont, we have plans to address these things in different ways (new menuing and display options in fusion mean changes to shortcuts and key bindings, etc will have to be mapped to a different UI/UX toolkit we use however one aspect of our test automation suite uses SCR files so it would make zero sense for us to scrap this). What's more, Fusion uses Python for scripting and I can only say that it would be, in my view, a "miss" if at some point we didnt create python bindings for all of this.
WRT interexchange files, they are a disaster and anyone that has ever rebuilt 00's of joints in a real, meaningful mechanical design knows the value of have true, parametric timeline awareness with every geometry. If you are not building commercial products or working across a team this may seem tolerable but having done this, I can tell you that creating a real binding between a sketch in a mechanical timeline and a boardshape in 2D PCB, and having spline curves that behave as spline curves and not approximations that fail to be editable...this is important to me. As you start to explore the tools, Id expect you'll find this to be the case too.
WRT desktop eagle, killing the bird is not particularly useful (I was more about Excite Bike than Duck Hunt...long-time fan of modding, sorry) and the SW you have will continue to run from the new entitlement. What we had done was to migrate your license to a Fusion license in a way that is transparent so that all EAGLE licenses (purchased from Autodesk) that are valid continue to enable EAGLE and will enable Fusion 360 as well. The only exception will be free where there was only a login, and you will have to register for the Fusion Hobbyist Version however that will enable EAGLE free as well.
Hope that clarifies and if you have questions or concerns, Im happy to try and answer things I can!
Best regards
Matt Berggren
Director - Autodesk
Fusion360, Electronics, EAGLE, Tinkercad