Web

I was asked a very interesting interview question today. Lets assume you have a single page application running on n users computers as a dashboard and you updated the application, how does all of the clients receive and manage the updated assets without incurring a browser refresh. The first problem to figure out is how do I know the application was updated? Polling the entry bundle asset Polling the Index.html and comparing hashes/versions Polling some custom tiny server text doc Dashboard websocket contains the version On acquisition of new data it contains version We don’t update until a change of route Now we have a version, we distinguish that the server version is ‘greater’ than ours. How do we acquire the new asset? ...

I’m commonly asked why more people don’t choose angular2 which in my head I correct to angular. (we’re on angular 3 alread.. no, 4,… no.) Quite simply, the answer is Typescript. Whether we like it or not the majority of javascript developers in our field are new or mediocre developers who don’t have the time or cognitive ease to attempt to learn another language. It was a huge mistake for the team to release the library with the small amount of constantly outdated documentation entirely in Typescript. Most stackoverflow searches for angular aren’t even relevant or accurate given the constantly changing api. Without good documentation, and so much irrelevant or outdated answers on stackoverflow these developers lose hope, and angular lost potential users. ...