2. Note that immediately before your quote, he made the same point I made: “Microsoft intentionally let IE6 development come to a halt because it was no longer strategically beneficial to them”.
3. In addition to reversing your earlier position on the first point, you never stated anything like his second point – just a tangent from the topic in question. You could have fleshed it out into something similar but never did.
4. There's potentially an interesting discussion about the benefits of API stability but that's not conclusively proven – there are many confounds – and there's a separate question of actually specifying behaviours and fixing bugs in the various in-the-wild-versions. As anyone who was working on the web in that era remembers even IE6 wasn't reliably a single target since key features depended on the combination of Windows patches installed on the client. There would have been zero downside had Microsoft more aggressively promoted updates so IE would consistently support HTTP compression, SSL, caching, etc. rather than marking them as minor updates.
2. Note that immediately before your quote, he made the same point I made: “Microsoft intentionally let IE6 development come to a halt because it was no longer strategically beneficial to them”.
3. In addition to reversing your earlier position on the first point, you never stated anything like his second point – just a tangent from the topic in question. You could have fleshed it out into something similar but never did.
4. There's potentially an interesting discussion about the benefits of API stability but that's not conclusively proven – there are many confounds – and there's a separate question of actually specifying behaviours and fixing bugs in the various in-the-wild-versions. As anyone who was working on the web in that era remembers even IE6 wasn't reliably a single target since key features depended on the combination of Windows patches installed on the client. There would have been zero downside had Microsoft more aggressively promoted updates so IE would consistently support HTTP compression, SSL, caching, etc. rather than marking them as minor updates.