Site protection

[raymor]

For me, it's less a matter of revenue than it is sharing the total experience of the beauty of homoerotic fantasy I've created. IE produces beautiful embedded calligraphic fonts;

Raymor, if I lose revenue, so be it. Those who want to share the beautiful experience of what I have created can easily acquire IE, if only for my experience.
It's easy to make IE play endless background wind and surf sounds with voiceover as well, so essential to the total experience.

We're definitely on gaywidewebmasters today. Seriously though, that's
cool. You know what the pros and cons are it sounds like.

IE produces beautiful embedded calligraphic fonts; Firefox et al. do not.

It seems Firefox just added embedded fonts about 18 months ago, in 3.5.
Safari has had embedded fonts since 3.1. Text kerning, ligatures, and multiple
weights along with support for rendering complex typographical scripts were
added in Firefox 3.0.

Yes, I know that with complex coding, I might get everything to work the same way in every browser (for a while), no matter what the browser, but that is not a frustrating complexity that I want to take on.

My experience, in case it's helpful for another project, is that generally if you
design in Firefox, you're designing toward the standards, so other browsers
including Chrome, Safari, and even IE will load the site nicely, because they all
support the same standards like HTML, CSS, etc., though some are more
standards compliant than others. No need for any significant work to make it
work in all different browsers if you design for the standard. On the other hand, if
you start with IE, my experience has been that a lot of IE specific bugs or E,E,E
"features" come up, so it looks like shit in a standard browser and needs a lot of
work to get it to look at work right in any other browser. In summary - starting
with IE leads to a lot of "cross browser" hacks, but starting with Firefox tends to
make a standards compliant site that works in any browser, including IE.