It's all based on use case, I guess. I spent the early part of my programming career building ERP and Accounting type systems, where real time updates are not factored into any design.
However, of late, I have been working on collaborative type apps, including IoT device programming, and real time updating is not just a luxury, it is expected. Indeed we are seeing things like SSE (Server Send Events) etc. being incorporated in the latest browser specs to support this.
Granted, unless you are using frameworks like Meteor etc., there is still a lot of work to be done to ease the integration between back end server push and browser real time display. Websockets are great, but require a lot of tedious management at scale.
But the thing is - once you start down the path of realtime updated apps, possibilities open up, and you begin to wonder how you used to program without it. For me, it all started when I knocked together this [0] real time update of Hacker News as a weekend project using RethinkDB for push updates, and Vue.js as the front end...
However, of late, I have been working on collaborative type apps, including IoT device programming, and real time updating is not just a luxury, it is expected. Indeed we are seeing things like SSE (Server Send Events) etc. being incorporated in the latest browser specs to support this.
Granted, unless you are using frameworks like Meteor etc., there is still a lot of work to be done to ease the integration between back end server push and browser real time display. Websockets are great, but require a lot of tedious management at scale.
But the thing is - once you start down the path of realtime updated apps, possibilities open up, and you begin to wonder how you used to program without it. For me, it all started when I knocked together this [0] real time update of Hacker News as a weekend project using RethinkDB for push updates, and Vue.js as the front end...
[0] - https://tophn.info