2021-02-22
2646
#rust#typescript
Ukpai Ugochi
34719
Feb 22, 2021 â‹… 9 min read

Switching from Rust to TypeScript (and vice versa)

Ukpai Ugochi I'm a full-stack JavaScript developer on the MEVN stack. I love to share knowledge about my transition from marine engineering to software development to encourage people who love software development and don't know where to begin. I also contribute to OSS in my free time.

Recent posts:

Build Chatbots in Langchain and RAG LogRocket Article

How to build smarter frontend chatbots with RAG and LangChain.js

Build smarter frontend chatbots with RAG and LangChain.js. Learn how to add context, improve accuracy, and cut costs with a practical tutorial.

Nelson Michael
Sep 18, 2025 â‹… 8 min read
alexandra spalato ai hallucination quote

How to stop your AI agents from hallucinating: A guide to n8n’s Eval Node

Walk through a practical example of n8n’s Eval feature, which helps developers reduce hallucinations and increase reliability of AI products.

Alexandra Spalato
Sep 17, 2025 â‹… 6 min read

Secure your AI-generated projects with these security practices

Secure AI-generated code with proactive prompting, automated guardrails, and contextual auditing. A practical playbook for safe AI-assisted development.

Ikeh Akinyemi
Sep 16, 2025 â‹… 5 min read

Let’s kill vibe coding and bring back prompt engineering

Explore the vibe coding hype cycle, the risks of casual “vibe-driven” development, and why prompt engineering deserves a comeback as a critical skill for building better, more reliable AI applications.

Oscar Jite-Orimiono
Sep 16, 2025 â‹… 11 min read
View all posts

3 Replies to "Switching from Rust to TypeScript (and vice versa)"

  1. “You don’t need to install any runtime environment to execute TypeScript code.” That’s not really true… you first need a TypeScript to Javascript, compiler, and then you need a Javacript interpreter runtime (embedded in a browser or in nodejs) to run your program. Granted, for many people they already have a runtime installed on their system, but for some applications this could be a deal-breaker.

  2. Good read for primer. Thanks

    “Rust has the const keyword. However, you can only set the variable value at runtime alone, not at compile time.

    fn another_function(x: i32) -> i32 {
    return x + 1;
    }

    fn main() {
    // RUN-TIME ASSIGNMENT, if you replace const with let, there’s no compile error
    const z = another_function(5);
    println!(“The value of z is: {}”, z); // 6
    }
    Because let can be set at compile time and const can’t, the code throws an error at compile time. Although Rust variables are immutable by default, you can redefine or shadow variables of type let:

    I’m pretty sure you meant run-time and compile-time the other way around for this section (the typo is in the text, not in the code).

Leave a Reply