- UL7IM4 G33K
- |
- Senior Legendary Member
"Science without religion is lame. Religion without science is blind." - Albert Einstien
Posted by: aku
Posted by: UL7IM4 G33K
That is wrong, it is not the browser's fault, it is the website for not being compatible. Safari runs much faster than Firefox in how it runs and uses RAM on your Mac. Firefox is slow on a Mac and is better one windows. The way websites work is that you program them to be compatible with several browsers so no one has a problem. If the website doesn't work with a browser, than it is up to the web team to fix the problem, not the person to fix it. Sure it is easier to download a new browser, but you are alienating a large portion of users who use safari (damn near all Mac users).
First impressions are everything, and it doesn't work on the first browser they use, they won't be happy.
Hmm... I'm not sure whether you've actually coded a webpage before or not. But the way it really works is, you code a website using the international standards that all browsers are supposed to follow. Then you go test all the main browsers to see if they work, and you find out that at least one of them doesn't. So you go play around with your code to try to get everything working right. Then you fail at that, so you settle for getting the important stuff right. Since you don't have eternity to get your site online, eventually you have to just say that you're satisfied, and what you have is what's going up. And sometimes you miss something.
Basically, all I'm saying is don't be so judgmental of Bungie.net. It probably (almost certainly) really IS the browser's fault. Of course, it's still the web team's responsibility to clean up the browser's mess, so this is a good thing to point out. I would send an email to bnetbugs@microsoft.com. That's what Achronos has always suggested.
Safari uses all the same standards as Firefox, Camino, and every other browser except one... which is Internet Explorer. Internet Explorer is the ONLY browser that uses a different standard which Microsoft tried to force on everyone. This is one of the reasons Internet Explorer was the only browser which couldn't display .png images correctly.
I haven't written code for a site personally, but I have assisted in site building many times and I do know what is going on, I think that I worded it a bit wrong though in my first post. I am not saying that it is necessarily the coder's fault, but it is still his responsibility to check how well it works on every browser, like you said.