Yosemite Safari versus teaching and learning: no title bar, and other problems
- Non existent Title Bars (Makes teaching new users more difficult)
Problems with Yosemite in educational environments in general – not classrooms alone – were predictable months ago. I should
never choose to use Safari 8.0 in a demonstration, and so on.
It's not only the removal of the title bar; the initial
response to Command-L is undesirable in a shared environment, and so on. Making your Mac experience
different from anyone else’s by default can be a frustration in a group environment where there's a shared desire for consistency, focus, predictability and order.
In pessimistic mood, I wonder whether Apple allowed enough teachers to test, to repeatedly demonstrate the operating system and gain meaningful feedback,
in teaching environments. Amongst
answers to frequently asked questions:
"… don't discuss the pre-release Apple software with or demonstrate it to others who are not in the OS X Beta Program. …"
– and from the OS X Beta Program Agreement (EA1172, 2014-06-02):
"6. … Except as expressly permitted in this Section 6, you agree that you will not disclose, publish, or otherwise disseminate any Confidential Information to anyone other than individuals who are enrolled in the same individual seed as you, or as otherwise expressly permitted or agreed to in writing by Apple. …"
Happily, feedback-oriented clauses such as those did not prevent Apple from developing some outstandingly good software in the past.
Now there's a great deal to admire about Yosemite, but some of the regressions are almost excruciatingly discordant with Apple's stated desire to produce the best. I strongly suspect that for just a few things, changes were (to put it politely) internally bulldozed through against the wishes of some of the most astute designers and developers. Less politely:
in the new human interface guidelines there's some inexcusable crap – at least, some of the wording there could easily apply to a hairspray or anti-wrinkle cream; at worst,
Apple wilfully ignores the meaning of <title> in HTML … truly a shame.
I quietly hoped for WebKit.app to not display the same UI regressions as Safari, but it does. For me, that was amongst the last straws.
My best advice at this time is to use, if possible, in educational environments, a respectably designed alternative to Safari.
Test builds of OmniWeb are reliable and very presentable for me on OS X 10.9.5. In my occasional tests of Yosemite, the same test builds were no less reliable. The Omni Group has a long history of considerate design; I should recommend OmniWeb without hesitation.
Parallel to using something other than Safari: send feedback to Apple. Make some noise.
Related
The value of addresses/locations/paths/URLs in Safari, and of title bars in general
Visionary Apple approaches to Mac OS X: past, present and future
… I get the sense that Apple no longer has a single, clear, shared vision for OS X. …