> Traditionally, Java hasn't been seen as suitable for the 'exploratory' style of Notebook code development due to its compilation process.
AFAIK, the jshell API, introduced in Java 9, was all that was needed for notebook support. There have been several Jupyter notebook kernels built on the jshell API. There is also https://dev.java/playground/ built on the jshell API.
One factor is much of the Java world has been stuck on Java 8, notably Databricks: Apache Spark itself supports Java 11/17, but Databricks images are still Java 8 only. This will change with Spark 4.0, which is raising the minimum supported Java from 8 to 17. But for now, Databricks is Java 8 only, and Databricks notebooks support Python or Scala but not Java.
Another obstacle is lack of demand + interest in notebook developers and notebook platforms.
> Traditionally, Java hasn't been seen as suitable for the 'exploratory' style of Notebook code development due to its compilation process.
AFAIK, the jshell API, introduced in Java 9, was all that was needed for notebook support. There have been several Jupyter notebook kernels built on the jshell API. There is also https://dev.java/playground/ built on the jshell API.
One factor is much of the Java world has been stuck on Java 8, notably Databricks: Apache Spark itself supports Java 11/17, but Databricks images are still Java 8 only. This will change with Spark 4.0, which is raising the minimum supported Java from 8 to 17. But for now, Databricks is Java 8 only, and Databricks notebooks support Python or Scala but not Java.
Another obstacle is lack of demand + interest in notebook developers and notebook platforms.