You posting this link and giving me a chance to read it has been a highlight of my day. The fundamental lispishness of JavaScript by way of scheme explains everything I hate about working with JavaScript after reading that essay.
Nothing is secure. That post is basically spreading FUD as far as I'm concerned. There isn't even a point of comparison to any other distribution platform/native toolkit.
I also trust browser vendors to focus on keeping stripped-down versions of their core products secure more than I just joe/jane schmoe the app developer that just learned how to use QT/Swing/whatever.
> That's the first type I think. The second type is the more HN-style professional programmer.
nah
> As a small P.S. to this, I think the middle ground is using the GPL for actual end-user applications, but leaving libraries and developer tools completely open with something like Apache-2.0 or MIT.
Thats closer. Non-reciprocal licenses are fine for projects that provide no value themselves. But for everything that provides direct value, reciprocal licenses like MPLv2 or GPL are better suited.
Even with the "Crazy Ideas" there currently is no reason to assume they would be blocked from being implemented, if only the resources for that were available. So, once the hard part of finding the resources for them is solved, why should one not put them on LO right away -- which is a much better maintained and stable base than the aging AOO?
> That's basically quibbling, though the OP did err in his history a bit. AOO existed before that point too, it just wasn't called AOO and it wasn't part of Apache; it was run by Oracle, and before that, Sun.
So OOo had:
1/ a different governance
2/ different copyright owners
3/ a different license
4/ different sponsors
5/ different contributors
6/ a different name
than AOO, but other than that it was totally the same?
"Other than that" being "own the trademark" here and only that. Just for fun, AOO didnt even use the trademarked term itself.
Even at the time of donation, LibreOffice had already gained a substantial set of the former Sun/Oracle developers: Stephan Bergmann (to Red Hat), Bjoern Michaelsen (to Canonical), Eike Rathke (to RedHat), Michael Stahl (to Red Hat).
Together with other former Sun developers like e.g. Thorsten Behrens and Caolán McNamara, LibreOffice had more of the old Sun developers than Apache OpenOffice had at any point in time. Incidentally, they also made a lot of contributions that allowed LibreOffice to strife past other derivatives: like build system cleanup, static code analysis and fuzzing, bibisecting.
