4 ms·

I read comments like this all the time and I feel like I'm in a different world. I just write standards compliant ES6 code, put it through a transpiler and som

• fixermark 8y ago
  It's often the case that this works fine. When you get into corner cases (i.e. if you try to stretch what animation APIs can do or you start to need to care deeply about the performance constraints of flex layout), you start to need to care about how the browsers actually work. ... but you can (and I'd argue in a lot of cases, looking around at the overly-complicated sites on the web, should) write a lot of fully functional web pages by keeping to the standard and trusting it's good enough. We are no longer in the bad old days where IE and other browsers deviated significantly---most of the browsers today adhere closely to the spec, and in the places they don't, it's often more like one browser handles a nasty corner case better than another because the browser built an optimization in for a critical path your page layout cares about.
• fgkramer 8y ago
  I'm tempted to say JS is not the biggest problem between browsers, but CSS... the fact that valid CSS code behaves differently and that it cannot be fixed without changing most of it. Not even mentioning if you actually need to change your DOM structure to make a layout work.