#scripting-language #expression-language #steel #script #applications #statically-typed

bin+lib steel-lang

Steel (Statically-Typed Embedded Expression Language) is a scripting language that can be embedded in other applications

1 unstable release

0.1.0 Apr 1, 2023

#14 in #steel

23 downloads per month
Used in steel-cli

Apache-2.0

12KB

Steel

Steel (Statically-Typed Embedded Expression Language) is a scripting language that can be embedded in other applications.

Steel is under construction and not ready for use

It is designed to be:

  • Easy and secure to use from other languages.
  • Simple to use, but with the safety of strict static types.
  • Feature-complete, no need to update runtimes to run new scripts.

Goals

The goal is to provide a simple language that end users can write small or medium scripts in, to run as part of a larger application. It is stable, so no mismatch between script and runtime versions, and no constant updates.

The simplicity, safety and the ease of use from other languages make Steel convenient as a scripting langauge. For example to provide modding capabilities in a video game, or to allow users to provide custom calculations in a financial or scientific model.

These are nice use cases, but there are many alternatives, why pick Steel?

You may choose Steel over a lot of other embeddable scripting languages if you prefer strict static typing, to tell users about their mistakes when they are writing the script, rather than when running. It also allows ahead-of-time compiling, in addition to interpreted mode.

But where Steel really shines is when scripts have to run embedded in more than one language. Steel tries hard to be embeddable in many languages by its design choices, most importantly by providing a stable langauge, so that any Steel script runs in any embedding environment.

An example of such a multi-language case are user scripts that can run in the backend, but also in a browser, or on a phone app. Support offline mode and save on hardware costs.

Another example is for scripts in a cross-system tool, like a message broker or message encoding that provides scripting. Steel was originally created for such a tool, Apivolve.

Non-goals

The goal is not to provide all the latest tricks, scale to thousands of lines, or write independent services. There is no file or network access unless the host application exposes it.

Dependencies

~7–16MB
~189K SLoC