On Fri, 28 Aug 2026 16:43:56 -0300, Kragen Javier Sitaker wrote:
Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
But J2SE was available in an open-source form, namely OpenJDK. So
they adapted that instead.
With respect, I think you may have gotten this wrong. Originally
they used Apache Harmony (presumably they preferred its non-copyleft
licensing) but switched to OpenJDK in 02016 in response to the
Oracle lawsuit
<https://arstechnica.com/tech-policy/2016/01/android-n-switches-to-openjdk-google-tells-oracle-it-is-protected-by-the-gpl/>
You are mixing up the language implementation with the library implementation.
On Thu, 27 Aug 2026 21:11:55 -0300, Kragen Javier Sitaker wrote:
the Python maintainers have adopted a policy of deliberately
breaking standard library backward compatibility in every point
release.
In what way?
They call it rCLremoving dead batteries from the standard libraryrCY ...
So they donrCOt want to keep accumulating legacy baggage that just adds
to the ongoing support burden.
Every open-source project does that. The key is to support the
important stuff that people care about.
Does anybody still want to use the rCLcgirCY module?
Sun rCLaurCY file format?
A Unix password encryption library that doesnrCOt keep up with current password encryption formats?
Yes. Although CGI was pretty costly when it went out of style in the[...]
01990s, hardware has improved dramatically, and CGI can now handle half
Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
On Fri, 28 Aug 2026 16:43:56 -0300, Kragen Javier Sitaker wrote:
Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
But J2SE was available in an open-source form, namely OpenJDK. So
they adapted that instead.
With respect, I think you may have gotten this wrong. Originally
they used Apache Harmony (presumably they preferred its non-copyleft
licensing) but switched to OpenJDK in 02016 in response to the
Oracle lawsuit
<https://arstechnica.com/tech-policy/2016/01/android-n-switches-to-openjdk-google-tells-oracle-it-is-protected-by-the-gpl/>
You are mixing up the language implementation with the library
implementation.
Your statement, rCLSo [the Android team] adapted [OpenJDK] instead [when
they could have chosen J2ME],rCY is not true of *either* the language implementation (Dalvik) *or* the library implementation (initially they adapted Harmony, and many years later they adapted OpenJDK).
Kragen Javier Sitaker <kragen@canonical.org> writes:
[...]
Yes. Although CGI was pretty costly when it went out of style in the[...]
01990s, hardware has improved dramatically, and CGI can now handle half
Why do you write years like this?
On Fri, 28 Aug 2026 20:27:04 -0300, Kragen Javier Sitaker wrote:
Your statement, rCLSo [the Android team] adapted [OpenJDK] instead [when
they could have chosen J2ME],rCY is not true of *either* the language
implementation (Dalvik) *or* the library implementation (initially they
adapted Harmony, and many years later they adapted OpenJDK).
rCLDalvikrCY was the original bytecode interpreter that Google came up
with for Android. That was not a rCLlanguage implementationrCY for any particular rCLlanguagerCY.
By rCLlanguage implementationrCY I was talking about SunJDK versus
OpenJDK.
I'm pretty sure they werenrCOt using the Sun JDKrCOs compiler from Java source to Java bytecode, because Dalvik couldnrCOt interpret the
standard stack-oriented JVM bytecode.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 55:42:13 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,709 |