Hacker News new | past | comments | ask | show | jobs | submit login

So Windows has become more sane than OS X in terms of security updates?

EDIT: Windows 7 was released in 2009 and is still receiving security updates. 10.6 was released in 2011 and has been EOL'd. Seeing as both people still want to use these products, but one group is being forced not to, that's why I'm saying OS X is taking a less sane stance than Windows.

Is this false?




OS X upgrades are free, more like Windows Service Packs in a way. Microsoft also drops support for pre-SP versions of Windows after a time. The clock is ticking for Windows 8.0; you have to upgrade to 8.1.


Free upgrades can still come at a cost.

Multi-monitor full-screen was broken from 10.7 through 10.8. Thousands complained, Apple claimed it a feature.

Not fixable, not tweakable, not reversible. 10.6 or one full-screen monitor at a time.

Fuck off, Apple.


I worked on the full screen feature in 10.7 through 10.9!

Full screen in 10.7 and 10.8 did render secondary displays useless. But it was a new feature in 10.7, so there was nothing to reverse. You can't take Safari, Mail, etc. full screen in 10.6.

Perhaps there was an app you used that switched from a custom full screen implementation to the system one, and so regressed on secondary displays?


VLC, iTerm (& Terminal? I think), Chrome, Firefox, ... Most things I used had some sort of full-screen mode that was then "hijacked" by 10.7's native full-screen mode. I say "hijacked" because even versions that were pre-Lion would somehow end up using the native "feature".

The thing to reverse would have been the "switch to new workspace when full-screening" - or at the very least make it optional. Certainly not respond "that's a feature" and close as "working as expected" when thousands complain.

I failed to see the value in that feature even with a single screen. An action that used to happen instantaneously now took 1-2s. and a dizzying sliding animation. (Many a flow was lost to toggling full-screen by accident - whereas previously you could toggle/toggle back immediately without losing your mental state - surely you appreciate that as a developer?).


Ok, I get it: you don't like how the system full screen integrates with workspaces, and you were peeved when other apps adopted it in place of their own implementations. Of course Apple did not "hijack" anything: full screen support has always been strictly opt-in. But apps would feel pressure to adopt the system implementation.

Full screen was an effort to make OS X more usable on small displays - recall that the 11" MacBook Air had just shipped. It didn't make much sense for media playback apps to adopt the system full screen mode, especially as it was in 10.7-8.

I would have loved to enable a system mode where full screen windows could coexist in the same workspace as unrelated windows, but this would have been a new feature, not something we could have achieved by reversing anything. And eventually Apple did enable a new mode, which was what shipped in 10.9.

Oh, and if you filed a bug, then whoever closed it as "working as expected" made a mistake. There was a (heavily duped) bug tracking the uselessness of secondary displays in FS, and it was closed when 10.9 shipped. I may even have been the one to close it, I don't remember.


Of course Apple did not "hijack" anything: full screen support has always been strictly opt-in. But apps would feel pressure to adopt the system implementation.

This doesn't make much sense, does it? Obviously apps adopt the system implementation. The problem the OP is talking about is that the system implementation became pretty weird, broke some apps that used to work just fine (especially lots of xquartz ones), and thought that the best use for your extra monitors was to just display a dark gray pattern.

Personally, I learned to live with it (sigh, uncheck "displays have separate spaces"), but it does seem like a good example of Apple shoving a half-baked idea out the door.


QuickTime and iTunes. I used to watch tv or a movie on one of my displays while coding on another. Instead I got to watch linen one screen while watching a movie (double whammy here because even showing pure black on the other screen would have been better since at least it wouldn't distract from the video).

I can't specifically recall, but I think the same was true of full screening video content from Safari (perhaps technically a "plugin feature", but maybe html5 video was around?), but QuickTime was 100% an apple regression.


I have no idea how the full-screen mode is supposed to work or what it is supposed to be good for; I just know that every now and then I fat-finger something and accidentally invoke it, at which point whatever single window I happened to be using zooms to take over one of my monitors, while the other monitor turns grey and useless. I don't understand how this could ever be a useful feature.


> Fuck off, Apple.

Log off, user.


I took it personally because my vendor condescendingly told me that the fact that I can't use my environment (multi-monitor) the way I wanted (full-screening applications) was actually a feature. Apple was telling me to STFU or GTFO.

So I did the latter :)


All you can do is seek your own joy. Expecting others to do that for you is setting expectations. Not sure why I got the downvotes, but I'm happy you got free of OSX. I'm still hanging in there...for now.


How was it broken ?

It worked exactly the same as before only Apple added full screen mode which didnt work in an ideal way. But guess what you don't have to use it. Just maximise your windows normally or use one of the many free tools to do it via keystrokes.

But yeh fuck Apple for offering free OS upgrades that are completely optional.


Windows 7 will be supported through 2020 according to http://windows.microsoft.com/en-us/windows/lifecycle

The updates are free.


Did you read what I said about OS X upgrades being like Service Packs? Did you read your link?

> Support for Windows 7 RTM without service packs ended on April 9, 2013.


A service pack doesn't completely redesign how people interact with Windows, though. But OS X "service packs" tend to do just that. In fact, that was the author's frustration.

Seeing as OS X service packs also come out very frequently, whereas Windows are very rare, I'm not sure the two are comparable.

I should probably bow out now. I just thought it was interesting.


Bow out if you will, but I've agreed with everything you've said thus far and don't think you made any false/slanderous/etc statements.


I think the principle attribute that determines how long support lasts is the cost to get to the next supported version and not anything to do with feature differences. Apple made the decision to give away upgrades precisely so they could move people off old versions I suspect.


They'd be like Service Packs if Service Packs broke backwards compatibility and changed core functionality of the OS, which they typically don't. They are not analogous.


Is it meaningful to compare it to a service pack when there are significant changes such that they're driving users away?


I believe 10.6 was released in 2009, not in 2011[1]

[1]http://en.wikipedia.org/wiki/Mac_OS_X_Snow_Leopard


>10.6 was released in 2011

Wikipedia says 10.6 was released August 28, 2009.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: