Stop Treating CSS Container Queries Like Traditional Media Queries Despite broad browser support, container queries remain surprisingly underused and frequently misunderstood. Let’s look at how they differ from media queries, when to reach for each, and how container queries help reusable components respond naturally to the contexts in which they appear. - CSS - Tools - Techniques https://www.smashingmagazine.com/2…

Channel
Front End World
@front_end_first
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
25,950subscribers
-221 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001068453571 |
|---|---|
| Type | Channel |
| Username | @front_end_first |
| Description | New articles about Front End development. JS, CSS, React, Vue, Angular and others! Russian tech blog: @five_a_m Admin: @jem_jem |
| Created | Between 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/front_end_first |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 13:59 | 25,950 | -19 |
| 14 Sept 2026, 12:42 | 25,969 | -5 |
| 13 Sept 2026, 02:20 | 25,974 | -6 |
| 11 Sept 2026, 02:59 | 25,980 | -41 |
| 8 Sept 2026, 05:17 | 26,021 | -43 |
| 4 Sept 2026, 22:38 | 26,064 | -10 |
| 3 Sept 2026, 05:58 | 26,074 | -6 |
| 2 Sept 2026, 02:13 | 26,080 | -7 |
| 1 Sept 2026, 00:07 | 26,087 | +4 |
| 30 Aug 2026, 20:15 | 26,083 | +6 |
| 29 Aug 2026, 21:43 | 26,077 | -13 |
| 28 Aug 2026, 23:25 | 26,090 | -8 |
| 28 Aug 2026, 02:36 | 26,098 | -5 |
| 26 Aug 2026, 05:36 | 26,103 | -7 |
| 25 Aug 2026, 05:17 | 26,110 | -13 |
| 24 Aug 2026, 05:04 | 26,123 | -7 |
| 22 Aug 2026, 14:38 | 26,130 | -3 |
| 21 Aug 2026, 07:35 | 26,133 | -20 |
| 20 Aug 2026, 07:16 | 26,153 | -4 |
| 19 Aug 2026, 07:42 | 26,157 | first reading |
Engagement
106 posts held, back to 27 July 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 61 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.60%
- avg views ÷ 25,950 subscribers
- Avg views / post
- 673
- 38 posts measured
- Reaction rate
- 0.174%
- reactions ÷ views · ER floor
- Posts in window
- 38
- of 106 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 17 of 38 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 26 September 2026 |
|---|---|
| Posts held | 106 (27 July 2026 – 26 September 2026) |
| Views total | 25,590 |
| Reactions total | 22 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 10:20 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- ≈4,860
- Videos
- ≈1
- Links
- ≈5,960
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
71 reactions across 46 posts, in 11 distinct kinds. The most used accounts for 49.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 35 | 49.3% | |
| 👍 | 18 | 25.4% | |
| ❤🔥 | 5 | 7.04% | |
| 🔥 | 3 | 4.23% | |
| 😁 | 3 | 4.23% | |
| ⚡ | 2 | 2.82% | |
| 👎 | 1 | 1.41% | |
| 👏 | 1 | 1.41% | |
| 🤡 | 1 | 1.41% | |
| 🤣 | 1 | 1.41% | |
| 🥰 | 1 | 1.41% |
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 49 of the 106 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 71 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 106 most recent posts we hold, published 27 July 2026 to 26 September 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
Angular State Management: From Local Signals to NgRx SignalStore See Angular state management options in a real app so you can see why different solutions work better for different cases. https://www.telerik.com/blogs/angular-state-management-local-signals-ngrx-signalstore?via=dailydev
Angular Resource APIs Explained: Generating Signal-Based Service Proxies Angular Resource APIs introduce a declarative, Signal-driven approach to data fetching, eliminating much of the boilerplate traditionally associated w... https://abp.io/community/articles/angular-resource-apis-explained-generating-signalbased-service-proxies-ksup6l1n?via=dailydev#gsc.tab=0
React Activity: When A Render No Longer Guarantees an Effect Discover how React 19.2 Activity changes component lifecycles, Effects, state, and cleanup—and how to avoid hidden bugs in production. https://hackernoon.com/react-activity-when-a-render-no-longer-guarantees-an-effect
How to Build a Scalable SVG Icon System for Your Web App https://www.sitepoint.com/how-to-build-a-scalable-svg-icon-system-for-your-web-app/?via=dailydev
Remove start and end margins with the margin-trim property https://rachelandrew.co.uk/archives/2026/09/15/remove-start-and-end-margins-with-the-margin-trim-property/
👍1
Comparing Values With CSS progress() https://blog.master.dev/comparing-values-with-css-progress/
🤣1
Beyond Frontend and Backend: The Rise of the Agent Layer Agents deserve an architecture layer of their own rather than lumped into frontend or backend, since they don’t behave quite the same as people or programs. https://www.telerik.com/blogs/beyond-frontend-backend-rise-agent-layer
How to Build a Browser-Based File Integrity Checker with JavaScript https://www.sitepoint.com/how-to-build-a-browser-based-file-integrity-checker-with-javascript/?via=dailydev
Still: From Akira to Ink Wash, Building a Generative Garden in WebGPU A technical deep dive into Still, exploring how WebGPU, procedural systems, and Japanese art influences come together to create a living generative garden. https://tympanus.net/codrops/2026/09/09/still-from-akira-to-ink-wash-building-a-generative-garden-in-webgpu/
TanStack Markdown vs react-markdown: Which is better? Compare TanStack Markdown and react-markdown. Learn how their token stream vs. AST architectures impact React app builds. https://blog.logrocket.com/tanstack-markdown-vs-react-markdown/
WebGPU Compute Shaders for High-Throughput Syntax Highlighting https://www.sitepoint.com/webgpu-compute-shaders-for-high-throughput-syntax-highlighting/
Showing the 12 most recent of 106 posts we hold for @front_end_first. 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
Named by 2 registered channels — 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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@fedevelopment · 28,752#1
@webde · 31,910#2
@frontend_info · 5,298#3
@javascript · 31,123#4
@linuxgram · 72,668#5
@computer_science_and_programming · 139,806#6
@github_repos · 27,297#7
@front_end_dev · 25,875#8
@thedevs · 32,129#9
@ready_dot_code · 8,465#10
@webdev_trainings · 133,855#11
@frontend_trend · 19,106#12
@webdevcoursefree · 79,578#13
@javascript_courses · 55,698#14
@React_Training · 62,922#15
@frontendnoteschannel_ru · 31,430#16
@wwwdev · 1,758#17
@CodingNews · 23,118#18
@happywebdev · 15,107#19
@web_developerz · 1,597#20
@r_CoolGithubProjects · 4,410#21
@WebsiteDesignLearningGroup · 27,872#22
@github_repositories_bds · 10,771#23
@laravelnews · 7,508#24
@csstrickscom · 515#25
@TheKerVerse · 954#26
@web_dev_bds · 4,373#27
@itsfoss_official · 12,962#28
@chapidevtalks · 10,318#29
@Programming_experts · 67,682#30
@everythingaboutcode · 9,593#31
@threejsbybrunosimon · 5,937#32
@webb_dev · 8,299#33
@frontendchannels · 8,768#34
@LinuxMastery · 67,565#35
@C0DE_NET · 5,039#36
@MadeWithVueJs · 790#37
@fulljavascript2023 · 11,488#38
@Udemy4 · 251,721#39
@dev_useful_stuff · 2,199#40
@ProjectsWithSourceCode · 2,610#41
@indianhtmlweb · 11,604#42
@programmer_humor · 21,475#43
@SoftSkills101 · 35,363#44
@front_end_master · 4,442#45
@ieofficial · 65,952#46
@ProgrammingTip · 46,484#47
@codingmaster52 · 9,512#48
@udemy_free_courses_with_certi · 70,681#49
@programmerjokes · 106,959#50
@JavaScript_Trainings · 96,712#51
@linkedin_learning · 217,924#52
@remotejobss · 159,925#53
@LearnPython3 · 125,222#54
@seniorFront · 23,904#55
@hacker_news_feed · 29,771#56
@josad_software · 14,135#57
@frontendproglib · 20,930#58
@Dagmawi_Babi · 9,066#59
@web_stack · 4,131#60
@oyaya17 · 2,438#61
@ru_react_notes · 3,436#62
@Javascriptproo · 4,137#63
@sWebDev · 7,489#64
@we_use_js · 10,795#65
@web_design_templates · 3,984#66
@tproger_web · 22,429#67
@htmlshit · 14,434#68
@TechnologyBoxs · 25,031#69
@remote_frontend_jobs · 4,737#70
@udemyrip · 68,291#71
@room_js · 894#72
@science · 120,230#73
@Python53 · 50,715#74
@ml_world · 11,103#75
@forwebdev · 13,123#76
@Remote_Software_Developer_Jobs · 26,539#77
@githubtrending · 11,622#78
@react_tg · 16,279#79
@easy_javascript_ru · 17,721#80
@javascript_jobs_feed · 14,924#81
@FrontChapter · 3,380#82
@crackingthecodinginterview · 52,232#83
@senior_front · 19,323#84
@DeepDevs · 9,235#85
@Templates_html_css_js · 6,712#86
@remotejobshg · 33,019#87
@forfrontend · 13,450#88
@sql_databases · 70,599#89
@techguide · 41,573#90
Read from Telegram’s recommendation API, most recently 13 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@fedevelopment · 28,752
Telegram ranks this channel #1 of 88 here — alongside 87 others — read 9 September 2026
@webde · 31,910
Telegram ranks this channel #2 of 84 here — alongside 83 others — read 5 September 2026
@CodingNews · 23,118
Telegram ranks this channel #4 of 68 here — alongside 67 others — read 19 September 2026
@thedevs · 32,129
Telegram ranks this channel #4 of 82 here — alongside 81 others — read 5 September 2026
@javascript · 31,123
Telegram ranks this channel #6 of 76 here — alongside 75 others — read 6 September 2026
@github_repos · 27,297
Telegram ranks this channel #7 of 76 here — alongside 75 others — read 11 September 2026
@computer_science_and_programming · 139,806
Telegram ranks this channel #8 of 87 here — alongside 86 others — read 13 August 2026
@WebsiteDesignLearningGroup · 27,872
Telegram ranks this channel #9 of 63 here — alongside 62 others — read 10 September 2026
@ProgrammingTip · 46,484
Telegram ranks this channel #10 of 73 here — alongside 72 others — read 27 August 2026
@SoftSkills101 · 35,363
Telegram ranks this channel #12 of 59 here — alongside 58 others — read 2 September 2026
@React_Training · 62,922
Telegram ranks this channel #12 of 64 here — alongside 63 others — read 21 August 2026
@ieofficial · 65,952
Telegram ranks this channel #16 of 92 here — alongside 91 others — read 21 August 2026
@linuxgram · 72,668
Telegram ranks this channel #19 of 90 here — alongside 89 others — read 19 August 2026
@webdev_trainings · 133,855
Telegram ranks this channel #23 of 65 here — alongside 64 others — read 13 August 2026
@JavaScript_Trainings · 96,712
Telegram ranks this channel #28 of 68 here — alongside 67 others — read 16 August 2026
@techguide · 41,573
Telegram ranks this channel #31 of 76 here — alongside 75 others — read 29 August 2026
@MotivationBySS · 47,663
Telegram ranks this channel #33 of 78 here — alongside 77 others — read 26 August 2026
@flutterDev · 22,422
Telegram ranks this channel #34 of 87 here — alongside 86 others — read 20 September 2026
@Polity_Notes_Quiz_PDF_PSIR_MCQ · 75,229
Telegram ranks this channel #37 of 72 here — alongside 71 others — read 19 August 2026
@designwithrehana · 22,855
Telegram ranks this channel #41 of 77 here — alongside 76 others — read 19 September 2026
@webdevcoursefree · 79,578
Telegram ranks this channel #45 of 79 here — alongside 78 others — read 19 August 2026
@codehype · 23,545
Telegram ranks this channel #46 of 74 here — alongside 73 others — read 17 September 2026
@the_coding_wizard · 178,758
Telegram ranks this channel #51 of 89 here — alongside 88 others — read 12 August 2026
@relocateme · 34,269
Telegram ranks this channel #57 of 89 here — alongside 88 others — read 3 September 2026
This channel appears in 27 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Front End World” (@front_end_first), 25,950 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/front_end_first.
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.