When comparing Live.js vs Reloadr, the Slant community recommends Live.js for most people. In the question“What are the best cross-browser live-update / synchronization tools?” Live.js is ranked 6th while Reloadr is ranked 8th. The most important reason people chose Live.js is:
Once the monitored .css file is saved, changes are implemented without reloading the whole page.
Ranked in these QuestionsQuestion Ranking
Pros
Pro CSS injection
Once the monitored .css file is saved, changes are implemented without reloading the whole page.
Pro Multiple browser support
Live.js has multiple browser support, it supports Chrome, Firefox, Opera, Safari and IE6+. Basically almost all the browsers that are currently in use.
Pro Easy setup
Setting up Live.js is extremely easy, the developer either adds the live.js script inside their page, or if they want to monitor only CSS changes, they can add the bookmark that is found on the Live.js homepage.
Pro Server-side PHP support
Reloadr has a reloadr.php file included, which when configured, monitors and .php file in the project folder. Once a .php file is updated, reloadr automatically reloads the page.
Pro Easy setup
Setting up Reloadr is rather easy. There are only two files that need to be included in the project folder, then the reloadr.js needs to be loaded in the view and the method to run Reloadr needs to be called. After that, everything is set up and ready to go.
Cons
Con No cross-device support live or otherwise
Does not have support for multiple devices or multiple browsers for live reloading.
Con No cross-device support
Reloadr does not support cross-device testing and live reloading.