Re:Microsoft to stop producing Windows versions
by 72deluxe on Monday May 11, 2015 @05:09AM
(#9523456)
Very informative, thanks. I write software for my daily job on OSX and I get the feeling that if you're not "current" then they don't care. Look at how they handled the recent security update and left all Mavericks users in the lurch by not back-porting the fix. (Does anyone know if they ever did?)
Re:Microsoft to stop producing Windows versions
by danieldk on Monday May 11, 2015 @06:27AM
(#9523669)
Which vulnerability?
https://support.apple.com/en-us/HT201222
I was under the impression that they are currently updating 10.8 to 10.0 (if it affects all these releases).
Re:Microsoft to stop producing Windows versions
by 72deluxe on Monday May 11, 2015 @07:06AM
(#9523788)
Specifically, OS X Yosemite v10.10.3 and Security Update 2015-004
Admin Framework
Available for: OS X Yosemite v10.10 to v10.10.2
CVE-2015-1130 : Emil Kvarnhammar at TrueSec
https://support.apple.com/en-gb/HT204659
https://truesecdev.wordpress.com/2015/04/09/hidden-backdoor-...
Are they backporting this?
Had this experience with Mac OS X. For 10.4 they switched to a new, dynamically linked libstdc++ that used the new Itanium C++ ABI. 10.3 had a statically linked libstdc++ and the old ABI.
They pushed out an OS update that installed the new libstdc++ on 10.3, breaking linking against libstdc++ with standard cxxflags. You see they had integrated cross-compilation for 10.3 into the new Xcode on 10.4, and didn't give a shit about people who were still compiling stuff on 10.3.
I decided after that that if Apple was going to break working compilation on my OS because I hadn't upgraded to the newest and shiniest, then they didn't really want my money. They seem to be doing OK without it, and I'm doing fine without them.
If Microsoft pulls this sort of stunt with Windows, then fuck everything about this change. They're such sticklers in the opposite direction, doing so much to ensure backward-compatible everything that the house of cards sometimes comes crashing down, that I don't think that will be a problem with Windows 10+x.