Re: [opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

I've been following Apple for over 35 years now, and they have introduced and abandoned technologies on a regular basis. You can't dismiss the fact that they introduced and abandoned GC in only a few years and confidently declare that Swift won't go the same way. It might stick. It might not. It

[opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

I said long term, and by long term I mean 5-10 year horizon. For an operating system that is closing in on 35 years of existence, that is a reasonable timespan. ;-)) System 10 (OS X, where X is the roman numeral 10) is now 15 years - 2 years more than SecondLife has been around. During that

Re: [opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

The point is, They announced garbage collection and then deprecated it only a few years later. Meanwhile traditional manual memory management which is like 25 years old, that's still supported. So the odds are, the course of action you're proposing ... it would have lead to TWO big development

[opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

Apple is pretty predictable in how they announce changes to their code. Every summer, at the WWDC, they announce a slew of changes that will be introduced throughout the next year. They also announce deprecated technologies, which usually takes 3-5 years to completely be unsupported. They also

Re: [opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

Look, Geir, not so many years ago the now-deprecated and soon defunct garbage collector was the new hotness. If we'd followed the course you're suggesting now, of always switching to Apple's latest APIs, we'd really be in a pickle now. On Jul 9, 2016 8:58 AM, "Geir Nøklebye"

Re: [opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

The only real thing that matters is, does the viewer run on the new O/S or not? If it runs, all this arguing is kind of pointless. ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the

Re: [opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

Like, I said, just wants to argue. Not interested in understanding. ;) On July 9, 2016 at 7:58:33 AM, Geir Nøklebye (geir.nokle...@dayturn.com ) wrote:  Having worked in Apple Product Management  heh. The GPU crash has been both acknowledged by Apple

[opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

In comment to Geenz Spad >: There is much more to it than the knee jerk opensource community reaction of resisting to "Apple made it the default for new projects, so you should too!” By migrating the code to to the Apple defaults makes

[opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers

To all your nay sayers, just try to compile the viewer with the -fobjc-arcflag that is the default since OS X 10.8 and see where that gets you. I also sugget you read the migration guide: