• Eric H.Eric H., over 8 years ago (edited over 8 years ago )

    Clearly the author doesn't fully grasp the complete and utter hell IE provided designers dating back to the late 90s. IE simply broke everything. Safari doesn't do this in the slightest.

    17 points
  • Fred Barker, over 8 years ago

    My main problem with using anything other than Safari when designing/coding on my MBPr is that once I start doing anything intensive like watching videos (tutorials, etc.) on Chrome, my computer sounds like it's about to take off. I've also noticed that my computer runs about 20-25 degrees hotter when using Chrome over Safari, not to mention it devours my battery.

    I know this doesn't change the fact that Safari is lagging from a dev standpoint but I thought it was worth pointing out.

    My MBPr is last year's model with 16GB of RAM, FWIW.

    2 points
  • John PJohn P, over 8 years ago

    showing a brazenness even beyond that of 90’s-era Microsoft

    Someone managed to either repress IE5.5 and IE6 out of the sheer horror or has conveniently forgotten how bad it used to be.

    If anything Firefox is the new IE seen as it dragged it's feet for YEARS on web video, forcing everyone to deliver encodes in the crummy ogm format.

    But yeah I'm sure 4 edge technologies not being included yet is way worse for web devs than YEARS of not supporting the most popular hardware accelerated video coded ever.

    0 points
  • Sam MularczykSam Mularczyk, over 8 years ago

    This is true in terms of release schedule.

    However, I otherwise disagree with this - Chrome is more like IE in that it introduces bleeding-edge, Blink-specific features that other browsers have to rush to implement. -webkit prefixes are flooding the web.

    Sites that say browsers like Firefox aren't supported should not exist. It's not hard to build a site that's supported by all major browsers. Unless it's some weird experiment, it just shouldn't exist.

    0 points