News for hackers. Stuff that matters.

A comment on Turbolinks: SPA-like Experience without the SPA-framework Hassle. Parent comment

Re:Turbolinks: SPA-like Experience without the SPA-framework... by bruncun on Monday December 11, 2017 @08:40PM (#15902410)
Turbolinks evolved from Pjax (4 yrs old) and is part of Ruby on Rails (11 yrs old). Not only does it respect back/reload out of the box, but it also supports native. Its as mature as it is supported as it is powerful.

It really just works - drop it into a project and you instantly have a SPA. Its far from a framework - its API has less surface area than even React. The above comment couldn't apply less to Turbolinks.

The only true caveat necessary is that it's written in CoffeeScript. :P

[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by the_gastropod on Tuesday December 12, 2017 @09:32AM (#15905779)
Just to be pedantic: pjax is nearly 7 years old. https://github.com/defunkt/jquery-pjax/commit/3efcc3c968c18c...
[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by dcwca on Tuesday December 12, 2017 @07:53AM (#15905221)
The only true caveat is you can’t have multiple dynamic elements per view.
[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by bruncun on Tuesday December 12, 2017 @08:42AM (#15905479)
It allows you to do partial updates, but indeed it doesn’t support view transitions out of the box. :/ That said, the native wrappers offer built-in transitions, and you could probably hack web transitions with some modding and a component library.
[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by jwandborg on Tuesday December 12, 2017 @02:45PM (#15908799)
I like your optimism, but I would like to remind (scare) you:

If you decide to put your effort into customizing the framework, you increase your risk of building

> [...] your poorly cobbled-together "framework" for the next 2, 3, or more years. If anything changes and pages stop working "right", you get to pick up the pieces. Yes, "you", because since your framework is something that you pieced together, there are no "tutorials" nor stack overflow questions nor manuals to refer to.

[ Parent | on HN ]
Re:Turbolinks: SPA-like Experience without the SPA-framework... by owens99 on Tuesday December 12, 2017 @11:02AM (#15906533)
This is easy to do in Rails on your own. Turbolinks is irrelevant to this.
[ Parent | on HN ]