Rune Alternatives

Similar projects and alternatives to rune

Visual Studio Code

2,840 158,095 10.0 TypeScript rune VS Visual Studio Code

Visual Studio Code
racket

188 4,695 9.7 Racket rune VS racket

The Racket repository
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
lem

55 2,059 9.9 Common Lisp rune VS lem

Common Lisp editor/IDE with high expansibility
immer

25 2,420 6.7 C++ rune VS immer

Postmodern immutable and persistent data structures for C++ — value semantics at scale (by arximboldi)
boa

20 4,694 9.8 Rust rune VS boa

Boa is an embeddable and experimental Javascript engine written in Rust. Currently, it has support for some of the language.
dotemacs

12 1 9.7 Emacs Lisp rune VS dotemacs
remacs

19 4,570 1.8 Emacs Lisp rune VS remacs

Rust :heart: Emacs
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
vlfi

9 443 0.0 Emacs Lisp rune VS vlfi

View Large Files in Emacs
gc-arena

4 361 8.2 Rust rune VS gc-arena

Incremental garbage collection from safe Rust
c-rrb

1 157 10.0 C rune VS c-rrb

RRB-tree implemented as a library in C.
Runestone

4 2,569 8.3 Swift rune VS Runestone

📝 Performant plain text editor for iOS with syntax highlighting, line numbers, invisible characters and much more.
ewig

3 517 0.0 C++ rune VS ewig

The eternal text editor — Didactic Ersatz Emacs to show immutable data-structures and the single-atom architecture
mmtk-core

2 25 6.6 Rust rune VS mmtk-core

Memory Management ToolKit (by wenyuzhao)
pimacs

3 25 8.7 Go rune VS pimacs

A partial, experimental implementation of an Elisp interpreter written in Go
vscode-mail

1 28 1.1 TypeScript rune VS vscode-mail

A Mail client embedded in Visual Studio Code.
SaaSHub

www.saashub.com sponsored

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better rune alternative or higher similarity.

Suggest an alternative to rune

rune reviews and mentions

Posts with mentions or reviews of rune. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-16.

The Emacsen family, the design of an Emacs and the importance of Lisp (2023)
6 projects | news.ycombinator.com | 16 Feb 2024

Two projects that may be of interest, related to this topic:
- Rune (https://github.com/CeleritasCelery/rune) - A re-implementation of Emacs but in Rust (like Remacs, but actively developed)
- Pimacs (https://github.com/federicotdn/pimacs) - Same, but using Go (created by me, but developed in a very slow pace)
Text Editor Data Structures
6 projects | news.ycombinator.com | 13 Jun 2023

[2] https://github.com/CeleritasCelery/rune/issues/17#issuecomme...
rune: Rust VM for Emacs
1 project | /r/planetemacs | 13 Feb 2023
Design of Emacs in Rust
1 project | /r/emacs | 19 Jan 2023

I second this ! I had trouble finding the github link, but here is is https://github.com/CeleritasCelery/rune
Rune: An experimental Emacs Lisp interpreter written in Rust
1 project | news.ycombinator.com | 17 Jan 2023
Implementing a safe garbage collector in Rust
4 projects | news.ycombinator.com | 29 Apr 2022

> How is anything rooted here? The lifetime changed from 'arena to 'root but I don't see a root being created.
In this example, the Vec has been rooted previously. So pushing an object into the Vec will make it "transitively" rooted (accessible from the root). You would root a struct with the root_struct![1] macro, which works very similar to the root! macro shown in the post.
However you made you realize one error; The rooted `Vec` in the example you pointed is a by value type, but in the implementation you can only get references to rooted structs, so that example needs to be updated.
> But later we see roots not obeying a LIFO order, under "Preventing escapes" where roots are dynamically created and destroyed in an arbitrary order.
Objects are just a copyable wrapper around a pointer, so they are not the part that has the LIFO semantics. inside the root! macro[2] there is a `StackRoot` type that is the actual "root". The object just borrows from that so that is has a 'root lifetime and is valid post gc. The actual root struct is not exposed outside of the macro.
I hope this makes the distinction between "roots" and "objects" clearer. Objects are just pointers to heap data. When we root an object we store the data it points to on the root stack and create a new `StackRoot`. Then we say this object is rooted. But the struct that "does the rooting" is inside the macro and not exposed. Rooting a struct works similarly.
[1] https://github.com/CeleritasCelery/rune/blob/5a616efbed763b9...

2 projects | /r/rust | 12 Apr 2022
I came to the conclusion that I wont learn Elisp...unless...
3 projects | /r/emacs | 24 Apr 2022

Hack on Rune
A note from our sponsor - SaaSHub
www.saashub.com | 28 Apr 2024

SaaSHub helps you find the best software and product alternatives Learn more →