Не хочу ничего более обсуждать. Сегодня на улице праздник!
😁57👍20🔥7❤🔥5🎉2🤡2🤝1🤯1

Channel
@vueist
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,197subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001996418937 |
|---|---|
| Type | Channel |
| Username | @vueist |
| Created | Between 1 October 2023 and 30 April 2024— 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/vueist |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 17:14 | 1,197 | -1 |
| 10 Aug 2026, 04:01 | 1,198 | +1 |
| 7 Aug 2026, 12:40 | 1,197 | no change |
| 6 Aug 2026, 22:02 | 1,197 | first reading |
18 posts held, back to 20 December 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 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 18 posts for this entry, the most recent from 2 June 2026. An engagement rate over an empty window would be a number about nothing.
918 reactions across 17 posts, in 21 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 407 | 44.3% | |
| 😁 | 138 | 15.0% | |
| 👍 | 135 | 14.7% | |
| ❤ | 112 | 12.2% | |
| 🤪 | 23 | 2.51% | |
| ❤🔥 | 21 | 2.29% | |
| 🎄 | 19 | 2.07% | |
| 🍾 | 13 | 1.42% | |
| 🤡 | 13 | 1.42% | |
| 🤝 | 11 | 1.20% | |
| 🍌 | 5 | 0.545% | |
| 🐳 | 5 | 0.545% | |
| 🥰 | 4 | 0.436% | |
| ☃ | 3 | 0.327% | |
| 🎉 | 2 | 0.218% | |
| 👏 | 2 | 0.218% | |
| 💩 | 1 | 0.109% | |
| 😍 | 1 | 0.109% | |
| 😢 | 1 | 0.109% | |
| 🤬 | 1 | 0.109% | |
| 1 further kind | 1 | 0.109% |
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 17 of the 18 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 918reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 20 December 2025 to 2 June 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.
Не хочу ничего более обсуждать. Сегодня на улице праздник!
😁57👍20🔥7❤🔥5🎉2🤡2🤝1🤯1
Гайд по Vue в 2026 Актуализируем свои проекты с последними тенденциями и мощностями. Обговорим весь стек. 1 шаблоны показали свою неэффективность используйте нечто иное - язык <template lang="pug">: позволит эффективнее использовать переменные в шаблонах, делать преиспользуемые части без костылей и сильно лаконичнее - использовать jsx: аналогично тому что выше, но вы можете улучшить экспириенс с помощью jsx-directi…
😁64🤪23🤡11🔥4🤝2❤1👍1🤬1
Порция RFC Видимо под влиянием анонса Solid 2 один из членов кор тимы vue (ubugeeei) решил накидать своего вижена какие фичи неплохо было бы видеть во vue дальше 1. RFC: Composed Async текущий Suspense завис в эксперементале на долгие годы. И по факту он прижился только в кишках Nuxt остальным же он оказался мало полезен (у Vue сейчас есть поддержка асинхронного setup (который отрабатывает лишь 1 раз) но нет асинхр…
👍21🔥7🤝3❤2
Мы дождались. Vue-ответ на современные вызовы (Tanstack Query) вышел в релиз: Pinia Colada! Создано автором Pinia и главный мйнтйнером Vue Router Posva Что дает? управление асинхронными ресурсами и кэшем поверх pinia В чем отличие от TanstackQuery? То что pinia colada построена поверх системы реактивности Vue и будет чуть лучше интегрироваться с экосистемой (например data loaders внутри Vue Router). В остальном API…
👍44🔥21
Posted without readable text
Ну что, ждем официальный порт Lynx (альтернатива react-native, работает по принципам схожим с react-native, а не WebView-based) под Vue? Твит от главы разработки Lynx PS. Есть народные попытки портов от автора Vue Vine для Vue Vine другая попытка (есть даже WIP PR в сам Lynx)
🔥43👍3❤🔥1💩1
Мне прислали вопрос по моему докладу: почему нежелательно использовать классы вместо компосаблов. Тема на самом деле куда обширнее чем кажется на первый взгляд, Именно поэтому я добавил ее в блок "потенциальный доклад по теме", Тут будет моя адаптация ответа. Так как композаблы сами в себе альтернатива ООП заточенная конкретно под нужды Vue. Они уже используют фичи соответствующие потребностям и отсекают вещи котор…
👍32🔥12❤2
#ТяжелыйПонедельник #видеозаписи Публикуем новую видеозапись выступления: Денис Чернов — Созвездия композаблов 😉 YouTube | 📺 VK Видео
❤30🔥18❤🔥5😍1
Вышел мой доклад по Vue composables где я попытался собрать практики использования композаблов по Vue в одном месте исходники на презу и сама преза
🔥23👍3
Вью роутер 5 вышел! Подробнее я писал уже выше. Гайд по миграции (если вы были на 4ой версии и не хотите файловый роутинг. то вам хвтит просто обновления, никаких ломающих изменений) Наиболее интересной частью мажора для меня явлется Data Loader-ы (experimental) Ну и нам сразу анонсировали, что стоит ждать 6-ого релиза
🔥43🍌5❤2
Слияние роутеров Вот такой вот мерж реквест вышел. Если кратко, то сейчас происходит процесс слияния unplugin-vue-router и vue-router. Что в этом интересного? unplugin-vue-router был неофициальным решением по отношению ко vue, но от самого автора и главногомейнтейнера vue-router. Изначально unplugin-vue-router давал возможность использовать файловый роутинг (да тот самый что в Nuxt) для vue-router-а. В последствии …
🔥29👍3❤🔥1😢1
Sticker, posted without a caption
❤31🍾13😁6🎄5🥰4☃3❤🔥1
Showing the 12 most recent of 18 posts we hold for @vueist. 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 — 884,831 of 1,189,255entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@vueist named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Vueist” (@vueist), 1,197 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/vueist.
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.