Channel
@scala_channel_ru
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
907subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001122352460 |
|---|---|
| Type | Channel |
| Username | @scala_channel_ru |
| Created | 27 October 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/scala_channel_ru |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 00:01 | 907 | +1 |
| 28 Aug 2026, 20:02 | 906 | -2 |
| 6 Aug 2026, 15:47 | 908 | no change |
| 6 Aug 2026, 15:39 | 908 | first reading |
15 posts held, back to 24 February 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
133 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 43.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 58 | 43.6% | |
| 🔥 | 24 | 18.0% | |
| 🎉 | 15 | 11.3% | |
| ❤ | 13 | 9.77% | |
| 💩 | 8 | 6.02% | |
| 😁 | 8 | 6.02% | |
| 🌚 | 2 | 1.50% | |
| 😍 | 2 | 1.50% | |
| 😭 | 2 | 1.50% | |
| 💯 | 1 | 0.752% |
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 14 of the 15 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 133 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 24 February 2026 to 3 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.
JVM Day 29 августа: новинки JVM мира и –10% на билет Бэкендеры, отличная новость. 29 августа в Москве пройдет конференция для своих. Приглашают Java-, Scala- и Kotlin-разработчиков, архитекторов и тимлидов. Здесь выступят и расскажут: — Андрей Кулешов — что нового в JVM за год. — Сергей Петрелевич — разработка по Mechanical Sympathy. — Александр Ланцов — Java после Loom и другие модели concurrency. — Антон Курако —…
🔥2
sbt-salad-days; sbt plugin to reduce Scaladoc JAR file size. Как многие из нас уже знают, мавен централ ввел паблишинг лимиты; поэтому плагин для снижения скаладок размеров очень актуален. :/ Плагин: https://github.com/sbt/sbt-salad-days Читать подробнее: https://eed3si9n.com/reducing-scaladoc-file-size-with-sbt-salad-days/
🔥3
Дед вещает! https://www.youtube.com/watch?v=Xn_YpUtXWT4
❤12
Пока одни инженерные задачи пропадают в недрах Jira, другие превращаются в темы будущих докладов😀 Если проще — мы открыли прием заявок на Joker 2026. Кажется, что для выступления нужен только уникальный кейс? Не обязательно. Часто хорошие доклады начинаются со сложного инцидента, проблемы производительности, неожиданного поведения JVM, архитектурного компромисса или решения, которое спустя время пришлось пересмотр…
SBT 2.0 🎉 https://www.scala-sbt.org/2.x/docs/en/changes/sbt-2.0-change-summary.html
👍18🎉15
Обратил внимание что у SBT 2 уже 15ый RC! https://github.com/sbt/sbt/releases/tag/v2.0.0-RC15 У ребят уже с апреля обновленный роадмап по этому поводу https://www.scala-lang.org/blog/2026/04/14/last-mile-towards-sbt2.html И статус плагинов на тему поддержки SBT 2; мне надо заняться sbt-jni 🤦♂️ https://github.com/sbt/sbt/wiki/sbt-2.x-plugin-migration
👍7
Антиконференция Summer Merge — перезагрузка для IT, которую нельзя пропустить 🔥 Устали от одинаковых конференций и бесконечных докладов? Summer Merge — это другой формат. — 3 дня на природе, без офисов и дедлайнов — Живые дискуссии вместо скучных лекций в аудиториях — Soft skills, карьера и реальные боли индустрии — Нетворкинг, который действительно работает — Спорт, вечерние посиделки у костра и десятки видов акти…
💩8
#scala Error 500? Как вместо кодов получать подробные сведения обо всех ошибках сразу На нашем Хабре вышла новая статья! В ней Артем Корсаков, руководитель группы Scala-разработчиков в «Криптоните», разобрался с обработкой ошибок в библиотеке http4s на Scala 3. А еще он показал, как настроить декодирование запросов так, чтобы клиент получал не просто код 500 или 422 с общим сообщением, а сразу видел все проблемы: …
👍9🔥1
Скала байткод оптимайзер портировали на скала 3 :0 Читать тут https://www.scala-lang.org/blog/2026/03/23/porting-the-optimizer.html
👍4🌚2
Скала дед влетает в ИИ получаеца: https://arxiv.org/abs/2603.00991
🔥11😁7👍2
Pure functional HTTP APIs in Scala бесплатна! https://leanpub.com/pfhais
🔥6😍2❤1💯1
Приглашаем на Scala-встречу в Центральном университете Вас ждут 3 доклада от экспертов Центрального университета, Т-Банка и Яндекс Вертикалей, а еще обсуждения и разбор реальных кейсов в неформальной обстановке. ☑️ 18 марта в 19:00 📚 Москва, ул. Гашека, д. 7 стр. 1 Подробности о докладах и регистрация
👍10
Showing the 12 most recent of 15 posts we hold for @scala_channel_ru. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Scala Nishtyaki Channel” (@scala_channel_ru), 907 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/scala_channel_ru.
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.