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 11 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 the other topics.
Growth
45 measurements spanning 87 days, net -381. 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 9,876–10,371 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)
Subscribers
Change
1 Nov 2026, 03:16
9,933
-18
29 Oct 2026, 07:19
9,951
-12
26 Oct 2026, 15:20
9,963
-12
24 Oct 2026, 01:08
9,975
-14
21 Oct 2026, 11:19
9,989
-10
18 Oct 2026, 03:57
9,999
-5
17 Oct 2026, 01:29
10,004
-1
16 Oct 2026, 01:56
10,005
-8
15 Oct 2026, 04:11
10,013
-5
14 Oct 2026, 01:27
10,018
-12
11 Oct 2026, 04:18
10,030
-24
7 Oct 2026, 01:20
10,054
-18
2 Oct 2026, 04:38
10,072
-54
18 Sept 2026, 11:17
10,126
-14
16 Sept 2026, 03:41
10,140
-5
14 Sept 2026, 13:41
10,145
-8
12 Sept 2026, 23:18
10,153
-6
11 Sept 2026, 02:17
10,159
-10
8 Sept 2026, 02:39
10,169
-17
4 Sept 2026, 20:56
10,186
first reading
Engagement
20 posts held, back to 9 September 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 37 pages 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 11 March 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
7m 21s
Average length
3m 41s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
338 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 40.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
137
40.5%
🔥
58
17.2%
❤
54
16.0%
🤯
29
8.58%
🍾
16
4.73%
🤣
15
4.44%
👏
14
4.14%
🥰
14
4.14%
🤔
1
0.296%
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 20 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 338 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 9 September 2023 to 11 March 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🔥🌎 TypeScript Revolution: Compiler Rewritten in Go for MIND-BLOWING Performance! 😲
Get ready for some EARTH-SHATTERING EXCITEMENT! 😉 The TypeScript team has just dropped a bombshell: they've completely rewritten the compiler in Go, and the results are nothing short of ASTOUNDING! 🤯
🎉 Here are the jaw-dropping highlights:
🔹 *10x FASTER TYPE-CHECKING* 🔥: Say goodbye to slow compilation times and hello to lightning-f…
JSR - the JavaScript Registry - is now available in public beta.
🛠️ TypeScript first, ESM only
🌐 Works across runtimes (Node, Deno, Bun, workerd and more) and alongside npm/yarn/pnpm
🤗 Free and open source
Read about it on the Deno blog:
https://deno.com/blog/jsr_open_beta
📢 LLRT (Low Latency Runtime) is a new JS runtime from Amazon ✨
⚡ Designed for fast Serverless startup time
🦀 Written in Rust
💨 Embeds the QuickJS engine written in C
💡 Lightweight (~3MB)
🧪 Experimental!
https://github.com/awslabs/llrt
A quick and fun guide to setup a template of
#SolidJS + #TailwindCSS + #Tauri
and develop for desktop and mobile simultaneously...
🤯🤯🤯
🔥 Follow @javascriptdaily 🔥
https://www.youtube.com/watch?v=W539_PP4Y98
An interesting take on Frontend in 2023 and also some predictions in the article by @Jamie
https://buttondown.email/whatever_jamie/archive/frontend-predictions-for-2024
#threejs
A quick example of how one can "synchronize" a 3d scene across multiple windows using three.js and localStorage
🔥 Follow @javascriptdaily 🔥
Repo:
https://github.com/bgstaal/multipleWindow3dScene
Announcing WinterJS
The most performant JavaScript Service Workers server thanks to Rust and SpiderMonkey.
WinterJS is a JavaScript Service Workers server written in Rust, that uses the SpiderMonkey runtime to execute JavaScript (the same runtime that Firefox uses). We chose to follow the WinterCG specification to aim for maximum compatibility with other services such as Cloudflare Workers, Deno Deploy and Vercel (…
Exciting news - roadmap editor is live 🥳
You can now create custom roadmaps, add content and resources, share them with your friends, teams or publicly.
This is a huge next step for us and we are so excited about what's coming next!
An interesting feature addition to https://roadmap.sh/
A good roadmap to bookmark: https://roadmap.sh/javascript
🔥 Follow @javascriptdaily 🔥
https://x.com/kamrify/status/17082931626…
Tauri 1.5.0 Released 🎉🎊🎉🎊
- Bun support
- Notarytool
- Code signing improvements
- macOS frameworks
- Mixed content on Windows
https://beta.tauri.app/blog/tauri-1-5/
👍5❤2
Showing the 12 most recent of 20 posts we hold for @javascriptdaily. 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.
Mentions
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.
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 1 November 2026 — this
entry's latest reading, not the date you are reading this.
“JavaScript Daily” (@javascriptdaily), 9,933 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/javascriptdaily.
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.