Enso2025
From APIDesign
(Difference between revisions)
(→Language & Libraries) |
(→Performance and Runtime) |
||
| Line 7: | Line 7: | ||
* Rely more on ''Y.js'': [https://github.com/enso-org/enso/issues/11477 execute Y.js and Insight together] & co. | * Rely more on ''Y.js'': [https://github.com/enso-org/enso/issues/11477 execute Y.js and Insight together] & co. | ||
* Usual speed ups like [https://github.com/enso-org/enso/issues/11846 Benchmark ... and speed it up] | * Usual speed ups like [https://github.com/enso-org/enso/issues/11846 Benchmark ... and speed it up] | ||
| + | * Towards '''Dual JVM'''! | ||
| + | ** [https://github.com/enso-org/enso/pull/12468 warning on non-AOT ready libraries] | ||
== Improving the GUI == | == Improving the GUI == | ||
Revision as of 08:30, 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 Benchmark ... and speed it up
- Towards Dual JVM!
Improving the GUI
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
