Enso2025
From APIDesign
(Difference between revisions)
(→Performance and Runtime) |
(→Improving the GUI) |
||
| Line 19: | Line 19: | ||
* [https://github.com/enso-org/enso/issues/12009 Progress API to report status of computation to the GUI] | * [https://github.com/enso-org/enso/issues/12009 Progress API to report status of computation to the GUI] | ||
| + | * [https://github.com/enso-org/enso/issues/13214 Telemetry via logging] to give us insight into what users really do | ||
== Language & Libraries == | == Language & Libraries == | ||
Revision as of 08:36, 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
List of 256 issues and requests in year 2025. The next year is Enso2026. The previous year was Enso2024.
Follow
