Enso2025
From APIDesign
(Difference between revisions)
(→Performance and Runtime) |
(→Performance and Runtime) |
||
| Line 15: | Line 15: | ||
** [https://github.com/enso-org/enso/pull/12468 warning on non-AOT ready libraries] | ** [https://github.com/enso-org/enso/pull/12468 warning on non-AOT ready libraries] | ||
** [https://github.com/enso-org/enso/pull/13570 Running tests in dual JVM mode] | ** [https://github.com/enso-org/enso/pull/13570 Running tests in dual JVM mode] | ||
| + | ** [https://github.com/enso-org/enso/pull/13570 Arrow format for LongStorage to make exchange between JVMs and Python possible] | ||
* Tighten up execution semantics with [https://github.com/enso-org/enso/pull/12655 ... when interrupting Enso execution] | * Tighten up execution semantics with [https://github.com/enso-org/enso/pull/12655 ... when interrupting Enso execution] | ||
Revision as of 08:39, 30 April 2026
In 2025 the Enso system has turned into really solid platform. Here is a curated list of important achievements:
Performance and Runtime
- Optimizing Enso distribution by not Wasting 100MB by Standard.Image
- Rely more on Y.js: execute Y.js and Insight together & co.
- Usual speed ups like
- Towards Dual JVM!
- 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
- Cleaning various APIs up
- Reducing helper methods in ...
- Designing Progress API
- Improving runtime type system
List of 256 issues and requests in year 2025. The next year is Enso2026. The previous year was Enso2024.
Follow
