`function update() { $("#live").load("/get_links/hot"); } setInterval(update, 10000);update();`
Polling per se is ok but you should do it on the server and push to the client through web sockets or server-sent events [1].
Refs:
[1] https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...
[2] https://github.com/Max00355/HNLive/blob/master/templates/new...
- Items for users with a delay configured get posted to the API before their content is made available (if you go to the story id on HN proper, there's a * placeholder)
- The odd item will come back as `null` from the API for a while
As long as you deal going from not having content for an item to having content in an update, the API usually corrects itself eventually.
Here are live feeds of new stories and comments from the Firebase API in the client I wrote when it was announced:
[1] https://developer.mozilla.org/en-US/docs/Web/API/EventSource...
A better option than repeated requests every X seconds (or X times per second) is long polling (see https://en.wikipedia.org/wiki/Push_technology for brief notes and your preferred search engine for many examples). You can only do this if you control the back-end (so can dictate its API) or the API you are using explicitly supports long polling, of course.
There are a number of libraries out there that try to wrap the different methods into one so you don't have to worry about compatibility, using the more efficient websockets where possible, falling back to long-poll where not, and sometimes other methods in between (integrating a little bit of flash for instance). http://socket.io/ is probably the best know of these.
It was never implemented directly in IE or Edge (http://caniuse.com/#feat=eventsource), so when you say "work in all browsers" do you discount IE or can you recommend a good well-supported polyfill?
In my personal projects I don't care about legacy browsers (to users that far out of date I say "please go be a pain in the side for someone else"), but professionally I'll have to support at least as far back as IE8 for a while yet and I suspect a great many people are in the same position.