Go & Vanilla JS: Fullstack Without Frameworks vs Front-End Engineer Career Path

Ten hours eleven minutes covering the full stack end-to-end: Go project setup and architecture, a JSON REST API with structured handlers, Postgres integration via a repository interface pattern, Vanilla JS web components, a client-side SPA router built from scratch, View Transitions API, search/filter/sort, and a complete JWT authentication flow covering registration, login, server-side middleware, and client-side route guards. Published May 27, 2025 — compatible with Go 1.22+ and modern browser APIs. The course deliberately avoids backend frameworks (no Gin, Echo, or Fiber), relying on Go's standard library, keeping outcomes transferable to any Go project.

Maximiliano Firtman is a prolific Frontend Masters instructor with prior courses on Mobile Web Development, Progressive Web Apps, and JavaScript Performance. The course holds a 4.9/5 star platform rating — among the highest for full-stack courses on Frontend Masters. Students consistently cite his habit of explaining architectural decisions and trade-offs rather than simply typing out code, and his willingness to debug real issues live during recording rather than presenting pre-cleaned output. Reviewers describe him as a "true master" whose teaching style emphasises the reasoning behind every decision.

Access requires a Frontend Masters subscription (~$39/month or ~$390/year for individuals) rather than a one-time purchase. Strong value for learners using the broader catalog — Frontend Masters covers JavaScript, TypeScript, React, CSS, Node.js, and dozens of related tracks under one subscription. Weaker for those taking only this course. No free tier beyond a short preview. The subscription cost is the dominant frustration across otherwise positive reviews, consistent with complaints across the entire Frontend Masters catalog.

The course builds a complete movie catalogue application end-to-end: a Go REST API with structured JSON handlers, a Postgres layer using a repository interface pattern, AIR-powered live-reload during development, full JWT authentication (registration, login, server-side middleware, golang-jwt token generation), and a Vanilla JS SPA with a hand-rolled client-side router, View Transitions, web components for every UI element, a search/filter/sort feature, and authenticated user pages (My Account, Favorites, Watchlist). Full authentication including client-side route guards distinguishes this course from most full-stack offerings that leave auth as an exercise or third-party library call.

The deliberate no-framework approach teaches patterns that transfer to any technology choice: the router is built from scratch, web components replace UI libraries, state management uses the Proxy pattern. Students report that this improves their ability to evaluate frameworks critically, because they understand what each framework is solving. Go's standard library — net/http, database/sql, log/slog — maps directly to production Go codebases. The Postgres repository pattern, AIR for live-reload, and Postman-tested API routes represent practices encountered in real engineering teams.

Curriculum covers HTML, CSS, vanilla JS, React, Redux and a capstone project across roughly 100 hours. Well-scoped for beginners but several long-time learners report content drift in framework modules and a pacing that prioritises bite-sized exercises over deep explanation.

No single instructor — the path is curriculum-by-committee, mixing written lessons with short videos. Praised for clarity in the early HTML/CSS units; later JS and React modules draw recurring criticism that they "feel like following instructions" rather than teaching.

Career Path requires Pro at $24/mo (~$240/year). Head-to-head with freeCodeCamp (free, similar scope), the value math is the corpus's most-debated point. Justifiable mainly for the structured path plus capstone, not the lessons alone.

The Pro-only capstone is the single most-cited reason to recommend the Career Path over the free modules. Mid-path mini-projects are praised as friction-removing but criticised as too guided to count as independent portfolio work.

Strong on language syntax and React 101 patterns; weaker on local dev environment, git workflow, deployment and modern build tooling. Several commenters describe the same "I can write a for loop, now what?" gap after finishing the early modules — a sandbox-first design trade-off.