Skip to content

Comparison to TurboLinks #127

Open
Open

Description

@jwickens

Really interesting project!

It seems really similar to the TurboLinks project (https://github.com/turbolinks/turbolinks)

I think your comparison to Ajaxify holds true "What makes React-Magic different is that it only updates the DOM nodes that have changed, whereas Ajaxify and similar solutions just blow away the whole document.body on every page load" except TurboLinks also caches previous pages.

One of the big problems with using TurboLinks is that scripts that rely on on document ready hooks are not executed as expected. I would assume this would be the same case.

Also TurboLinks has a directive for marking a DOM element as "permanent" which means its preserved across page loads. This is obviously the default in react magic. I wonder if there is a case for a similar markup in react magic but to do the opposite - force tear down of a component so that state can be reset.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions