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

-- Forwarded message -- From: Argent mailto:secret.arg...@gmail.com> > Date: Sat, Jul 9, 2016 at 2:52 PM Subject: Re: [opensource-dev] About memory management on macOS 10.12 (Sierra) potentially affecting all viewers To: Geir Nøklebye mailto:geir.nokle...@dayturn.com> > Cc:

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

n email to Oz and feel him out on opening a Storm jira. >> But be warned it would have to be detailed and include build and test cases. >> Nicky >> -- Forwarded message ------ >> From: Argent mailto:secret.arg...@gmail.com>> >> Date: Sat, Jul 9, 20

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 mi

[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 t

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 eff

[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" wrote: > In comment t

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 p

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 product

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

In comment to Geenz Spad mailto:ge...@exodusviewer.com>>: 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 the code much more portable

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

Literally all this does is enable ARC. Don't forget that Apple still allows opt-out on a file by file basis for situations where ARC is not desired (such as cases where the compiler isn't doing something that you want WRT retaining objects outside of autorelease pools). This does not change th

[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: https://developer.apple.com/library/ios/releasenotes/ObjectiveC/RN-TransitioningToARC/Introduction/Introduc

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

On July 8, 2016 at 4:36:39 PM, Geenz Spad (ge...@exodusviewer.com ) wrote: To my knowledge, manual memory management is still supported under OS X 10.12, It would take an incredible amount of effort to deprecate since you’d need to fundamentally change NSObject,

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

https://xkcd.com/386/ With that out of the way, autorelease pools don't have much to do with garbage collection - in fact the document that you've linked to specifically outlines the following with regards to autorelease pools and GC: > In a garbage-collected environment,

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

Since it’s clear you just want to argue and have no interest in understanding memory management, we’ll leave it at that then. I really doubt the other hundred people subscribed to this list are interested. --  Cinder Roxley Sent with Airmail On July 8, 2016 at 3:13:44 PM, Geir Nøklebye (ge

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

I cannot see there is anything “advanced” MRR (manual retain-release) going on in: NSAutoreleasePool *pool = [[NSAutoreleasePool alloc]init]; insert your viewer code here [pool release]; That can’t be handled with @autoreleasepool, if you even need to handle it outside the main thre

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

None of the examples you pasted have anything to do with Apple’s garbage collector, hun. They’re just examples of advanced MRR.  As I already stated, the viewer has never used Apple’s garbage collector. It uses a combination of autorelease pools and MRR which is perfectly fine to do, especially

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

> Cinder Roxley said: > The viewer has never used the garbage collector so it?s not an issue. Why is it that in llopenglview-objc.mm, as en example, we have statement like: NSOpenGLPixelFormat *pixelFormat = [[[NSOpenGLPixelFormat alloc] initWithAttributes:attrs] autorelease]; or - (void)d

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

On July 7, 2016 at 1:57:23 PM, Geir Nøklebye (geir.nokle...@dayturn.com ) wrote: Apple posted the first public beta of macOS 10.12 (Sierra) today, meaning some users will install it and find there are issues with just about every viewer. >From the Xcode 8 bet

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

Apple posted the first public beta of macOS 10.12 (Sierra) today, meaning some users will install it and find there are issues with just about every viewer. From the Xcode 8 beta 2 release notes, please take note that: macOS 10.11 was the last major release of macOS that supported the previously