In short
ShardScript 0.5 looks less like an attempt at yet another general-purpose language and more like a kit for embedding scripts into applications. I look at what is already there for integration and why an LSP prototype matters more than loud promises.
The main value of ShardScript 0.5 is not the C-like syntax itself but the attempt to simplify embedding scripts into finished applications. For a developer that means less of a gap between the main C++ code and high-level scripts, though not a ready replacement for existing languages.
The release includes an interpreter, an updated standard library (STL) and officially supported third-party modules. That matters more than merely publishing a grammar: the language gets a basic toolkit you can start integrating with, rather than assembling an environment by hand.
The prototype LSP server for Windows stands out separately. Editor support here is still at the prototype stage, but the very appearance of LSP shows the project's practical focus: the language is being made convenient not only for execution but for everyday work with code.
That said, the release is worth taking without undue enthusiasm. ShardScript is written in C++ and distributed under Apache 2.0, with binary builds available for Windows and Linux, yet the LSP is still a prototype and Windows-only. The source also carries no data on performance, community size or compatibility with particular applications — so the maturity of the ecosystem cannot be judged from this release.
If you had to embed a scripting language into a C++ application today, would you choose a small specialised project like ShardScript or a proven ecosystem with many ready integrations? Source: OpenNews.opennet.ru: General news feed