

You cannot compete with giants without collaboration, despite they are competitors too (prisioneer's dilemma). I think small EDA developers should make something like OASIS (Organization for the Advancement of Structured Information Standards) and form a coallition to have a proper interoperability by using the same file format and provide importing filters of their former ones. There was EDIF (Electronic Design Interchange Format) but it seems little apps use it. You can import XML files in DipTrace Component and Pattern editors directly (without. National Instruments' OECL (Open EDA Component Library) If Eagle library has saved in version 7.5 or later it has XML format. They get rich by vendor lock-in and customer support. That's why big names in EDA stay alive, despite their software is very buggy. It's bad for competition, it creates monopolies and make users very unhappy with bad done software.

So 100% interoperability with Eagle is mandatory for my use case, no exceptions. If I were able to use a common file format or export to the formats of those apps, I would be able any other EDA software such as DipTrace. There's a zillion new file formats and some weak efforts at providing a standard one.įor example: It's mandatory for my school to send projects in Eagle for schematics and PCBs, Proteus for simulation. The EDA file format situation is similar than Microsoft Office before OpenDocument.
