[swift-evolution] What about garbage collection?

[Goffredo Marocchi]

I think those changes can be overcome... but yes, it is not something that would happen tomorrow... More like five years from now ;). *Crossing fingers for memristors or some new nonvolatile storage solution to overcome the current flash issue with frequent read/write cycles....*

Maybe enough redundancy and better controllers can allow the same flexibility on mobile's that we enjoy on any SSD on laptops and desktops nowadays and similar I/O throughout though. 

Sent from my iPhone

> On 10 Feb 2016, at 00:32, Greg Parker <gparker at apple.com> wrote:
> 
> 
>>> On Feb 9, 2016, at 2:21 PM, Goffredo Marocchi via swift-evolution <swift-evolution at swift.org> wrote:
>>> 
>> 
>>>> On 9 Feb 2016, at 18:18, Charles Srstka via swift-evolution <swift-evolution at swift.org> wrote:
>>>> 
>>>>> On Feb 9, 2016, at 8:35 AM, Jean-Denis Muys via swift-evolution <swift-evolution at swift.org> wrote:
>>>>> 
>>>>> It’s a long since resolved dispute, and GC won. I don’t want Steve Jobs to reach out from the grave and drag us back to the 70s. There’s nothing special about mobile phones: they are more powerful than the computers that GC won on in the first place.
>>> 
>>> I’d disagree with that, for one rather important reason; the computers that GC won on had virtual memory. On mobile, when your RAM runs out, it’s out. So RAM constraints are somewhat more serious on mobile.
>> 
>> This will be then more fun when we have page file support as virtual memory is already there.
> 
> 
> Unlikely with current hardware technology. NAND storage on mobile devices has limited lifetime based on the number of writes. Adding a swap file would burn through that lifetime awfully fast.
> 
> 
> -- 
> Greg Parker     gparker at apple.com     Runtime Wrangler
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160210/f77e939a/attachment.html>