This is a good reminder about how the "support popular browsers" approach of web development is flawed. And how sites, and thus the code driving them, live a lo

This is a good reminder about how the "support popular browsers" approach of web development is flawed. And how sites, and thus the code driving them, live a lot longer than expected. This kind of technical debt accumulates, fixing it involves rebuilding it (probably a clean slate approach, since there are issues caused by the underlying Siebel baseline). It's also a great comparison with the GDS Team's gov.uk initiative, the difference in quality is distinctively noticeable. That quality is based, not on the popular browsers of today, but based on the fundamental premise of the web as an open and platform neutral environment. I guess, in 5, even 10 years, this iteration of gov.uk will still be a reference example of a high quality web development build. I know a couple of the GDS Team behind the gov.uk project are regulars here. To them, thanks for the amazing work, the attention to detail. I think this is the first time where a UK government organisation/agency is leading web development by example. This is a great example of high quality web development being done at the fraction of the budget given to high profile government IT project failures. Certainly, smaller, agile, internal, passionate team of skilled individuals outperforms the huge contracts to IT/Consulting companies.