Telegram RegisterThe public register of Telegram
Telegram profile photo for compilers

Channel

compilers

@langdev

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

234subscribers

+23 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002113856907
TypeChannel
Username@langdev
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/langdev

Topic

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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Growth

211234222.57 August 2026 — 211 subscribers8 August 2026 — 211 subscribers16 August 2026 — 222 subscribers24 August 2026 — 225 subscribers31 August 2026 — 229 subscribers9 September 2026 — 231 subscribers17 September 2026 — 234 subscribers7 August 202617 September 2026
7 measurements spanning 40 days, net +23. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 208–237 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 05:37234+3
9 Sept 2026, 18:39231+2
31 Aug 2026, 15:29229+4
24 Aug 2026, 06:29225+3
16 Aug 2026, 02:12222+11
8 Aug 2026, 11:02211no change
7 Aug 2026, 19:40211first reading

Engagement

20 posts held, back to 2 October 2025 — 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

135 reactions across 17 posts, in 2 distinct kinds. The most used accounts for 94.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤12894.8%
💘75.19%

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 18 of the 20 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 135 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 2 October 2025 to 7 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.

Recent posts

7 Aug 2026, 14:56 UTC72 views5 reactionsread 8 August 2026
Forwarded from @vchecraft

Нашёл отличный доклад по теме JIT-компиляции в Cpython. В докладе затрагиваются подробности имплементации JIT такие как уникальный механизм copy and patch компиляции и micro codes interpreter. Что же нам предвещает добавление JIT в коробочную версию cpython? Мы получим бесплатное ускорение всех наших программ и возрадуемся или всё не так просто? Давайте попробуем разобраться вместе. https://youtu.be/BiVEhI7wYS4?si=…

❤5

Signed Artyom

6 Aug 2026, 12:22 UTC236 views9 reactionsread 8 August 2026
Photo

😭Сегодня в нашем дискорде смотрели язык V (vlang.io). Помимо того, что компилятор допускает утечку при обычном hello world, так еще и проблемы из review 2023 года не были решены. Забавно, что автор изначально задумывал минималистичный язык, а по итогу мы имеем borrow checker, arena allocator, autofree, manual memory management, а также built-in orm и параллельный сборщик мусора! Интересно, что нужно добавить в V, чт…

❤9

Signed Artyom

2 Aug 2026, 07:18 UTC233 views5 reactionsread 8 August 2026

🔈Aya-Prover Интерактивная система, предназначенная для формализации теорий и написания программ с зависимыми типами. Система имеет блог, который содержит не только документацию языка, но и публикации авторов, которые проливают свет на внутреннее устройство проекта: https://www.aya-prover.org/pubs/. Если вам интересны Coq, Agda и подобные, то рекомендую ознакомиться и с Aya.

❤5

Signed Artyom

31 Jul 2026, 17:50 UTC281 views8 reactionsread 8 August 2026
Photo

🗑 Сборка мусора в Python Если вам было бы интересно узнать об устройстве сборки мусора в Python, то этот цикл статей точно для вас! В статьях подробно описываются внутренние алгоритмы сборщика мусора Python понятным языком и с примерами. Рекомендуем к прочтению! https://habr.com/ru/articles/940642/ https://habr.com/ru/articles/951250/ https://habr.com/ru/articles/986784/ https://habr.com/ru/articles/992026/ #Стать…

❤8

Signed Вячеслав

31 Jul 2026, 10:53 UTC490 views12 reactionsread 8 August 2026

🤩ИТОГИ Пришло время подводить итоги langjam (plic). Первое место забирает язык программирования Dola. Просьба победителя связаться с @k1ngmang, чтобы забрать свой приз. Ну а вот какие языки попали в первую пятерку: 1) dola 2) graft 3) ftorlisp 4) ygvm 5) py++

❤12

Signed Artyom

20 Jul 2026, 04:01 UTC393 views8 reactionsread 8 August 2026

👨‍💻🐨 До конца приёма работ на langjam осталось 3 часа. 10:00 — это последнее время, когда можно сделать пулл реквест.

❤8

Signed Вячеслав

17 Jul 2026, 16:28 UTC355 views9 reactionsread 8 August 2026
Photo

😀Напоминаю про дедлайн. 20 июля 10:00 - это последнее время, когда можно сделать пулл реквест. Рассматриваться будут только те языки, которые успели к этому времени

❤9

Signed Artyom

13 Jul 2026, 09:18 UTC863 views6 reactionsread 8 August 2026

Когда-то мы планировали открыть дискорд сервер для нашего сообщества, так вот, наступило время это сделать! Будем рады видеть вас здесь: https://discord.gg/ANUc56vnKd

❤6

Signed Вячеслав

12 Jul 2026, 06:26 UTCviews —

compilers dev pinned «Поздравляю вас с началом лангджема. Тема, условия и инструкция по сдаче проекта находится в репозитории: https://github.com/langdev-jam/plic Кратко напоминаю об условиях: вы пишите свой язык программирования (компилятор/интерпретатор) на тематику, которая…»

12 Jul 2026, 06:26 UTC988 views9 reactionsread 8 August 2026

Поздравляю вас с началом лангджема. Тема, условия и инструкция по сдаче проекта находится в репозитории: https://github.com/langdev-jam/plic Кратко напоминаю об условиях: вы пишите свой язык программирования (компилятор/интерпретатор) на тематику, которая определена в репозитории. Следуя инструкции выкладываете свой проект и забираете приз Приз: 5000 RUB Дата окончания: 20 июля

❤9

Signed Artyom

5 Jul 2026, 12:49 UTC926 views13 reactionsread 8 August 2026
Photo

ДАТА НАЧАЛА ЛАНГДЖЕМА 12 июля будут опубликованы условия мероприятия. Приз: 5000 рублей (~$65). Кратко напомню о мероприятии: участникам даётся определенный период времени, в течении которого они должны будут сделать язык программирования, который соответствует условиям. На выбор может быть несколько идей, выбираете ту, которая нравится больше всего и делаете яп

❤13

Signed Artyom

22 May 2026, 06:10 UTC690 views10 reactionsread 8 August 2026

👨‍💻 LANGJAM Некоторое время назад мы объявили о мероприятии, где участникам предлагается написать свой язык программирования, соответствующий выбранной теме, которая будет определена во время начала конкурса. В прошлом посте мы обещали опубликовать ресурсы для тех, кто ни разу не писал свой язык программирования, но очень хотел бы поучаствовать. Так вот, мы возвращаемся со списком ресурсов! 🌟Ресурсы: 1. Книга: Cra…

❤10

Signed Вячеслав

Showing the 12 most recent of 20 posts we hold for @langdev. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

26 Mar 2026, 07:13 UTCAnonymous Poll98 voters

Какой контент вы бы хотели тут видеть?

  1. Оптимизации51%
  2. Теория типов47%
  3. Обзор других языков44%
  4. Фронтенд компиляторов41%
  5. Бекенд компиляторов56%

The shares total 239%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 2 October 2025 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“compilers” (@langdev), 234 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/langdev.

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.