UTF-8 is not new from python or go: it has become the default string format of all browsers, JS operates in WTF-16, which is as close to utf-16 as it can go without breaking existing content, macOS X has been utf-8 for two decades.
Go and Python aren’t magical drivers when the entire industry has already moved in that direction.
It did not. The JEP still hasn’t targeted a version. There were a couple changes here that help enable Loom, including the reflection via method handles and the address resolution SPI.
It is hard to miss that impact of python and golang in the UTF and simple web server additions.
UTF-8 is not new from python or go: it has become the default string format of all browsers, JS operates in WTF-16, which is as close to utf-16 as it can go without breaking existing content, macOS X has been utf-8 for two decades.
Go and Python aren’t magical drivers when the entire industry has already moved in that direction.
It is not clear from release notes, but does anybody know if Loom (fibers) made into JDK 18 ?
https://wiki.openjdk.java.net/display/loom/Main
It did not. The JEP still hasn’t targeted a version. There were a couple changes here that help enable Loom, including the reflection via method handles and the address resolution SPI.