When comparing LiveReload vs Reloadr, the Slant community recommends LiveReload for most people. In the question“What are the best cross-browser live-update / synchronization tools?” LiveReload is ranked 3rd while Reloadr is ranked 8th. The most important reason people chose LiveReload is:
LiveReload supports LESS, SASS, Compass, Stylus, CoffeeScript, IcedCoffeeScript, Eco, SLIM, HAML and Jade out of the box. It instantly compiles them and puts the compiled files in the specified folder.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Great bundled compilers
LiveReload supports LESS, SASS, Compass, Stylus, CoffeeScript, IcedCoffeeScript, Eco, SLIM, HAML and Jade out of the box. It instantly compiles them and puts the compiled files in the specified folder.
Pro Works with most modern browsers
LiveReload supports Safari, Chrome, Firefox, Mobile Safari and Opera with web sockets enabled.
Pro CSS injection
Once the monitored .css file is saved, changes are implemented without a refresh.
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 To use it, a code snippet or an extension to the browser needs to be added
To use LiveReload, a code snippet needs to be added inside the view, or an extension to be installed to the browser(s) of choice. While it's not too much work, it can be a hassle and a deal-breaker for some people.
Con No cross-device support
Reloadr does not support cross-device testing and live reloading.