Rust for TypeScript Developers vs Web Performance Fundamentals, v2
Same Bayesian formula, same rubric — so the difference in scores reflects the difference in the courses, not the difference in how we evaluated them.
Frontend Masters · Web Development
Rust for TypeScript Developers
Frontend Masters · Web Development
Web Performance Fundamentals, v2
Per-criterion
In 5 hours and 19 minutes the course maps every major Rust primitive to its TypeScript analogue: variables and mutability, number and string types, vectors, tuples, structs, enums with pattern matching, iterators, the borrow checker and ownership rules, traits, and error handling with Option and Result. The pacing is deliberately dense — ThePrimeagen makes no attempt to slow down for readers new to systems concepts. Reviewers consistently describe the content as non-trivial and current, though several note that 5 hours is a primer rather than a complete Rust education: the course ends just as WebAssembly, async Rust, and framework-level topics (Axum, Loco) would begin.
ThePrimeagen — a senior software engineer at Netflix, prolific Twitch streamer, and YouTuber — is the course's defining asset. The official Frontend Masters course page carries a 4.9/5 rating, and the specific praise is consistent: "entertaining, funny and with great examples throughout," "excellent material, fast paced and very content dense," and "not the typical watered down content you find often on online courses." His side-by-side comparison technique — writing the same construct in TypeScript then immediately in Rust — is repeatedly cited as the feature that makes unfamiliar ownership semantics land without feeling abstract. No reviewer in our sample criticises his clarity; the only caveat is that his pace may be a barrier for developers with no prior exposure to typed systems languages.
The course is subscription-only: approximately $39/month or $390/year, unlocking the full Frontend Masters library of 150+ courses. Learners who already subscribe treat this as a bonus title on a platform they already value. For someone who wants only a Rust introduction, the economics are less clear — the subscription buys access to all of Frontend Masters rather than this one course, and the course materials (theprimeagen.github.io/rust-for-typescript-devs/) are publicly accessible without a subscription. Trustpilot rates Frontend Masters at 4 stars overall (38 reviews), with consistent praise for instructor quality and periodic complaints about the absence of standalone purchase options.
The course is exercise-driven rather than project-driven. There is no cohesive build-along application in the style of a full-stack course — instead, learners write increasingly complex Rust snippets in parallel with TypeScript equivalents. This approach is pedagogically sound for learning syntax and memory semantics but produces nothing portfolio- ready. The GitHub repository (github.com/ThePrimeagen/rust-for- typescript-devs, 221 stars, 20 forks) stores lesson files and is publicly available. Multiple reviewers note the need to supplement the course with The Rust Book and Advent of Code exercises to build practical, deployable projects.
Rust's footprint in web tooling has grown substantially: Rspack (23x faster than Webpack), Biome (the successor to Rome), and the SWC JavaScript compiler are all Rust projects that web developers encounter daily. This course provides the ownership, borrowing, and trait semantics that underpin all of them. The TypeScript comparison framing also applies directly to WebAssembly work, where Rust is the dominant compile target. That said, the course stops before Axum, async Rust, and WASM-specific tooling — so a web developer who finishes this course can read Rust code in tooling projects but cannot yet write a Rust web server or compile to WASM without further study.
The course covers the full stack of modern web performance knowledge in approximately six hours — a tight, well-curated curriculum that avoids the padding common in longer Udemy-style recordings. It opens with the psychology of perceived performance (drawing on David Maister's "Psychology of Waiting Lines"), then moves through Core Web Vitals metrics (LCP, CLS, and INP, which replaced FID as an official Google signal in March 2024), measurement APIs, synthetic testing with Lighthouse and WebPageTest, Real User Monitoring with CrUX, and finally concrete optimization tactics for each metric — TTFB, FCP, LCP, layout shift prevention, and interaction latency. The October 2024 update brought the curriculum fully current with the INP transition, so learners are not working with obsolete tooling or metrics. What sets the content apart from generic performance tutorials is its insistence on real user data before optimization. The recurring lesson — "focus on your worst metric, fix the most basic thing first, and confirm with RUM" — is a workflow, not just a collection of tips. The course also links performance work directly to business outcomes: conversion rate, SEO rankings, and user retention statistics are woven into the justification throughout, which gives engineers the language they need to advocate for performance work with non-technical stakeholders. The GitHub workshop repository (113 stars, 87 forks as of mid-2026) demonstrates the exercises have genuine uptake in the developer community.
Todd Gardner is one of the most credentialed practitioners teaching web performance in any format. As co-founder of TrackJS and Request Metrics, he has spent years building commercial RUM tools and working directly with thousands of development teams on performance problems — a background that produces very different teaching than a course built purely from documentation. His Frontend Masters blog articles (published November 2024 on INP and February 2025 on image optimization) extend the same practical, measurement-first methodology into the broader developer community. Student feedback collected from the official course page is unusually consistent in citing his teaching clarity as a differentiator. Anurag Bhandari wrote "Wonderfully planned and executed. Such a heavy topic explained in such simple terms." Pedro Antônio Pereira called it "a masterclass in how to understand web performance." Ryan Davidson, recommending it broadly, wrote: "Great blend of breadth and depth in the performance space. All web engineers — backend or frontend, junior or senior — should be taking this course!" The breadth of that recommendation — extending to backend engineers — reflects how Gardner anchors the course in concepts (HTTP caching, server response times, rendering pipelines) that apply regardless of whether you write CSS or database queries.
The course is included in a Frontend Masters subscription, priced at approximately $39/month or $390/year (annual plans have carried a 17-20% discount in 2025-2026). A seven-day free trial is available. For a subscriber who accesses even two or three courses, the per-course cost is minimal, and the Web Performance Fundamentals course is among the most immediately actionable in the entire library — the techniques taught apply to any existing project without needing to rebuild or refactor an architecture. Deeptiman Mallick's testimonial captures the evergreen value: "This course is like a bookmark to come back to when we're working on performance." Unlike courses that you complete once and set aside, the performance metrics and tools taught here — Lighthouse, WebPageTest, CrUX — are ones practitioners return to on every new project or optimization sprint. The value proposition is strongest for working developers with a real codebase to optimize; the course is less compelling as a purely theoretical exercise for learners with no project to apply it to. There is no standalone purchase option, so non-subscribers must commit to at least one month of the full subscription.
The hands-on component uses a real Node.js + Express e-commerce project — "Developer Stickers Online" — which is deployed to multiple regions and available on a global CDN with HTTP/3 support, making it possible to test real network conditions rather than synthetic localhost scenarios. Students work with actual Lighthouse scores, WebPageTest waterfalls, and CrUX field data rather than simulated metrics, which bridges the gap between tutorial and professional practice. The workshop's focus on a single, realistic project (rather than a series of disconnected toy exercises) is appropriate for the subject: web performance work lives in real measurement data, and the course correctly models that. The project repository's 87 forks suggest learners actively run the exercises rather than just watching. The main limitation is scope: the project is a static storefront, so learners working primarily on Single Page Applications, server-rendered frameworks like Next.js, or complex state-heavy UIs will need to extrapolate some of the tactics. There is no separate project tier with more complex application types.
Web performance is one of the highest-ROI skills a working web developer can acquire in 2024-2026: Core Web Vitals are a confirmed Google Search ranking signal, and the business case studies cited throughout the course (eCommerce and SaaS conversion improvements correlated with performance gains) are drawn from real production data. Gardner's background running RUM tools for thousands of teams means the tactics are not academic — they are the same ones practitioners reach for when a client's LCP score drops. Multiple student reviews specifically noted immediate applicability: Álex Castelo wrote that the course made them realize "how easy it can be to boost a website's performance exponentially," and Yuganshu Mohan distilled the practical lesson as "focus on the worst metric and perform the most basic fixes." The methodological frame — measure with real user data first, then fix, then confirm — transfers directly to professional performance audits. Taran Bains, writing an extended reference post from the course material in August 2025, used it as the foundation for a comprehensive web performance guide, which is a reliable signal that the content holds up as a reference long after the initial watch-through.
Scoring methodology applies identically to every course on the site — see the formula.