Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jgaskins/turbolinks-vs-clearwater
Performance comparison of Turbolinks and a virtual DOM
https://github.com/jgaskins/turbolinks-vs-clearwater
Last synced: 22 days ago
JSON representation
Performance comparison of Turbolinks and a virtual DOM
- Host: GitHub
- URL: https://github.com/jgaskins/turbolinks-vs-clearwater
- Owner: jgaskins
- Created: 2016-02-29T01:05:40.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2016-03-09T19:41:19.000Z (almost 9 years ago)
- Last Synced: 2024-12-09T10:55:46.610Z (25 days ago)
- Language: Ruby
- Size: 25.4 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Turbolinks vs Clearwater
[Check the demo](https://turbolinks-vs-clearwater.herokuapp.com)
This project was created to confirm or deny claims that Turbolinks is faster than a virtual DOM and therefore better to use for old/low-performance clients. Turns out, Turbolinks performance is an order of magnitude worse than Clearwater on a realistic number of DOM elements when only a small number of those change.
Granted, a 4k-article blog is not a realistic app, but it does represent a realistic number of DOM changes between two renders.