embedded-scripting-languages VS kutil

Hopefully the linked README provides a general overview (I know I need to write some more documentation!), but Steel is an implementation of the scheme programming language (not entirely compliant yet, but aiming for R5RS and R7RS compliance). It can be used as a standalone language via the interpreter/repl (like Python or Racket), or it can be embedded inside applications, like Lua. There are hundreds (thousands, probably) of embeddable languages, each with their own flavor - see a list compiled here for example https://github.com/dbohdan/embedded-scripting-languages

Use cases are generally for either configuration, scripting, or plugins - so scripting in games, or adding extensions to your text editor without having to use FFI or RPC + serializing a bunch of data. The advantage it has over using dynamic libraries (in general) is it runs in the same process, and can access the internal data structures directly without a lot of ceremony involved. The downside is typically is not as fast as native code unless a JIT is involved.

Javascript is an example of an embedded scripting, where the browser is the host application.

> There is a huge opportunity, IMO, for more players here.

There are quite a few embeddable scripting languages [1]. I think these days it's less common to embed a language mostly because there are good high-level languages that applications can be predominantly written in.

[1] https://github.com/dbohdan/embedded-scripting-languages

I'm not a huge fan of Lua but I think it is at least way more popular and better on every measure than TCL. There are plenty of other better less well-known options too: Rhai, Wren, AngelScript, Starlark (for some use cases), etc. There's a good list here.

or perhaps use one of this list (depending on who's writing the configuration): https://github.com/dbohdan/embedded-scripting-languages

https://github.com/dbohdan/embedded-scripting-languages (coincidentally, from a user whose name I recognize from the Tcl wiki)

For reference, here's my implementation. Note that my wrapper supports both structured and traditional logging APIs.

For JS in Go use goja, which offers excellent integration with Go. Also I maintain an extension that adds Common-JS compatibility to it.

I think your instinct is right. For all my projects I use these wrappers. If you have any feedback or contributions they would be much appreciated. I know it's a losing battle, but there's no choice but to fight. Semper fi.

This is mostly what I did with my kutil logging library (sorry, no good documentation on how to use it yet). So I can use the same API in all my code and then pick various backends per project in order to better unify the log. For example, in Kubernetes I can use klog as the backend. I also wrote my own "simple" backend that does everything that I personally want. I'm sure there are other similar libraries out there.

I really like the idea of an Extended JSON, so I created my own version called "CJSON". The code is pretty straightforward.