3 ms·

How about you link which xkcd [0] comic and Joel [1] blog post you're talking about rather than assuming we know. [0] It's not capitalised [1] Spolsky, I assu

by eterm 11y ago

How about you link which xkcd [0] comic and Joel [1] blog post you're talking about rather than assuming we know. [0] It's not capitalised [1] Spolsky, I assume.

jasonkester 11y ago
Sorry about that. I expected that the Internet would have sorted that out for me by now. Googling: https://xkcd.com/927/ https://xkcd.com/927/ http://www.joelonsoftware.com/items/2008/03/17.html http://www.joelonsoftware.com/items/2008/03/17.html
- DiThi 11y ago
  Joel's article is barely relevant now. The main problem has been layout discrepancies, and the pages were made for IE+others back then. Nowadays it's very difficult to step on something not properly supported in your target browsers (except if your target includes old versions of IE). I develop exclusively on Chrome with a lot of fancy HTML5 stuff and very rarely I have to tweak something for Firefox, IE11, Safari, Opera... It's a completely different scenario than when I did web dev in 2008. Also, Joel article is not fifteen years old, it's nine.
  - jasonkester 11y ago
    Sounds like you're not pushing things as much as you used to in '08. The situation is no different today than it was in 1996 when I started this ride. There are sections of my current codebase that switch for iOS 4, 6, 7, 8+, android and desktop Chrome, working around idiosyncracies of each. There's also IE, Firefox and "am I running from the local filesystem" checks in there. All necessary to work around real differences in implementation in the most current crop of "modern" browsers. It's a rare feature that I can ship that works out of the box in every browser. But, as it was 20 years ago, this is the job we signed up for. I just wish people stopped going out of their way to add more unnecessary things that I need to special case around.
    - tuxracer 11y ago
      As a side note, new versions of iOS get adopted extremely fast. It's unlikely you need to maintain code to support more than a single version of iOS back. https://developer.apple.com/support/app-store/ https://developer.apple.com/support/app-store/

by eterm 11y ago

How about you link which xkcd [0] comic and Joel [1] blog post you're talking about rather than assuming we know. [0] It's not capitalised [1] Spolsky, I assume.

jasonkester 11y ago

Sorry about that. I expected that the Internet would have sorted that out for me by now. Googling: https://xkcd.com/927/ https://xkcd.com/927/ http://www.joelonsoftware.com/items/2008/03/17.html http://www.joelonsoftware.com/items/2008/03/17.html

DiThi 11y ago
Joel's article is barely relevant now. The main problem has been layout discrepancies, and the pages were made for IE+others back then. Nowadays it's very difficult to step on something not properly supported in your target browsers (except if your target includes old versions of IE). I develop exclusively on Chrome with a lot of fancy HTML5 stuff and very rarely I have to tweak something for Firefox, IE11, Safari, Opera... It's a completely different scenario than when I did web dev in 2008. Also, Joel article is not fifteen years old, it's nine.
- jasonkester 11y ago
  Sounds like you're not pushing things as much as you used to in '08. The situation is no different today than it was in 1996 when I started this ride. There are sections of my current codebase that switch for iOS 4, 6, 7, 8+, android and desktop Chrome, working around idiosyncracies of each. There's also IE, Firefox and "am I running from the local filesystem" checks in there. All necessary to work around real differences in implementation in the most current crop of "modern" browsers. It's a rare feature that I can ship that works out of the box in every browser. But, as it was 20 years ago, this is the job we signed up for. I just wish people stopped going out of their way to add more unnecessary things that I need to special case around.
  - tuxracer 11y ago
    As a side note, new versions of iOS get adopted extremely fast. It's unlikely you need to maintain code to support more than a single version of iOS back. https://developer.apple.com/support/app-store/ https://developer.apple.com/support/app-store/