Erik Wright
Jul 10, 2017 · 1 min read

Great historical recap of the common JS frameworks we’ve had over time. While I try to stay as far away from any abstraction layers as I possibly can, I can certainly understand why development teams would choose a framework for their projects.

However, what I really want to know is if someone has implemented proper client-server side timeout verification yet… Why do I ask? Well, because I still find myself refreshing JS webapp sites on a daily basis when the frontend view becomes de-sync’d with the backend DB and model controller.

For example, Facebook’s Ad Manager, Trello, and even Google Drive apps in Chrome all become unresponsive sometimes, despite my always online 150mbps connection. I hope there’s a library somewhere out there, or at least under development, that sends a heartbeat to check for and correct anomalies on-the-fly. If so, I’d like to see it implemented on all JS libraries across the board, because there’s nothing worse than losing your changes because someone forgot to properly implement integrity checking.

    Erik Wright

    Written by

    Developer, IT Consultant, Photographer