In this particular case, the Member homepage, there is a lot going on behind the scenes to render that page. Each row is computed with the most recent data possible, to ensure you see information that is pertinent for you. The pause is purely on the server side, not the client downloading assets. We are working on improving this.
As always, it depends on the group or team you are applying for. Some groups actually have a lot of applied computer science concepts and benefit from these type of questions. On my team, Web UI, we typically try to ask questions that pertain to the tasks they would encounter day to day.
We refresh periodically as we dynamically deploy new UI code, which can be accessed at new routes. (/home and /homeV2 for example) This allows us to not have to restart our servers or push out new server code just to serve a new UI at a different (or the same) route.
We like the option of dynamically loading new routes, that point to new endpoints. We also have the ability to release new versions of our UI without redeploying (or restarting) our servers.
Second dmak, would love to understand more. I can following dynamically loading routes but can't follow how that would be implemented end to end. Some things I would be interested in:
- Where do the keep the code that gets executed for new routes? Is that deployed dynamically as well?
- If you are changing routes dynamically how do you test in non-prod, are you constantly syncing non prod with prod?
- How do you control what you deploy dynamically vs what you migrate through the environments?
I use it for 3 different pinned tabs at startup and it works great. It would be nice to have it configurable from the options menu, but I will take what I can get.
I thought apple was allowing accessories to connect to the dock at the bottom after the 3.0 software update. Wouldn't it make more sense, and be sturdier if it was at the bottom? Also, with a bigger piece of hardware you might be able to use the quick pass functionality of some cards (the ones with ultra super secure RFID).
I think there is a licensing fee involved with using the dock connector - at the least you have to apply to Apple and all that.
There's no reason why you couldn't have a slide-in case designed to make this headphone jack-based one more sturdier though, or something along those lines.
Sure, but it won't work with any phone, because Apple uses a proprietary TRRS connector that allows data to be sent to the iPhone/iTouch (used by Apple for an external mic and remote on standard earphones).
I thought perhaps it would work with the iPhone but that does not seem to be the case. Looks pretty neat and simple. As others have said similar to userfly.com.