Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:philosophy:java_downfalls [2022/03/24 00:01] i3_relativism missing certificate for that reson link needs to be removed |
en:philosophy:java_downfalls [2022/03/28 14:44] i3_relativism [Solutions] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Further details: | ||
- | * Java security: https:// | ||
- | * Criticism of Java: https:// | ||
- | * OpenJDK Trademark Notice: https:// | ||
- | |||
====== Java's Language Downfalls ====== | ====== Java's Language Downfalls ====== | ||
- | As free software activists, we all enjoy using the latest and greatest in free software, but we need to make sure that **the software we are using really does respect our freedom**. A lot of software | + | As free software activists, we all enjoy using the latest and greatest in free software, but we need to make sure that the software we are using **really does respect our freedom**. A lot of software relies and **depends on Java**, since it appears to be fully free software, nontheless we have **many concerns with implementation** |
===== What are the issues? ===== | ===== What are the issues? ===== | ||
- | Removal reasons: | + | Firstly the **OpenJDK** trademark policy |
- | * Trademark: | + | |
- | * Security: Java has been one of the most common infection vectors | + | |
- | * Packaging Standards: All current PKGBUILDs that were inherited from Arch are "dirty" in the sense that they download various pre-compiled and pre-packaged binaries. These are a risk to our users. To properly build them requires several hundred additional PKGBUILDs and the time to rebuild Java from scratch. This would require considerable effort | + | |
- | ** ** (jvm) [[https://issues.hyperbola.info/ | + | Secondly, on what comes to security |
- | In short, **Mozilla won't be happy with us applying patches and modifications** to their trademarked language | + | And Lastly, current or previously |
+ | In short, **OpenJDK won't be happy with us applying patches and modifications** to try to adress this issues in to their trademarked language** without approval, or the need for entire language rebrand, so it is belated atack to our users freedom**. For further references, [[https:// | ||
===== Big Picture ===== | ===== Big Picture ===== | ||
Line 26: | Line 19: | ||
===== Solutions ===== | ===== Solutions ===== | ||
- | * **Rebranding** the entire language to avoid the trademark restriction. Such as [[https:// | + | * **Rebranding** the entire language to avoid the trademark restriction. Such as [[https:// |
- | maintained by the GNU Project and FSDG-compliant distros could be the way**. However, we would need patches to adapt all Rust-dependant applications to the modified | + | maintained by the GNU Project and FSDG-compliant distros could be the way**. However, we would need **patches** to adapt all **Java-dependant applications** to the rebranded |
- | * Getting | + | * Getting |
===== Comparisons with other software trademarks ===== | ===== Comparisons with other software trademarks ===== |