Hybrid visual and textual functional programming.
Go to file
2021-02-26 10:43:18 +00:00
.cargo Prepare the repo for working on rust code (#841) 2020-06-16 17:18:11 +01:00
.github Implement the first part of the database library (#1475) 2021-02-25 13:48:18 +00:00
distribution Implement the first part of the database library (#1475) 2021-02-25 13:48:18 +00:00
docs Enable the docker pipeline for releases (#1500) 2021-02-23 14:12:24 +00:00
engine fix: lambda locations (#1522) 2021-02-26 12:59:21 +03:00
lib Band-aid the "template pattern segment" error (#1509) 2021-02-25 09:46:03 +00:00
project Implement the first part of the database library (#1475) 2021-02-25 13:48:18 +00:00
std-bits/src/main/java/org/enso/base Implement the first part of the database library (#1475) 2021-02-25 13:48:18 +00:00
table/src/main/java/org/enso/table Table: Fix bool column sorting (#1505) 2021-02-24 17:36:24 +01:00
test Implement the first part of the database library (#1475) 2021-02-25 13:48:18 +00:00
tools Implement the first part of the database library (#1475) 2021-02-25 13:48:18 +00:00
.gitignore Add API for dataflow errors (#1422) 2021-01-25 14:41:20 +00:00
.jvmopts Java 11 Migration (#928) 2020-07-01 13:21:13 +02:00
.prettierignore Project Manager Native Image (#1318) 2020-12-09 14:58:11 +01:00
.prettierrc.json Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
.scalafmt.conf Bump SBT and Scalafmt (#1203) 2020-10-22 16:12:28 +02:00
build.sbt Bump the snapshot version 2021-02-26 10:43:18 +00:00
Cargo.lock Add API for dataflow errors (#1422) 2021-01-25 14:41:20 +00:00
Cargo.toml Preparation for more parser work (#1363) 2020-12-18 14:25:30 +00:00
LICENSE Set up the repository (#1) 2019-06-11 17:07:54 +01:00
package.json Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
README.md Make some minor updates to the readme (#1449) 2021-02-15 08:57:15 +00:00
RELEASES.md Prepare for the 0.2.5 release (#1524) 2021-02-26 10:42:26 +00:00


Enso Visual Environmment

Enso Language


Chat Actions Status Actions Status License License


All your data and analytics. Unified. Interactive.

Enso is a general-purpose programming language and environment for interactive data processing. It is a tool that spans the entire stack, going from high-level visualisation and communication to the nitty-gritty of backend services, all in a single language.

      Connect to all the tools you're already using
      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.
      Cutting-edge visualization engine
      Enso is equipped with a highly-tailored WebGL visualization engine capable of displaying even millions of data points 60 frames per second in a web browser.
      Polyglot
      Enso allows you to use any Java library in your code. Soon, it will also allow you to copy-paste code from Python, JavaScript, Ruby, and R with close-to-zero performance overhead at runtime.
      High performance
      Enso graphs and code can run up to 100x faster than the analoguous Python code.
      Results you can trust
      Enso incorporates many recent innovations in data processing and programming language design to allow you to work quickly 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 a rich set of primitive types.
      Runs everywhere
      Enso is available on MacOS, Windows, and 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 of phone access to your data.

Getting Started

An example Enso graph



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 a just-in-time compiler, runtime, and language server. These components can be used on their own as command line tools.

  • Enso IDE. The Enso IDE is the desktop application that allows working with the visual form Enso. It consists of an Electron application, a high performance WebGL UI framework, and the Searcher which provides contextual search, hints, and documentation for Enso 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 choosen to both provide you with a 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, but also to act as a record of the decisions that have been made through Enso's evolution.