Про Sendable и Sendable с собачкой! С примерами и объяснением, конечно. https://www.avanderlee.com/swift/sendable-protocol-closures/
👍5
Signed Surik Sarkisyan

Channel
@ios_heads
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
5,295subscribers
-15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001148524011 |
|---|---|
| Type | Channel |
| Username | @ios_heads |
| Created | Between 1 June 2017 and 31 July 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/ios_heads |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 20:34 | 5,295 | -10 |
| 7 Aug 2026, 00:03 | 5,305 | -5 |
| 6 Aug 2026, 04:16 | 5,310 | no change |
| 6 Aug 2026, 04:09 | 5,310 | first reading |
23 posts held, back to 19 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 23 (19 May 2026 – 10 August 2026) |
| Views total | 10,669 |
| Reactions total | 40 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 04:29 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
104 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 36.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 38 | 36.5% | |
| 👍 | 16 | 15.4% | |
| 💩 | 12 | 11.5% | |
| 👎 | 11 | 10.6% | |
| 🔥 | 11 | 10.6% | |
| 😁 | 8 | 7.69% | |
| 🤡 | 7 | 6.73% | |
| 👏 | 1 | 0.962% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 23 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 112reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 19 May 2026 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Про Sendable и Sendable с собачкой! С примерами и объяснением, конечно. https://www.avanderlee.com/swift/sendable-protocol-closures/
👍5
Signed Surik Sarkisyan
Автор утверждает, что AI резко увеличил объём генерируемого кода, из-за чего обычный «человеческий» code review перестал масштабироваться: разработчики тонут в тысячах строк, дублировании и типовых ошибках. В статье автор рассказывает свое видение решения проблемы! https://swiftandmemes.com/ai-broke-code-review-heres-how-to-rebuild-it/
😁3👍1
Signed Surik Sarkisyan
Сразу скажу, что мне не нравится этот ресурс и мне не нравятся статьи этого автора, я их примерно всегда игнорирую и не делюсь с вами, потому что они достаточно сомнительного качества, но тут вот хочу поделиться небольшим материалом о том, какой апдейт получил AsyncImage. Не факт, что этот апдейт нужен будет многим, но хотя бы знать про то, что теперь такая опция есть, будет полезно! https://nilcoalescing.com/blog/As…
🤡7
Signed Surik Sarkisyan
Ну и опять для новичков, но не только. Про MainActor в Swift. Очень много примеров и объяснений, достаточно подробный материал! https://www.avanderlee.com/swift/mainactor-dispatch-main-thread/
❤5😁3🔥1
Signed Surik Sarkisyan
Что-то довольно интересное от Claude Code про то, как тестировать с ними аппку на симуляторе. Сам пока не тестировал, но скоро планирую! https://code.claude.com/docs/en/desktop-ios-simulator
👎4❤2
Signed Surik Sarkisyan
Простите за отпуск и отсутствие статей. Возвращаемся с действительно полезным материалом! Одна из основных проблем всех, кто работает на маке и не имеет пары терабайт жесткого диска (а может и для них тоже основная) - это отсутствие свободного места. И если вы вдруг еще не научились чистить сами, то статья тем более для вас. А если даже научились, думаю вариант автора статьи будет получше. В общем статья о том, как к…
❤9
Signed Surik Sarkisyan
Ну если вдруг по какой-то из причин вы не особо знаете про defer, то вот отличный материал об этом. Вдруг вы совсем новичок, то вам будет полезно! https://www.avanderlee.com/swift/defer-usage-swift/
Signed Surik Sarkisyan
Классная статья про два очень неприятных бага анимаций в SwiftUI, где проблема в том, как SwiftUI пересобирает дерево вьюшек (и не только в этом). https://fatbobman.com/en/posts/debugging-notes-on-two-swiftui-animation-bugs/
👍5🔥1
Signed Surik Sarkisyan
Очень прикольный и интересный материал о том, как под капотом устроен SwiftUI! https://aleahim.com/blog/swiftui-is-one-graph/
🔥8👍1
Signed Surik Sarkisyan
Немного про обновления в работе с Concurrency в Swift 6.4 https://www.avanderlee.com/concurrency/swift-6-4-whats-new-in-concurrency/
👍2🔥1
Signed Surik Sarkisyan
Еще немного с последнего WWDC. Про Xcode и всякие фишки работы с ним! https://antongubarenko.substack.com/p/wwdc26-xcode-tips-and-tricks-group
❤1
Signed Surik Sarkisyan
Автор достаточно ёмко делится своим впечатлением от WWDC 26! Материал не такой уж маленький, но все разложено по топикам, можете прочитать только те, что вам интересны. https://fatbobman.com/en/weekly/issue-139/
👎1
Signed Surik Sarkisyan
Showing the 12 most recent of 23 posts we hold for @ios_heads. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 181,625 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“iOS.Devs” (@ios_heads), 5,295 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ios_heads.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.