↵

Chrome is the new IE(medium.com)

8 years ago from Marc Edwards, Founder at Bjango

  • Rick LanceeRick Lancee, 8 years ago (edited 8 years ago )

    Gradients are very expensive to draw, fixed elements hurt scrolling performance, paint times often prevent you from reaching a steady 60FPS, and so on.

    If you can't build a smooth 60fps web app you're doing it wrong. It has nothing to do with the browser; it's because your app is badly coded.

    7 points
    • Joakim WimmerstedtJoakim Wimmerstedt, 8 years ago

      I don't think that judgement is fair. 'Badly coded' is not the same as when a developer lacks the understanding needed about the rendering engine. I do however agree on your sentiment that it's not the browsers fault.

      Also, sometimes you need to pull back on resource-heavy design decisions if they're hurting performance.

      1 point
      • Rick LanceeRick Lancee, 8 years ago

        It might have sounded harsh and I agree that it might not be fair, but if you lack understanding you will write "bad" code. It doesn't mean you can improve or be taught to code better.

        1 point