Getting Past “Ampersand-Driven Development” in Rust

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

InfluxDB - 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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • hylo

    The Hylo programming language

    See Val for a possible step into that direction.

    https://www.val-lang.dev/

    Or how the Chapel language for HPC is going at it,

    https://chapel-lang.org/

  • InfluxDB

    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.

    InfluxDB logo
  • chapel

    a Productive Parallel Programming Language

    See Val for a possible step into that direction.

    https://www.val-lang.dev/

    Or how the Chapel language for HPC is going at it,

    https://chapel-lang.org/

  • Vale

    Compiler for the Vale programming language - http://vale.dev/ (by ValeLang)

    > I've been wondering lately whether a new spatial approach can yet again simplify matters.

    I've been closely following the development of Vale since I first saw it here. Though their approach is slightly higher-level than Rust and requires (some) runtime safety checks (though to be fair, so does GC).

    https://vale.dev/

    https://verdagon.dev/blog/zero-cost-memory-safety-regions-ov...

    I think it would be tough to change the spatial model in a language as low-level as Rust, because that spatial model is just reflecting how your CPU actually works under the hood. If you try to hide that away, the programmer is going to end up losing some control.

  • csp-cso-chipmunk-

    chipmunk- \x ()

    Very cool. I will take a look. This * was a (just) sketch I did years ago starting from a CSP base (Go). Explicit spaces (or "regions") and defined transition semantics (which compiler and runtime can enforce and guarantee). Single ownership spaces also make distributed GC so much simpler.

    *https://github.com/alphazero/csp-cso-chipmunk-

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • The Vale Programming Language

    1 project | news.ycombinator.com | 27 Nov 2023
  • Two Stories for "What Is CHERI?"

    3 projects | news.ycombinator.com | 13 Oct 2023
  • I've heard that "Rust's borrow checker is necessary to ensure memory safety without a GC" usually also implying it's the only way, but I've done the same without the borrow checker. Am I just clueless/confused?

    2 projects | /r/rust | 13 Sep 2023
  • Single Ownership and Memory Safety without Borrow Checking, Reference Counting, or Garbage Collection

    1 project | /r/ProgrammingLanguages | 16 Jun 2023
  • The Top Programming Languages to Learn in 2024

    7 projects | dev.to | 24 Jun 2024