4 ms·
> On non-IE browsers, the difference in speed is negligible Are you suggesting that people develop two versions of their JS? One for IE and one for everyone el
by mr_justin 17y ago
> On non-IE browsers, the difference in speed is negligible
Are you suggesting that people develop two versions of their JS? One for IE and one for everyone else? Just to appease the pedantics of JS DOM manipulation?
For small bits of HTML, DOM creation/insertion is fine for reasons you have cited (attaching events, etc), but for a bunch of markup, sticking to your guns on this policy is going to cost you your job.
- axod 17y agoNo, I'm saying that if you don't mind making IE users experience worse than other peoples, use the DOM methods. Making IE users experience worse also pushes people toward other browsers, which is a very good thing.
- mr_justin 17y ago> Making IE users experience worse also pushes people toward other browsers That is simply false. The average internet user should not have to make that leap of faith. They simply will think your website/app is crap and they will stop using it, because there's probably another product out there that does the same thing but actually works for them. If you want to gain users and keep them, you do not make their experience intentionally bad.
- axod 17y agoMy experience is the opposite of yours. IE usage is the minority, so I don't feel bad if their experience is slightly worse than users using a better browser. When they come and ask why X is slow, we send them over to firefox/safari/chrome, and they thank us.
- mr_justin 17y agoSo where do you work? Is it: A) A fantasy land B) A college computer lab C) Develop intranet apps for a small company
- axod 17y agoI wrote http://www.mibbit.com http://www.mibbit.com - so none of the above. I get to decide what I do, and so far it's worked: http://tinyurl.com/d8nqu7 http://tinyurl.com/d8nqu7 (Traffic growth) If you work in the corporate world, then totally. You probably have to bend to IE's every whim.