Mojo 1.0: язык от Modular дошёл до стабильной версии Modular выпустила Modular 26.5 и Mojo 1.0 — спустя три года после первого релиза. Заодно почистили язык: переменные объявляются только через var, замыкания унифицированы, остался один тип Pointer, появился Python-подобный синтаксис lambda. Главное — обещание стабильности: в ветке 1.x изменения будут в основном аддитивными, а ломающие — аккуратно, «как в зрелых яз…

Channel
NOP::Nuances of Programming
@nuancesprog
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
56,992subscribers
-91 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001120605809 |
|---|---|
| Type | Channel |
| Username | @nuancesprog |
| Created | 7 July 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/nuancesprog |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:26 | 56,992 | -14 |
| 11 Aug 2026, 19:52 | 57,006 | -19 |
| 10 Aug 2026, 19:12 | 57,025 | -15 |
| 9 Aug 2026, 17:02 | 57,040 | -7 |
| 8 Aug 2026, 18:58 | 57,047 | -5 |
| 7 Aug 2026, 20:27 | 57,052 | -17 |
| 6 Aug 2026, 21:50 | 57,069 | -14 |
| 6 Aug 2026, 02:15 | 57,083 | first reading |
Engagement
26 posts held, back to 8 July 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 17 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.85%
- avg views ÷ 56,992 subscribers
- Avg views / post
- 2,200
- 16 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 16
- of 26 held
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 12 August 2026 |
|---|---|
| Posts held | 26 (8 July 2026 – 12 August 2026) |
| Views total | 35,122 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 19: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.
Recent posts
Nemotron 3.5 Lightning: 30B параметров, 3B активных Nvidia выложила NVIDIA-Nemotron-3.5-Lightning-30B-A3B — MoE-модель с 30 млрд параметров, из которых активны лишь 3 млрд на каждый токен. Формат NVFP4 (4-битный) позволяет запустить её на одной карте с низкой задержкой. Модель поддерживает блоки размышлений <think> и встроенный tool-calling через XML-теги — готовая для агентов без доделок. Минус: NVFP4 нативно раб…
Rust portable SIMD теперь работает на GPU VectorWare заявили о первом запуске core::simd на GPU: тот же код, что на ноутбуке компилируется в AVX или NEON, ложится на варп. Идея простая — SIMT это и есть SIMD: варп из 32 лейнов, а Simd<f32, 32> раздаёт по элементу на лейн. Элементарные операции идут нативно, редукции и свизлы — через warp shuffle, маски — через vote/ballot. Ранее они уже отобразили std::thread на ва…
Джуниор с ИИ пишет код быстро, но не умеет его дебажить Выпускник команды автора выкатил чистый PR на 400 строк за вечер: тесты зелёные, ревью пройдено, а потом в продакшене поехала память — и человек замер. Автор ссылается на исследование Anthropic: писавшие код руками набрали в тестах на понимание 67%, активные пользователи ИИ — 50%, группа «полного делегирования» — меньше 40%. Хуже всего — вопросы про отладку. Г…
Почему C нельзя «спасти», не спасая ABI В C имя функции — единственное, что видит линкер. Объявили do_stuff(long long), а в другой TU реализовали как do_stuff(__int128_t) — сборка пройдёт молча, а на x86_64 вызывающая сторона положит аргумент в rdi, вызываемая прочитает rdi + rsi. Мусор в старших битах вместо ошибки компиляции. В C++ такого не будет: манглинг вшивает типы в символ, и линкер ловит несоответствие. Ав…
CRDT без академических статей: интерактивный курс на JavaScript Lars Hupel собрал серию туториалов про Conflict-Free Replicated Data Types — структуры данных, которые сливаются между репликами всегда и без конфликтов. Всё на JavaScript, весь код исполняется прямо в браузере как в Jupyter: правишь сниппет, нажимаешь Run, смотришь результат. Зачем это вам: любое приложение с офлайн-режимом или синхронизацией между ус…
Рассмотрим поэтапный процесс создания веб-сканера для отслеживания изменений и последующего оповещения посредством e-mail. Работаем с Python, Beautiful Soup и Pipedream. https://nuancesprog.ru/p/15423/ VK: https://vk.com/@nuancesprog-sozdaem-veb-skaner-stranic-s-pomoschu-python Дзен: https://dzen.ru/a/YiaJJedBN25-itgx @nuancesprog #Python
Разбираемся в том, что такое чистая архитектура, какие преимущества она дает и как ей следовать на практике. Рассмотрим все примеры с иллюстрациями. https://nuancesprog.ru/p/15255/ VK: https://vk.com/@nuancesprog-chistaya-arhitektura-rukovodstvo-dlya-nachinauschih Дзен: https://dzen.ru/a/YhKpryffu3osChZf @nuancesprog #SoftwareDevelopment #Architecture
Обработка ошибок - важнейшая часть программирования на Type/JavaScript. Приложение может столкнуться с большими проблемами в будущем, если вы не уделите должного внимания выявлению и регистрации ошибок. Посмотрите, как это делают профи. https://nuancesprog.ru/p/16979/ VK: https://vk.com/@nuancesprog-professionalnaya-obrabotka-oshibok-v-typescript Дзен: https://dzen.ru/a/Y_-4ExyViF3Sxwup @nuancesprog #TypeScript #…
Принято считать ошибающийся ИИ недостаточно умным. На самом деле моделям чаще всего не хватает не ума, а обвязки — четкой инструкции из нескольких простых правил. Узнайте, как написать такую инструкцию, чтобы превратить хаотичное поведение агента на базе ИИ в надежную работу с файлами, тестами и средой. https://nuancesprog.ru/p/32523/ VK: https://vk.com/@nuancesprog-vash-ii-ne-glup-u-nego-prosto-net-obvyazki @nuan…
Сегодня доступно множество инструментов для мобильной разработки. Одним из них является Flutter, который в последнее время стал довольно популярным. Рассказываем, в чем секрет успеха Flutter и почему стоит обратить на него внимание. https://nuancesprog.ru/p/17075/ VK: https://vk.com/@nuancesprog-chto-takoe-flutter-i-zachem-ego-izuchat Дзен: https://dzen.ru/a/ZBYe--bhOw9saTyi @nuancesprog #Flutter
Начните свой проект по науке о данных с создания Python-скрипта, используя библиотеку Selenium для извлечения данных. Предлагаем узнать, как это выполнить в 3 шага. https://nuancesprog.ru/p/16725/ VK: https://vk.com/@nuancesprog-kak-sobrat-dannye-dlya-ds-proekta-s-pomoschu-python-3-shaga @nuancesprog #Python #Selenium
Showing the 12 most recent of 26 posts we hold for @nuancesprog. 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
Citation-graph rank — 720,214 of 1,160,990entries 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.
Forward network
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.
Mentions
Named by 3 registered channels — 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@physics_lib · 145,853
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 13 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
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.
“NOP::Nuances of Programming” (@nuancesprog), 56,992 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nuancesprog.
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.