Re: Embeddinator-4000 begetting an Ada-cross-platform future?

["Dan'l Miller" <optikos@verizon.net>]

Lucretia wrote:
> Another closed, i.e. proprietary, compiler isn't going to help Ada, another free one will. 

Anyone can have another open-source Ada compiler whenever so desire:
1) Fork the FSF copy, so as to (apparently?) have the proper license.
2) Put an LLVM backend on it.  Either modernize Dragon Egg itself or conceptually repeat the entirety of Dragon Egg's old work differently in a more-modern release of GNAT and GCC.
3) Indeed, even ASIS it to semi-automatedly drastically refactor/overhaul the Ada code in which GNAT is written.  Even do this gratuitously for no reason to inhibit merging it back into FSF easily (unless someone else develops the anti-refactorer to recursively unwind the deeply-accumulated divergent ASIS-assisted refactorings).
4) Always contribute all such evolution in GPL-compliant ways, such as on GitHub.
5) Go merrily on your way, never looking back at FSF (or at AdaCore).

The big problem is never begetting the open-source repository itself for a 2nd open-source Ada compiler.  The big problem is how to fund an open-source business model.  (Hence, why closed-source business models arise for entirely-different not-GPLed source-code bases.)

Conversely, I would pay relatively-small-but-still-substantial amounts of money (less than $1000 per year per seat) for a proprietary closed-source Ada toolchain so that I could write both nonportable/SDK-specific UI/UX and portable backend-processing libraries all in Ada on iOS, MacOS, and Android.  Being closed-source is a non sequitur if the affordable compiler vendor is fairly rapidly responsive to new Ada language definitions and to bug fixes and to having a VisualStudio/XCode level of IDE user experience (e.g., what JetBrains provides in ReSharper extensions to VisualStudio and in stand-alone IDEs for the JetBrains-supported languages {C++, C#, Java, Kotlin}).