Enso2025

From APIDesign

Current revision

In 2025 the Enso system has turned into really solid platform. Here is a curated list of important achievements:

The Year of Dual JVM!

• Towards Dual JVM!
  • Dual NI + JVM Mode for Loading Libraries
  • warning on non-AOT ready libraries
  • Running tests in dual JVM mode
  • Arrow format for LongStorage to make exchange between JVMs and Python possible
  • Fibonacci benchmark comparing hosted and dual JVM modes
  • Support for dynamic loading of native JVMs
  • Arrow like storage over ByteBuffer to allow dual JVM buffer exchange

Other Performance and Runtime Improvements

• Optimizing Enso distribution by not Wasting 100MB by Standard.Image
• Rely more on Y.js: execute Y.js and Insight together & co.
  • Launching ydoc-server together with language-server
  • Channel connecting two JVM instances
• Usual speed ups like
  • Benchmark ... and speed it up
  • 60% speed up....
• Tighten up execution semantics with ... when interrupting Enso execution

Improving the GUI

• Progress API to report status of computation to the GUI
• Telemetry via logging to give us insight into what users really do

Language & Libraries

• Encapsulation via private keyword
  • Types with private constructors can be public & co.
  • Prevent Meta access...
• Cleaning various APIs up
  • Reducing helper methods in ...
  • Designing Progress API
  • Moving >, >=, <, <= to types ....
  • Make Enso "conversion and equality oriented" language - cleaning up Enso RootClass in the tradition of jokes I like to tell... about OOP flaws
• Improving runtime type system
  • Allow -> Column&Any to let any visible type thru

List of 256 issues and requests in year 2025. The next year is Enso2026. The previous year was Enso2024.