Channel
@js_spec
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
48subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002144934790 |
|---|---|
| Type | Channel |
| Username | @js_spec |
| Created | 11 March 2024 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/js_spec |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 13:03 | 48 | no change |
| 7 Aug 2026, 12:59 | 48 | first reading |
10 posts held, back to 11 March 2024 — 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 pageof 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 10 posts for this entry, the most recent from 6 May 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
117 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 34.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 40 | 34.2% | |
| 🤮 | 35 | 29.9% | |
| 😁 | 15 | 12.8% | |
| 🤡 | 12 | 10.3% | |
| 🔥 | 8 | 6.84% | |
| 🥰 | 3 | 2.56% | |
| ❤ | 2 | 1.71% | |
| 🆒 | 1 | 0.855% | |
| 🤩 | 1 | 0.855% |
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 9 of the 10 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 117reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 11 March 2024 to 6 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
React 19 Beta Релиза ждали 2+ года, что имеем: 1) Серверные компоненты: спорно, т.к. они заставляют думать еще больше, а значит ухудшают DX(кстати SEO они все еще не помогают) 2) Формы: круто, но явно не переплюнет рхф или же superforms из свелта(там глубокая интеграция форм со свелткитовскими форм экшенами, из-за чего и без того ахуенный перф еще лучше) 3) use: крутой хук, особенно интеграция с саспенсом. Тепе…
👍9🥰3
Photo, posted without a caption
😁14👍2
Deffector moments 😡 — Не умеет в динамику(решается с помощью кей-вэлью) — Высокий порог входа Ну, судя по тому что минусов у него меньше чем у редакса, жупшука и танстака, он лучше чем они 🥹
🔥5🤮3🤩1
MUI moments — Платные компоненты — Плохие дефолтные стили — Стили переопределяются через жопу — Тяжело интегрировать с другими либами — Плохой DX(не имхо, вытекает из пунктов 2 - 4) — Большой бандлсайз(стандартный для монолитной юай либы) — Низкий перф(использует много дом узлов)
👍8🤮5
Redux moments - Монолитность с большой буквы - Неявная связанность частей состояния - Бешеный бойлерплейт (даже с обвязками его много) - Полная беспомощность без оберток/фабрик/тулзов сбоку - Плохой DX для кейсов сложнее палки - Отсутствие компьютедов - Отсутствие возможности делать служебные свойства без апдейта всего стора - Каждый апдейт вызывает всех подписчиков (“мемоизированные” селекторы не бесплатные) - Монс…
👍6🤮5😁1
React(без всяких еффекторов\реатомов, это уже другой мир) moments — Не реактивен(в привычном понимании реактивности) - реакт скорее "планирует" изменения, а не реагирует на месте — Нет компонент ивентс - во вью\свелте на них можно делегировать процентов 30% работы с локальными стейтами(решается инструментами а-ля еффектор с их ивентами, но опять же: хотелось бы видеть нативное решение) — Нет слотов - приходится пр…
👍9🤡8🤮5
Зато редгрупп одобряет
👍5🤮5
Tanstack Query moments — Шаг влево-вправо от простейших кейсов отправки данных - нужно уже мутить свои костыли — Наглухо прибит к реакту (если что вынести в хук - это не решение), требуется следить за ререндерами, логикой в хуках и прочим — Отсутствие решения для клиентских стейтов(как в аполло например, или в farfetched) - приходится либо ебашить свою костыляку либо прикручивать какой-нибудь зустанд — Ебануто ог…
🤮6🤡4🔥3
Zustand moments - Абсолютно тупой стм, подходит только для тонких клиентов с простыми стейтами без цепочек сайд еффектов - Очень плохо работает с SSR - Вместе с зустандом придётся тащить что-то для серверного стейта -> больше бандлсайз, хуже перф - Не выводит типы, нужно явно указывать дженериком, увеличивая кодовую базу в разы
🤮6❤2👍1🆒1
Channel created
Showing the 10 most recent of 10 posts we hold for @js_spec. 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 — 780,286 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“нинавижу реакт” (@js_spec), 48 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/js_spec.
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.