You said it doesn't work in the "latest (current)". Which it works fine, if your people knew what they were doing. Then you try to change your post's meaning... nice.
For the third time: It. Does. Not. Work.
I knew about the terminal command from the start - but where all other browsers use a GUI, and mainstream ones like Mozilla have the features visible on the menus always - safari has nothing in-browser to see what the error-message *caused by the browser* is.
Apple pioneered standards in GUI design, yet their own flagship web-browser "doesn't do" error-message dialogs, nor even use the status bar for them (which is lame, but better than nothing). Personally, I find that unimpressive.
You said it requires a "secret" hack to turn on. Which it requires a defaults write, never been a secret, it's a developer tool (which is what the debug line is aimed at).
I couldn't find it documented anywhere except on the apple developer website - there was no menu option, nothing in preferences, nothing in system preferences. That's not a normal application feature AFAICS.
Shrug. YMMV on this point - but to me when you do not use the standard for setting a preference (the apple application menu) and having to go outside the app to a system-dependent setting is a hack. Not having any clue as to how this works or why within the app itself makes it a deliberately hidden, or secret, hack.
You say that bugs release "1 month ago" are so severe that many users stop using it. Ok, um, what? Where is even the anecdotal evidence?
I use a mac every day, but I don't sit around in the mac community. On a daily basis I work with many who do - mostly professional design companies, illustrators on massively souped-up macs (witness we have an Adobe Illustrator file that no-one has yet been able to export from AI because tis so huge it crashes all systems we've tried on so far), programmers, etc. We share news and warnings on things like Tiger. Only one person I know upgraded - everyone else tried on a spare system first. Some people found core apps they needed in order to do their dayjobs no longer worked with Tiger, and so waited for updates from Apple to fix those issues. Others (like myself) were able to migrate their main machine to use Tiger.
You call it a "lame" OS.
Well, each time I've pointed to a conrete problem, you've ignored it
. Concrete problems are severe as:
- apple doesn't (apparently) do basic regression testing
- safari doesn't render XML
- safari doesn't render mainstream webpages
- OS X doesn't support MIME (pointed out various times elsewhere)
- apple broke safari in their minor OS update that they charge a fair whack of money for, and have aggressively pushed to everyone
- OS X leans heavily on certain technologies including Samba - but OS X's samba support is utterly utterly awful. If you look carefully, you'll see a large contributory factor: they are MANY versions behind the current release (of the order of 18 months or so IIRC). Even windows 95 has better samba support than OS X
- previous apple OS updates are well known to have done things like wipe the harddisk, or corrupt it. As far as I know, MS has only once had this problem, ever, and we all know how good they are at writing good code
This is a very ignorant post. Next time instead of coming on here and complaining, do a little research, find out what the problem is and fix it. You'll find that YOU are the isolated case, and YOU should look into why that is.
Shrug. I started the post to request help, but whilst writing it and digging further found out all fingers pointed back to Apple and general shoddiness, and it morphed from a request for help into a warning to anyone trying to debug applets on OS X + safari: don't. Just tell your users to get mozilla, or any other browser that actually works.
EDIT: Anyways, you are pretty damn good at Trolling me, I don't know why I always bite on your obvious flamebait posts.
LOL. Maybe it's better to get a reaction, risk being wrong and stupid, and at least be educated by your fellow posters than to never say anything contentious and never learn anything new?
I know I don't care, and the only people it will hurt is you.
Good. The aim wasn't to hurt anyone, but instead to spare people pain. A lot of us are branching out into bending over backwards to get stuff working nicely on OS X, and here's an example of where it's not worth even trying to.