When comparing Live.js vs Browserlink.vim, the Slant community recommends Browserlink.vim for most people. In the question“What are the best cross-browser live-update / synchronization tools?” Browserlink.vim is ranked 5th while Live.js is ranked 6th. The most important reason people chose Browserlink.vim is:
It's a Vim plugin, so it's natively tied to Vim itself.
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 Native Vim support
It's a Vim plugin, so it's natively tied to Vim itself.
Pro CSS injection
Live injects CSS. This means that any time that there is a change in the CSS stylesheet, the page does not reload, only the CSS does.
Pro Error and console support
Cons
Con No cross-device support live or otherwise
Does not have support for multiple devices or multiple browsers for live reloading.
Con Only supports Vim
Supports only Vim, and works only for developers who use Vim.