i think cutting off dependencies on ms is a great idea. i say, it's about time.
i despise ie for many reasons, the greatest of which is standard compliance or the lack thereof. for some reason, ms sees nothing wrong with adding their own little tweaks to existing technologies, or changing them just enough to be able to call them their own.a prime example of this is "JScript" used back in ie4, which is an obvious ripoff of "JavaScript". see the resemblance? boy, we sure don't know where you got that idea from. the differences are slight, but significant enough to necessitate writing a second version of nearly all scripting. otherwise ie users will complain about things not working, oblivious to the real reason behind it. i go along with it only because their browser is so widely used, and the alternative limits accessibility. i also see this tactic at work in css to some degree, and it sickens me.
a "call to arms" if you will, for any and all web developers/designers who may read this - stay current on coding standards and use them. validators can be found on the left side of this page. also, some literature.
chimera would be an excellent choice of browser for apple to adopt. it's completely osx native which makes it speedier than most others, with the possible exception of icab or opera. having branched from the mozilla project, which complies with standards more extensively than any other i've encountered - almost too much in some instances that i won't elaborate on just now, it would surely set apple in the right direction.
as for ms office, i have no use for it. actually, i try to boycott it wherever possible. there have been rumors on mosr about an impending major appleworks update, a large concern of which is supposedly office compatibility. does this not eliminate the need for ms support of the apple platform? if this pulls through, one of the biggest attractions of switchers will still be there, but will no longer involve ms directly or their notoriously shoddy interface design. good riddance.
personally, if i want to distribute any kind of documentation or paperwork via computer, my first choices are rich text and pdf. both widely used and supported, dare i say more so than word documents. and imo pdf is the way to go for anything intended for print on the receiving end for its accuracy and font inclusion. i would like to point out that anything that can be printed using a standard osx print dialog can be saved in this format.
i'll freely admit my bias against ms and their products. but i would hope this makes quite the convincing argument for the ms dependent. thus ends my rant.
i despise ie for many reasons, the greatest of which is standard compliance or the lack thereof. for some reason, ms sees nothing wrong with adding their own little tweaks to existing technologies, or changing them just enough to be able to call them their own.a prime example of this is "JScript" used back in ie4, which is an obvious ripoff of "JavaScript". see the resemblance? boy, we sure don't know where you got that idea from. the differences are slight, but significant enough to necessitate writing a second version of nearly all scripting. otherwise ie users will complain about things not working, oblivious to the real reason behind it. i go along with it only because their browser is so widely used, and the alternative limits accessibility. i also see this tactic at work in css to some degree, and it sickens me.
a "call to arms" if you will, for any and all web developers/designers who may read this - stay current on coding standards and use them. validators can be found on the left side of this page. also, some literature.
chimera would be an excellent choice of browser for apple to adopt. it's completely osx native which makes it speedier than most others, with the possible exception of icab or opera. having branched from the mozilla project, which complies with standards more extensively than any other i've encountered - almost too much in some instances that i won't elaborate on just now, it would surely set apple in the right direction.
as for ms office, i have no use for it. actually, i try to boycott it wherever possible. there have been rumors on mosr about an impending major appleworks update, a large concern of which is supposedly office compatibility. does this not eliminate the need for ms support of the apple platform? if this pulls through, one of the biggest attractions of switchers will still be there, but will no longer involve ms directly or their notoriously shoddy interface design. good riddance.
personally, if i want to distribute any kind of documentation or paperwork via computer, my first choices are rich text and pdf. both widely used and supported, dare i say more so than word documents. and imo pdf is the way to go for anything intended for print on the receiving end for its accuracy and font inclusion. i would like to point out that anything that can be printed using a standard osx print dialog can be saved in this format.
i'll freely admit my bias against ms and their products. but i would hope this makes quite the convincing argument for the ms dependent. thus ends my rant.
