Hybrid visual and textual functional programming.
Go to file
Hubert Plociniczak c54c3b7e9d
Eliminate circe-yaml dependency (#10326)
* Eliminating circe-yaml

This change adds our very-own YAML parser on top of SnakeYAML. Compared
to Circe parser on top of SnakeYAML. The advantage? In some not-so-distant
future we might actually get rid of circe and the related performance
issues.

The logic is similar to what circe does i.e. analyzing SnakeYAML to
build our own structure.
This change is not complete, as there are still some tests failing, but
most common Configs are already parseable.
We _could_ auto-generate some of the code but still some of the logic
would have to be tweaked by hand; the current logic has a number of
special cases, as I found out the hard way.

* wip: more tests passing

* Fix remaining tests in ConfigSpec

* Fixing YAML decoder for editions

Dropping circe as a decoder for Editions revealed some problems. Turns
out the current implementation had even more special cases to deal with.

* nit

* Allow for empty exports

* Mostly complete encodin part

Replaced almost all `toYAML` locations with SnakeYAML equivalent.
The encoding has to use Java collections for which there exists a
built-in support. If we were to use Scala collections we would have to
deal with tagging, at the very least.

* Remove the last remaining Circe's YAML parser

* Bug fix + further loop optimization

* removal of some dependencies

* Remove circe-yaml

Added a custom SnakeYAML Node updater to mimick the JSON -> YAML -> JSON
conversion needed for updating fields. The algorithm recursively follows
the key-path and inserts the desired Node. This is not a performance
oriented code on purpose.

* Fix compilation issues

`circe-core` was marked as `provided` but no one eventually included it
in the final jar, hence `NoClassFoundException`.

* fix licensing

* Removing obsolete circe definitions

* fmt

* nits

* s/SnakeYamlDecoder/YamlDecoder

* fmt

* Partial revert, PM needs JSON decoders/encoders

* style

* incremental compilation gone wrong
2024-07-05 09:32:45 +02:00
.cargo Custom Windows Installer & Uninstaller (#9815) 2024-05-07 16:22:11 +00:00
.github Remove ENSO_CLOUD_REDIRECT variable (#10322) 2024-06-20 13:16:01 +03:00
.vscode Run whole test/Base_Tests in native image runner (#10296) 2024-06-21 06:03:53 +02:00
actions/setup-build misc: bump wasm-pack (#3983) 2022-12-14 18:45:39 +01:00
app Tune Text.trim, fix for Text.split (#10445) 2024-07-04 22:24:56 +00:00
build Rename env variables (#10336) 2024-06-28 11:38:22 +01:00
distribution Eliminate circe-yaml dependency (#10326) 2024-07-05 09:32:45 +02:00
docs Add project/duplicate endpoint (#10407) 2024-07-02 11:39:43 +00:00
engine Eliminate circe-yaml dependency (#10326) 2024-07-05 09:32:45 +02:00
lib Eliminate circe-yaml dependency (#10326) 2024-07-05 09:32:45 +02:00
project ydoc-server is a separate module (#10156) 2024-06-07 12:56:42 +02:00
std-bits Implement Decimal support for Postgres backend (#10216) 2024-07-02 15:01:55 -04:00
test Tune Text.trim, fix for Text.split (#10445) 2024-07-04 22:24:56 +00:00
tools Eliminate circe-yaml dependency (#10326) 2024-07-05 09:32:45 +02:00
.envrc Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
.git-blame-ignore-revs More E2E tests; export default classes from modules (#8730) 2024-01-31 11:35:41 +00:00
.gitattributes Eliminate VCS TimeoutExceptions on startup (#8080) 2023-10-18 09:34:08 +00:00
.gitignore Custom Windows Installer & Uninstaller (#9815) 2024-05-07 16:22:11 +00:00
.ignore Refactoring: merge utils into prelude; merge workspaces. (#3151) 2021-11-10 14:36:08 +01:00
.jvmopts Update java formatter sbt plugin (#8543) 2023-12-15 14:45:23 +00:00
.node-version Vue dependency update, better selection performance, visible quotes in text inputs (#9204) 2024-03-06 15:34:07 +00:00
.prettierignore Syntactic synchronization, automatic parentheses, metadata in Ast (#8893) 2024-02-02 10:22:18 +01:00
.prettierrc.yaml Fix prettier config; run prettier (#6132) 2023-03-31 14:49:34 +02:00
.scalafmt.conf Bump SBT and Scalafmt (#1203) 2020-10-22 16:12:28 +02:00
build-config.yaml [CI] Provide latest FlatBuffers to the Engine build. (#9654) 2024-04-12 10:10:44 +00:00
build.sbt Eliminate circe-yaml dependency (#10326) 2024-07-05 09:32:45 +02:00
Cargo.lock Build script cleanups (#9931) 2024-05-13 13:56:28 +00:00
Cargo.toml Custom Windows Installer & Uninstaller (#9815) 2024-05-07 16:22:11 +00:00
CHANGELOG-2021.md Clear Changelog (#10077) 2024-05-29 11:27:32 +00:00
CHANGELOG.md Tune Text.trim, fix for Text.split (#10445) 2024-07-04 22:24:56 +00:00
clippy.toml Build script merge (#3743) 2022-10-10 23:38:48 +02:00
flake.lock Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
flake.nix Google Analytics events for opening and closing the app, and opening and closing projects (#9779) 2024-04-25 11:33:59 +00:00
LICENSE Set up the repository (#1) 2019-06-11 17:07:54 +01:00
package-lock.json Fix errors in GUI WebSockets (#10421) 2024-07-04 12:48:57 +00:00
package.json Remove ensogl-pack (#9407) 2024-03-18 12:18:18 +00:00
README.md Only Escape cancels edits (#9913) 2024-05-10 16:13:59 +00:00
RELEASES.md Add API for component groups (#3286) 2022-02-24 15:41:14 +03:00
run Build script: git-clean and cwd fixes (#8424) 2023-11-29 20:35:06 +01:00
run.cmd Build script fixes & improvements (#8285) 2023-11-23 21:19:31 +01:00
run.ps1 Build script fixes & improvements (#8285) 2023-11-23 21:19:31 +01:00
rust-toolchain.toml Bump Rust Toolchain (#9517) 2024-03-24 23:45:55 +00:00
rustfmt.toml remove unused rust modules (#9540) 2024-03-27 12:19:38 +00:00
vitest.workspace.ts Fix AST spacing (#9366) 2024-03-12 01:57:29 +00:00

Chat Actions Status Actions Status License License


Enso.org. Get insights you can rely on. In real time.

Enso is an award-winning interactive programming language with dual visual and textual representations. It is a tool that spans the entire stack, going from high-level visualization and communication to the nitty-gritty of backend services, all in a single language. Watch the following introduction video to learn what Enso is, and how it helps companies build data workflows in minutes instead of weeks.


Screenshot 2021-04-15 at 12 16 32

Enso's Features

Turning your data into knowledge is slow and error-prone. You cant trust tools that dont embrace best practices and provide quality assurance. Enso redefines the way you can work with your data: it is interactive, provides intelligent assistance, and was designed on a strong mathematical foundation, so you can always trust the results you get.

      Intelligent suggestions of possible next steps. Build workflows in minutes instead of weeks.
      Enso analyses the data, suggests possible next steps, and displays related help and examples. It lets you build dashboards, RPA workflows, and apps, with no coding required. Enso ships with a robust set of libraries, allowing you to work with local files, databases, HTTP services, and other applications in a seamless fashion.
      Learn more →
      Reproducible, trustworthy results.
      Versioning and visual data quality management allow you to trust the results that you get.
      Learn more →
      A powerful, purely functional language. Both visual and textual.
      Enso incorporates many recent innovations in data processing and programming language design to allow you to work interactively and trust the results that you get. It is a purely functional programming language with higher-order functions, user-defined algebraic datatypes, pattern-matching, and two equivalent representations that you can switch between on-demand.
      Learn more →
      Mix languages with close-to-zero interop overhead.
      Import any library from Enso, Java, JavaScript, R, or Python, and use functions, callbacks, and data types without any wrappers. Enso uses GraalVM to compile them to the same instruction set with a unified memory model.
      Learn more →
      A cutting-edge visualization engine.
      Enso is equipped with a highly-tailored WebGL visualization engine capable of displaying many millions of data points at 60 frames per second in a web browser. Currently, Enso includes a set of core data visualizations out of the box, and you can easily extend it with libraries such as D3.js, Three.js, Babylon.js, deck.gl, VTK.js, Potree, and many more.
      Learn more →
      Runs everywhere.
      Enso is available on macOS, Windows, and GNU/Linux, and the Enso IDE runs on web-native technologies. In time, you'll be able to run it in the web-browser, giving even your tablet and phone access to your data.
      Learn more →

Getting Started

An example Enso graph



Enso Source Code

If you want to start using Enso, please see the download links in the getting started section above. Alternatively, you can get the IDE here. This section is intended for people interested in contributing to the development of Enso.

Enso is a community-driven open source project which is, and will always be, open and free to use. Join us, help us to build it, and spread the word!


Project Components

Enso consists of several sub projects:

  • Enso Engine: The Enso Engine is the set of tools that implement the Enso language and its associated services. These include the Enso interpreter, a just-in-time compiler and runtime (both powered by GraalVM), and a language server that lets you inspect Enso code as it runs. These components can be used on their own as command line tools.

  • Enso IDE: The Enso IDE is a desktop application that allows working with the visual form of Enso. It consists of an Electron application, a high performance WebGL UI framework, and the searcher which provides contextual search, hints, and documentation for all of Enso's functionality.


License

The Enso Engine is licensed under the Apache 2.0, as specified in the LICENSE file. The Enso IDE is licensed under the AGPL 3.0, as specified in the LICENSE file.

This license set was chosen to provide you with complete freedom to use Enso, create libraries, and release them under any license of your choice, while also allowing us to release commercial products on top of the platform, including Enso Cloud and Enso Enterprise server managers.


Contributing to Enso

Enso is a community-driven open source project which is and will always be open and free to use. We are committed to a fully transparent development process and highly appreciate every contribution. If you love the vision behind Enso and you want to redefine the data processing world, join us and help us track down bugs, implement new features, improve the documentation or spread the word!

If you'd like to help us make this vision a reality, please feel free to join our chat, and take a look at our development and contribution guidelines. The latter describes all the ways in which you can help out with the project, as well as provides detailed instructions for building and hacking on Enso.

If you believe that you have found a security vulnerability in Enso, or that you have a bug report that poses a security risk to Enso's users, please take a look at our security guidelines for a course of action.


Enso's Design

If you would like to gain a better understanding of the principles on which Enso is based, or just delve into the why's and what's of Enso's design, please take a look in the docs/ folder. It is split up into subfolders for each component of Enso. You can view this same documentation in a rendered form at the developer docs website.

This folder also contains a document on Enso's design philosophy, that details the thought process that we use when contemplating changes or additions to the language.

This documentation will evolve as Enso does, both to help newcomers to the project understand the reasoning behind the code, and also to act as a record of the decisions that have been made through Enso's evolution.