rusty-TONC VS rust

Compare rusty-TONC vs rust and see what are their differences.


Having fun on the GBA, and porting TONC's examples. (by tbelaire)


Empowering everyone to build reliable and efficient software. (by rust-lang)
Our great sponsors
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • Onboard AI - Learn any GitHub repo in 59 seconds
  • SaaSHub - Software Alternatives and Reviews
rusty-TONC rust
1 2609
43 87,671
- 1.3%
10.0 10.0
about 7 years ago 4 days ago
C Rust
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.


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


Posts with mentions or reviews of rust. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-08.
  • Quants use Rust; Devs use C++ - Hey, it's a compromise!
    2 projects | /r/cpp | 8 Dec 2023
    If you are comparing hoops that library authors need to jump through in both languages, you can easily make the real-world comparison in the other direction, by comparing Rust's Option with C++'s std::optional (an exercise left for the reader): Rust std: libcxx:
  • Food for thought: Simple Rust a'la Simple Haskell?
    2 projects | /r/rust | 6 Dec 2023
    finishing const generics, so that you can use them in const expressions in a natural way (including in associated constants)
  • Behind the Scenes of Rust String Formatting: format_args!()
    2 projects | /r/rust | 6 Dec 2023
    I haven't considered that option yet. If you think it is worth exploring, it might be good to leave that idea in a comment on the tracking issue:
    2 projects | /r/rust | 6 Dec 2023
    Typo: The "shipped as part of Rust 1.71" link should probably point to
  • Common Rust Lifetime Misconceptions
    4 projects | | 4 Dec 2023
    Here is the original GitHub issue on the question:

    Intuitively, the bottom lifetime should the one that is uninhabited, which would be a lifetime with no extent rather than 'static.

    4 projects | | 4 Dec 2023
  • Is Ada safer than Rust?
    2 projects | | 2 Dec 2023
    Easy to compare:

    Search the gnat bug tracker for stack overflow: 14 bugs

    Rust: 243 (plus 830 closed)

    Choose by yourself which seems safer

  • Recap of Werner Vogels' Keynote at re:Invent 2023
    3 projects | | 2 Dec 2023
    He delved into the evolution of AWS Lambda's pricing strategy, transitioning from T2 instances to the innovative Firecracker microVMs for superior resource optimization. Vogels also advocated for exploring energy-efficient programming languages like Rust, showcasing AWS's adoption in Firecracker and a substantial segment of their S3 service, aiming for more efficient and cost-effective solutions. This blog is really helpful about Firecracker – Lightweight Virtualization for Serverless Computing
  • Advent of Code 2023 - DAY 1
    3 projects | | 1 Dec 2023
    It's Christmas time and time for Advent of Code 2023 edition. Starting from today I will try to solve puzzles in Rust and publish a post a day in which I tell my solution. My goal is not to climb the leaderboard but to use the problems to practice writing Rust code and improve my language knowledge. Copilot yes or Copilot not? It's for learning so Copilot definitely not. The solutions will be available at the following git repository, as I don't have much time to write a template from scratch, I will use the starter template available here.
  • Rust std:fs slower than Python
    7 projects | | 29 Nov 2023
    > I know it’s easy to change but the arguments for using glibc’s allocator are less clear to me:

    You can find them at the original motivation for removing jemalloc, 7 years ago:

    Also it's not "glibc's allocator", it's the system allocator. If you're unhappy with glibc's, get that replaced.

    > 1. Reliability - how is an alternate allocator less reliable?

    Jemalloc had to be disabled on various platforms and architectures, there is no reason to think mimalloc or tcmalloc are any different.

    The system allocator, while shit, is always there and functional, the project does not have to curate its availability across platforms.

    > 2. Compatibility - again sounds like a FUD argument. How is compatibility reduced by swapping out the allocator?

    It makes interactions with anything which does use the system allocator worse, and almost certainly fails to interact correctly with some of the more specialised system facilities (e.g. malloc.conf) or tooling (in rust, jemalloc as shipped did not work with valgrind).

    > Also, most people aren’t writing hello world applications

    Most people aren't writing applications bound on allocation throughput either

    > so the default should probably be for a good allocator.

    Probably not, no.

    > I’d also note that having a dependency of the std runtime on glibc in the first place likely bloats your binary more than the specific allocator selected.

    That makes no sense whatsoever. The libc is the system's and dynamically linked. And changing allocator does not magically unlink it.

    > 4. Maintenance burden - I don’t really buy this argument.

    It doesn't matter that you don't buy it. Having to ship, resync, debug, and curate (cf (1)) an allocator is a maintenance burden. With a system allocator, all the project does is ensure it calls the system allocators correctly, the rest is out of its purview.

What are some alternatives?

When comparing rusty-TONC and rust you can also consider the following projects:

carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)

zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.

Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).

Odin - Odin Programming Language

Elixir - Elixir is a dynamic, functional language for building scalable and maintainable applications

Rustup - The Rust toolchain installer

rust-analyzer - A Rust compiler front-end for IDEs [Moved to:]

go - The Go programming language

mimalloc - mimalloc is a compact general purpose allocator with excellent performance.

scala - Scala 2 compiler and standard library. Bugs at; Scala 3 at

spaCy - 💫 Industrial-strength Natural Language Processing (NLP) in Python