Исходное сообщение
"Компания Apple выпустила язык программирования Swift 4.1" Отправлено csdoc, 01-Апр-18 16:51
подробное объяснение, почему в Swift сделали ARC и не сделали полноценный GC, как например, в Java: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mo... [swift-evolution] What about garbage collection? [...] > Has a GC been considered at all? GC also has several *huge* disadvantages that are usually glossed over: while it is true that modern GC's can provide high performance, they can only do that when they are granted *much* more memory than the process is actually using.  Generally, unless you give the GC 3-4x more memory than is needed, you’ll get thrashing and incredibly poor performance.  Additionally, since the sweep pass touches almost all RAM in the process, they tend to be very power inefficient (leading to reduced battery life). I’m personally not interested in requiring a model that requires us to throw away a ton of perfectly good RAM to get an “simpler" programming model - particularly on that adds so many tradeoffs.

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> подробное объяснение, почему в Swift сделали ARC > и не сделали полноценный GC, как например, в Java: > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160208/009422.html > [swift-evolution] What about garbage collection? > [...] >> Has a GC been considered at all? > GC also has several *huge* disadvantages that are usually glossed over: while > it is true that modern GC's can provide high performance, they > can only do that when they are granted *much* more memory > than the process is actually using. Generally, unless you give > the GC 3-4x more memory than is needed, you’ll get thrashing > and incredibly poor performance. Additionally, since the sweep pass touches > almost all RAM in the process, they tend to be very > power inefficient (leading to reduced battery life). > I’m personally not interested in requiring a model that requires us to > throw away a ton of perfectly good RAM to get an > “simpler" programming model - particularly on that adds so many tradeoffs.
	Введите код, изображенный на картинке: