3 ms·

I'm under the impression that this site doesn't do all that much. Ok... you store URLs, then mark them as "read" and "unread." Not necessarily a good or bad t

I'm under the impression that this site doesn't do all that much. Ok... you store URLs, then mark them as "read" and "unread." Not necessarily a good or bad thing.. I'm sure it's incredibly useful. That's not my point. My point is, how can a 2 page website drop support for a whole browser? Just seems like laziness to me.

brk 18y ago
I think he did a pretty good job explaining why he made the choice to drop support for IE in TFA.
- sam_in_nyc 18y ago
  I read: author wanted to make his website pretty, but IE was making it hard, especially since he was developing on a Mac which made it harder to test, so author dropped support for IE. Author then explains less than 10% of his users use IE, anyway, so it doesn't really matter. Sparks browser war. While I admit, IE really blows, and I hate developing for it, it's really not that bad. It's manageable if you test on it often, which author failed to do. Is it hard to make a 9 cell table to get rounded corners? Or how about learning "hasLayout" which fixes virtually every IE6+ css rendering bug?
  - sprsquish 18y ago
    I think Marco's point was that he's created this site as a fun side project. Supporting IE isn't fun. The vast majority of the site's users aren't IE users so he wont get a lot of flack from its users. I agree that developing for IE isn't the worst thing ever, but it's certainly not fun. I have to side with Marco on this, if I were to build a site just for fun, I'd probably never look at it in IE.
    - sam_in_nyc 18y ago
      Agreed. To each their own. I'd personally rather have more people be able to use it :)
greyman 18y ago
Exactly my thought, it's a simple bookmarking application. And I can't run it on IE7 because author must use rounded corners and at the same time doesn't want to go through the hassle to implement them under IE. ;-)

3 ms·

I'm under the impression that this site doesn't do all that much. Ok... you store URLs, then mark them as "read" and "unread." Not necessarily a good or bad t

by sam_in_nyc 18y ago

brk 18y ago
I think he did a pretty good job explaining why he made the choice to drop support for IE in TFA.
- sam_in_nyc 18y ago
  I read: author wanted to make his website pretty, but IE was making it hard, especially since he was developing on a Mac which made it harder to test, so author dropped support for IE. Author then explains less than 10% of his users use IE, anyway, so it doesn't really matter. Sparks browser war. While I admit, IE really blows, and I hate developing for it, it's really not that bad. It's manageable if you test on it often, which author failed to do. Is it hard to make a 9 cell table to get rounded corners? Or how about learning "hasLayout" which fixes virtually every IE6+ css rendering bug?
  - sprsquish 18y ago
    I think Marco's point was that he's created this site as a fun side project. Supporting IE isn't fun. The vast majority of the site's users aren't IE users so he wont get a lot of flack from its users. I agree that developing for IE isn't the worst thing ever, but it's certainly not fun. I have to side with Marco on this, if I were to build a site just for fun, I'd probably never look at it in IE.
    - sam_in_nyc 18y ago
      Agreed. To each their own. I'd personally rather have more people be able to use it :)
greyman 18y ago
Exactly my thought, it's a simple bookmarking application. And I can't run it on IE7 because author must use rounded corners and at the same time doesn't want to go through the hassle to implement them under IE. ;-)