Enso2025
From APIDesign
(Difference between revisions)
(→Performance and Runtime) |
(→Language & Libraries) |
||
| Line 21: | Line 21: | ||
* Encapsulation via '''private''' keyword | * Encapsulation via '''private''' keyword | ||
** [https://github.com/enso-org/enso/pull/12052 Types with private constructors can be public] & co. | ** [https://github.com/enso-org/enso/pull/12052 Types with private constructors can be public] & co. | ||
| + | ** [https://github.com/enso-org/enso/pull/12905 Prevent Meta access...] | ||
* Cleaning various [[API]]s up | * Cleaning various [[API]]s up | ||
** [https://github.com/enso-org/enso/pull/12031 Reducing helper methods in ...] | ** [https://github.com/enso-org/enso/pull/12031 Reducing helper methods in ...] | ||
Revision as of 08:32, 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
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
