Hacker News new | ask | show | jobs
by skrebbel 5157 days ago
I really subscribe to the attitude in this post. We're developers, we're supposed to make decent software. Our users won't care whether it's our fault or somebody else's if the software doesn't work. Just like you don't go blaming the database if your app becomes slow, you shouldn't blame the browser for rendering your page wrong, even if you're right!

Dammit, we're grown ups here. Make decent software! Test it! Automate the tests! Gracefully degrade! Yes, it's difficult, yes, it's costly! Get over it already!

Either make a fancy web app that works, or just make it highly non-fancy (HN, anyone?) to avoid all the headache. Or go somewhere halfway, as long as you're in control.

2 comments

Absolutely. IE still has tons of users in the world, and it seems a joke to not invite them to the party. It doesn't really bother me as much if they change the features per browser platform, but when you visit a site and it browser sniffs and comes back with a blanket message "Browser not supported please upgrade." that's when I know that the dev is a lazy piece of shit. They don't even bother to try to let it degrade so that people can still access the content, they just shut it off. Rediculous and immature is what this is, why would you put effort into being such a hater especially when its your customers that are being stopped?

I suggest that we windows users boycott the sites that simply block IE. If it removes features I would skip it as well. Not supporting IE shows a lack of commitment to your users. As a user, I object to such half-assed notions. Its already bad enough with the entire dev community telling their users what they must do and how they must act. There is really no reason to be blocking IE10 at this point (yes I've seen it and was shocked and amazed that the fool would actually do that).

I agree. Or at the very least, identify what your users are using (in my case IE9 and webkit via iOS) and test accordingly. Granted I am only making things for internal consumption among a very small pool of users, but still If I decided to only test for Safari and Chrome, I need my teeth kicked in for being lazy.