2020-12-24
1351
#ruby on rails
Diogo Souza
30738
Dec 24, 2020 â‹… 4 min read

Turbolinks for faster web navigation

Diogo Souza Brazilian dev. Creator of altaluna.com.br

Recent posts:

Frontend Devs Aren't Lazy, They're Burnt Out

Frontend developers are burned out, not lazy

Shipping modern frontends is harder than it looks. Learn the hidden taxes of today’s stacks and practical ways to reduce churn and avoid burnout.

Shalitha Suranga
Sep 15, 2025 â‹… 4 min read

Can native web APIs replace custom components in 2025?

Learn how native web APIs such as dialog, details, and Popover bring accessibility, performance, and simplicity without custom components.

Daniel Schwarz
Sep 12, 2025 â‹… 9 min read
too many tools: How to manage frontend tool overload

Too many tools: How to manage frontend tool overload

Read about how the growth of frontend development created so many tools, and how to manage tool overload within your team.

Shalitha Suranga
Sep 11, 2025 â‹… 12 min read
shruti kapoor the modern ai stack

What you actually need to build and ship AI-powered apps in 2025

Discover what you actually need to build and ship AI-powered apps in 2025, with tips for which tools to choose and how to implement them.

Shruti Kapoor
Sep 10, 2025 â‹… 10 min read
View all posts

2 Replies to "Turbolinks for faster web navigation"

  1. “Turbolinks improves performance of SPAs (single-page applications) by substituting the common full-page loads for partial loads.”

    That’s not true.

    Turbolinks has nothing to do with SPAs (applications made with React, Angular, etc.)

    SPAs don’t do “common full-page loads”.

    Turbolinks is about making multi-page applications render faster.

  2. Hey Random Dev, thanks for reaching out.

    You’re right, it was my mistake. The original idea of the post was to be about Turbolinks usage along with SPAs, but then it shifted.

    The post is updated now.

    Thanks for this! 🙂

Leave a Reply