Enso2025
From APIDesign
(Difference between revisions)
(→Improving the GUI) |
(→Language & Libraries) |
||
| Line 29: | Line 29: | ||
** [https://github.com/enso-org/enso/pull/12031 Reducing helper methods in ...] | ** [https://github.com/enso-org/enso/pull/12031 Reducing helper methods in ...] | ||
** Designing [https://github.com/enso-org/enso/pull/12163 Progress API] | ** Designing [https://github.com/enso-org/enso/pull/12163 Progress API] | ||
| + | * Improving runtime type system | ||
| + | ** [https://github.com/enso-org/enso/issues/13390 Allow -> Column&Any to let any visible type thru] | ||
List of [https://github.com/enso-org/enso/issues?q=state%3Aclosed%20author%3Ajaroslavtulach%20closed%3A2025%20sort%3Acreated-asc 256 issues and requests] in year 2025. The next year is [[Enso2026]]. The previous year was [[Enso2024]]. | List of [https://github.com/enso-org/enso/issues?q=state%3Aclosed%20author%3Ajaroslavtulach%20closed%3A2025%20sort%3Acreated-asc 256 issues and requests] in year 2025. The next year is [[Enso2026]]. The previous year was [[Enso2024]]. | ||
Revision as of 08:37, 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
