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:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 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