[ANN] Dyad: A New Language to Make Hardware Engineering as Fast as Software

Package Announcements
, , , ,
79

Thanks for the clarifications, Stefan.
They help, but the main strategic worry is still hanging:

Open modelling in Julia must not become collateral damage in the push for a slick, vendor-controlled ecosystem.

Wouldn’t right now every fresh component library have to run through Dyad if we want

  • the shiny SVG GUI
  • the “official” standard libraries
  • first-class Julia/SciML hooks?

In Modelica I have a choice of proprietary and open tools; competition can “do its thing” in principle.

To me the lock-in worries still remain valid:

  1. Spec—Without a public spec (or at least a living “grammar” documentation) how can anyone ever write an open compiler?
  2. Open ModelingToolkit libraries—What stops today’s MIT/BSD ModelingToolkit libraries from quietly sliding behind that paywall?
  3. Governance—How do we make sure Dyad complements, but not dictates the future of Julia modelling?
  4. FOSS author seat—Is there any chance for seat fees getting waived (or heavily discounted) for developers who ship their libraries under OSI licences?

See also:

9 Likes