Xvm Alternatives
Similar projects and alternatives to xvm
-
kuroko
Dialect of Python with explicit variable declaration and block scoping, with a lightweight and easy-to-embed bytecode compiler and interpreter.
-
-
SonarLint
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.
-
-
-
-
grammars-v4
Grammars written for ANTLR v4; expectation that the grammars are free of actions.
-
OPS
OPS - Build and Run Open Source Unikernels. Quickly and easily build and deploy open source unikernels in tens of seconds. Deploy in any language to any cloud.
-
The-Spiral-Language
Functional language with intensional polymorphism and first-class staging.
-
-
star
An experimental programming language that's made to be powerful, productive, and predictable (by ALANVF)
-
-
passerine
A small extensible programming language designed for concise expression with little code.
-
-
-
-
-
-
TypeScript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
-
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better xvm alternative or higher similarity.
Reviews and mentions
Posts with mentions or reviews of xvm.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-10.
-
Would it be good to add inconsistency to add a small string variant in the value payload?
We plan to use the same trick in the XVM (Ecstasy virtual machine) for its fat pointers. Each reference in Ecstasy has two conceptual pieces of information: A type and an identity. If the compiler knows that the type is fixed and the reference doesn't escape, then it can generate code knowing that type and doesn't need to encode it into the reference (assumed to be 8 bytes). Similarly, if the identity fits into the 8 bytes, then the value doesn't need to be "boxed". In our original design, for example, 8-byte ints (i.e. instances of the Int64 class) that are known to be of the type Int64 could always be stored in the fat pointer itself. We've come a long way in the design since then, but the same basic concept still holds: Don't allocate objects when the object can fit in the thing that you would have used to point to the object.
-
Are First-Class Properties Still A Good Idea?
In Ecstasy, we use properties, as described on this blog. There is still an underlying struct, which is exposed -- but it is exposed as an object, whose properties represent the fields of the struct.
-
January 2022 monthly "What are you working on?" thread
Lots of activity on Ecstasy:
-
December 2021 monthly "What are you working on?" thread
Ecstasy update:
-
How does one implement closures.
To give you some idea of how difficult it is, the Ecstasy compiler uses three distinct passes over a closure (each of which is "morally equivalent" to a full module compilation).
-
How about considering threads as allocators? (aka: Maybe this helps with simplifying multi-threading and stuff?)
When a message is received by a service, the service creates a new fiber to handle the message. Only one fiber can run at a time within a service, although when a fiber blocks waiting on another service, that allows another fiber to execute, if the service is marked as concurrent. You can read a bit more about that topic here.
-
Disambiguating x.f()
This is a complicated potential ambiguity, if you're not careful. And in a left-associative OO language like C++ (i.e. target-dot-method), it gets even more complicated, because the x in x.f() can be an object reference. For what it's worth, we decided to keep this approach in Ecstasy, but it definitely did put a heavy burden on the compiler; I'd say a full half of the entire complexity of the compiler is spent on the NameExpression and InvocationExpression, to answer questions like the one posed here. Ecstasy added binding (currying) and partial binding as well, using the same syntax, so disambiguation is pretty complicated.
-
November 2021 monthly "What are you working on?" thread
Current Ecstasy projects:
-
Initially-nullable types
(Some more details here.)
-
How to keep file information when tokenizing?
The Source is a stream of characters associated with a file, and tracks current line number, offset, and so on.
-
Breaking out of all loops without using GOTO
In Ecstasy, we used the label approach, and made the Label into a compile-time object that exposes runtime attributes of the labeled statement. Here are two different examples of how this can be used:
-
Languages with integrated dependency injection
Ecstasy requires DI for all resources other than CPU and RAM (storage, network, console, GUI, whatever), and makes DI available intrinsically for any other purpose that a developer finds useful.
-
The problem with untyped literals
Instead, we have explicit types for each literal. For example, the value 0 has a type: IntLiteral. In theory, instances of that type hold a String. In reality, the primary reason for the type is to allow the compiler to reason about the type, without nailing it down as a some number and arrangement of bits.
-
October 2021 monthly "What are you working on?" thread
Ecstasy: Only a few things hot at the moment:
-
Green Threads vs Async/Await, ergonomics-wise, toward thread-safety
In our R&D for the XVM (Ecstasy), we knew that one enormous global mutable space (a la C++, Java, C#, Python, etc.) was a bad idea, because of the specific goals that we had in mind. Based on some advice and a request from Rich Hickey, we initially tried implementing STM (Software Transactional Memory) in the XVM. We invested about a year in that design, before completely giving up (and shortly before Intel gave up on HTM; they disabled it by microcode in 2018, and removing support for it in CPUs starting in 2020). We spent a few months trying to recover from our failure, before finally settling on a hierarchical execution+memory model (lightweight software containers, easily supporting thousands inside a single running process space). To achieve concurrency and memory safety, we rely on a combination of services (with a dynamically configurable re-entrancy policy) and fibers (which are, conceptually, short-lived green threads).
Stats
Basic xvm repo stats
55
95
9.8
3 days ago
xtclang/xvm is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
Popular Comparisons
Less time debugging, more time building
Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
scoutapm.com
Are you hiring? Post a new remote job listing for free.