| starlight | aulang | |
|---|---|---|
| 7 | 5 | |
| 500 | 37 | |
| 1.8% | - | |
| 1.8 | 0.0 | |
| over 2 years ago | about 3 years ago | |
| Rust | C | |
| Mozilla Public License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
starlight
-
Really it have to be some kind of virus that spreads sneakly
I have great news
-
gc-shadowstack: Implementation of shadow stack algorithm to track GC rooted objects.
Hello to all! This crate implements Shadow Stack algorithm which allows to track GC objects on stack with almost zero overhead! This algorithm is used inside Restricted Python and seems to work very well. This crate soon will replace DIY shadow stack implementation in starlight(JS engine in Rust) too.
-
March 2021 monthly "What are you working on?" thread
Working on startup snapshots in starlight. I already have very basic implementation which allows to initialize runtime in just 17 microseconds from snapshot vs 23 microseconds without snapshot when every builtin is created from scratch. Future work is aimed mostly on making deserialization faster
-
Reference counting GC vs tracing GC and JITs
Hi to all! I'm working on starlight (JS engine in Rust) and I can't choose memory management technique: Right now I have conservative on stack precise on heap GC which somehow manages to work but still has segfaults and I'm also working on rcgc feature which will use RC as GC algorithm but my main question: is it worth using RC over tracing cycle and how hard it will be to implement JIT when RC is used? I've never seen any runtimes that use RC and implement JIT.
-
Starlight: JS engine focused on performance in Rust.
There's test262_passed file in repo, you can take a look at what tests pass :)
aulang
-
April 2021 monthly "What are you working on?" thread
Apart from the language I also built a simple website for Aument, a JSON parser in Aument and incomplete bindings for libuv.
- Aument: a dynamically-typed scripting language written in C and compiles to C
-
March 2021 monthly "What are you working on?" thread
Since last month, I've added a lot of changes to my programming language, now named Aument, namely classes, method dispatching and the module system.
-
February 2021 monthly "What are you working on?" thread
I've been lurking here for a while, but never actually created a Reddit account. So, as a first post, hi! This month I'm working on aulang, it aims to be a portable and embeddable dynamic scripting language like Python or Lua. It is prepreprepreprepre alpha so don't expect it to be that amazing, but it has the bare minimum features and the language can even be compiled to native code through C (currently only works on Linux).
What are some alternatives?
boa - Boa is an embeddable and experimental Javascript engine written in Rust. Currently, it has support for some of the language.
kuroko - Dialect of Python with explicit variable declaration and block scoping, with a lightweight and easy-to-embed bytecode compiler and interpreter.
Matrix - Easy-to-use Scientific Computing library in/for C++ available for Linux and Windows.
star - An experimental programming language that's made to be powerful, productive, and predictable
bluebird - A work-in-progess programming language modeled after Ada and C++
xvm - Ecstasy and XVM
fastcode - A unique blend of C, Java, and Python tailored for those who desire a simple yet powerful programming language.
lisp - A lisp JIT compiler and interpreter built with cranelift.
pkg-tasks - Aument package for asynchronous I/O
firefly-boot - Bootstrap compiler for Firefly
yasl - Bytecode Interpreter for Yet Another Scripting Language (YASL).