News for hackers. Stuff that matters.

A comment on LiveReload: Reflect CSS Changes Instantly, with No Browser Reload. Parent comment

Re:LiveReload: Reflect CSS Changes Instantly, with No Browse... by ELV1S on Saturday October 29, 2011 @06:26PM (#3172984)
LiveReload should works on every browser that supports WebSockets. It should work on modern WebKit-based mobile browsers.

Live.js uses polling. It sends XHR HEAD request every second.

LiveReload monitors file changes using FSEvents (on Mac OS X) and inotify (on Linux). When the file modified, it pushes its path to the browser and reloads immediately.

[ Parent | on HN ]
Re:LiveReload: Reflect CSS Changes Instantly, with No Browse... by benatkin on Saturday October 29, 2011 @07:27PM (#3173118)
> Live.js uses polling. It sends XHR HEAD request every second.

The horror!

[ Parent | on HN ]
Re:LiveReload: Reflect CSS Changes Instantly, with No Browse... by hnwh on Saturday October 29, 2011 @07:38PM (#3173139)
It is horror when you forget about it, and push it up to production
[ Parent | on HN ]
Re:LiveReload: Reflect CSS Changes Instantly, with No Browse... by benatkin on Saturday October 29, 2011 @07:57PM (#3173192)
Has nothing to do with Live.js then. Isn't really even about a developer's forgetfulness when pushing to production. It would be about failure to set up different production and development environments, which can cause problems much worse than a wasteful AJAX call.
[ Parent | on HN ]