2023-07-06
2337
#node#rust
Anshul Goyal
17596
Jul 6, 2023 ⋅ 8 min read

Improving Node.js performance using Rust

Anshul Goyal I love to code and use new technologies.

Recent posts:

Why Go wasn’t the right choice for the TypeScript compiler

Why Go wasn’t the right choice for the TypeScript compiler

The switch to Go may be a pragmatic move in the short term, but it risks alienating the very developers who built the tools that made TypeScript indispensable in the first place.

Muhammed Ali
May 8, 2025 ⋅ 4 min read
how and when to use type casting in TypeScript

How and when to use type casting in TypeScript

Discover the basics and advanced use cases of type casting, how and why to use it to fix type mismatches, and gain some clarity on casting vs. assertion.

Paul Akinyemi
May 8, 2025 ⋅ 14 min read

How to format dates in JavaScript: Methods, libraries, and best practices

JavaScript date handling can be tough. Here are some native Date API tools and specialized libraries to tackle them with.

Nelson Michael
May 8, 2025 ⋅ 8 min read
tailwind typography

How to use the Tailwind Typography plugin

Walk you through how to set up and use the Tailwind Typography plugin, also known as the @tailwindcss/typography or the prose plugin.

David Omotayo
May 7, 2025 ⋅ 7 min read
View all posts

8 Replies to "Improving Node.js performance using Rust"

  1. > Rust can mimic the behavior of a C library.
    Like C++ can’t? 🙂
    What `extern “C”` is for in C++ then? 😉

  2. Rust is somehow flew above my head. However node.js is something that I use everyday in my projects. It help me doing a lot of things easily. For example, I use gulp for automating tasks.

  3. What is meant by “You can use WebAssembly to create a node_module, but all Node.js functionality is not available”? Can’t you create a wasm and bind to any part of the Node.js API with wasm-bindgen?

  4. Can we please stop writting article with AI. I could tell with the first sentance and then ran it through an AI detector, and guess what AI generated.

    1. Hi Tom, thanks for your feedback. The first sentence of this article is the same as when this article was first published in 2020, before ChatGPT’s first release. It’s possible a different AI content generator was used, but we’ve found that certain writing styles tend to get marked as AI-generated when they’re not, which is the more likely explanation here. While things can certainly slip through the cracks, our team rigorously checks every draft and update we receive for both plagiarism and AI usage, and we have worked hard to ensure that the authors we work with write original content with integrity using their personal experience as developers. Still, we recognize it can be frustrating to read an article that sounds like AI, and we appreciate your reaching out to let us know your thoughts!

Leave a Reply