4 ms·
> But adding a link to the page then took 2 weeks and 600 lines of code That is interesting, without giving away in proprietary info, what sort of changes did
by rileymat2 11y ago
> But adding a link to the page then took 2 weeks and 600 lines of code
That is interesting, without giving away in proprietary info, what sort of changes did you have to make to add a link?
- nostrademons 11y agoIt's hard to really describe without giving away proprietary info, but some things that are public-but-not-commonly-thought-of include: how do you propagate "sticky" settings like SafeSearch, a user-defined current location, or multi-login? Is it an ad-click, in which case it needs to be tracked rigorously because real money is changing hands for it? Or is it a result click, where we want to do anything possible to avoid introducing latency in getting the user to where they need to be? Or a feature click, where the destination is our own servers? Should the browser do a full page refresh, or will it do an AJAX fetch for only part of the page? If it's an AJAX fetch, what needs to be refreshed? Does a history entry need to be pushed? Are we going to display something special if the user hits "back", like Facebook does for "More stories like this" (the feature in question was actually one of the first sites that did this, before Facebook)? What happens if we've changed the code on the server while the user has an outdated page open in their browser? What are all the browser differences in handling these?