Well, another good reason to hurry up with a proper, digitally signed(legally binding in Estonia),
statement about the ParaSail stdlib license, a kind of statement that would actually hold in an Estonian/European court. The ID-cards can be obtained from Estonian embassies around the world for about 100€ (10*10€=100€). Placing an explicit statement about the ParaSail stdlib into the ParaSail source distribution would be a minimum, what the AdaCore can do. As it seems from this forum thread, the race seems to be on and history has shown times and times again that it is NOT the technically best solution that necessarily wins. Part of the context of my current post is the
which demonstrates that unless there are multiple parties developing the "core tools"(compiler, interpreter, source-to-source-translator, whatever-needed/preferred) for the given programming language by using some non-proprietary-standard, the copyrights can end up at the hands of some extortionists and the more popular the language, the greater the extortion opportunities. Even the Micro$oft learned from the Java mess and tries to shove the "Micro$oft Java" == C# intellectual property to a nonprofit
That is to say, just fixing the ParaSail stdlib legal statement issue is not enough, it's just a first step. The next step might be that there are forks like there are forks of the Chrome browser and Mozilla Firebird/Firefox browser. Say what You/me/whoever will about the technical aspects of the C/C++, the C++ is a _godsend_ from legal certainty point of view, because there exists not just multiple core technology providers, even the Java has multiple VM vendors, but the core technology(compilers, frontents, etc.) providers are well financed and UNDERSTAND that their business heavily depends on the core technology(C/C++ compilers). The same with the web "standards". Quotes, because there are so many to choose from and because they tend to describe dirty hacks that lack systematic approach. Dirty hacks they may be, but they are certainly hassle free from legal point of view, because they are not maintained by any single company or even if there is only one company that uses them, that company has at least publicly declared in the form of the IETF/W3C/etc. standard that anybody can re-implement it without paying or getting any licenses.
etc.
I hope that I'm mistaken, but as of 2019_07_01 I can't recall any languages other than JavaScript or C/C++ that would be that safe to use from legal point of view. Once upon a time, not long ago, I suspected that Pascal
might compete with the C/C++/JavaScript on being legally hassle fee and having a proper, really long term, support, but in 2019_06 (about a month ago, may be) I realized that actually the FreePascal case is just another Java-lawsuit waiting to happen, because it aims to be at least partly compatible with the Delphi, which is a proprietary language. The C/C++ is, what it is, but one of the C++ syntactic sugar option is the
which just adds another layer of dependencies and complexity on top of C++, but it can be a nice option for some corner cases. What regards to C++ replacement for Game developers, then there's also the
that has a nonprofit, a lot like the C# and FreePascal have. Without saying anything about the technical side of the C# and Haxe, I can tell that what I definitely do not like about the C# and Haxe, and Rust for that matter, is that their development tends to depend "too much" on the availability of money. The main reason, why I see that as an issue is that such projects will not survive, what I call as "financial winters", inspired from the term "AI winter".
Funding WILL run out at some point and then, unless there exist some set of fanatics that keep the project usable on modern hardware and operating system combinations, the project will not be usable. A very beautiful and positive example of a project that, in my 2019_07_01 very subjective opinion, will be able to survive financial winters, is the FreePascal/Lazarus project, because it really is maintained without any centralized funding or heavy monetary donations, but, as I described earlier, the FreePascal has that proprietary Delphi lawsuits dark shadow over it. I'm not totally sure, but I suspect that may be some extra primitive "poor man's ParaSail substitute" might be created by writing some C++ OpenMP code generator that uses some domain specific language that might be implemented by using the
("Lambda Jam 2015 - Robby Findler - Racket: A Programming-Language Programming Language ")
(It's basically about Racket macros, about how to create
source-to-source translators by applying text substitutions.)
SUMMARY_OF_MY_CURRENT_POST:
x) Projects that depend on large amounts of money probably won't survive _financial_winters_.
x) Intellectual property of for-profit companies tends to get sold during liquidation and as long as a programming language stdlib copyright (think of the Oracle and Java case) is owned by a for-profit company, there is a risk that the copyright ends up at the hands of extortionists even, if the stdlib is properly open-sourced.
x) Placing all of the programming language related intellectual property to a proper non-profit is the minimum smart thing to do in 2019. Even Micro$oft does it.
x) C/C++/JavaScript are old had have their baggage, but they are safe to use from legal point of view and their baggage assures that there exists enough motive/incentive to port them to all possible hardware and operating system combinations that are meant to run general purpose non-real-time applications in non-safety-critical manner. Very roughly speaking, the Ruby and Python interpreters can be seen as syntactic sugar for C/C++ for cases, where speed and memory consumption is not that critical. It's the C/C++ that keeps the Ruby/Python usable and if ParaSail/whatever_else will be used as a dependency of such huge investments like writing Ruby/Python/PHP/JavaScript/etc. interpreter and stdlib, then it better be legally safe to use for at least 30 years, with written assurances that stand in both, U.S. courts and EU courts, alike.
Thank You for reading my post.