Computer Science and Programming
前往频道在 Telegram
Channel specialized for advanced topics of: * Artificial intelligence, * Machine Learning, * Deep Learning, * Computer Vision, * Data Science * Python Admin: @otchebuch Memes: @memes_programming Ads: @Source_Ads, https://telega.io/c/computer_science
显示更多
网络:📈 Telegram 频道 Computer Science and Programming 的分析概览
频道 Computer Science and Programming (@computer_science_and_programming) 英语 语言赛道中的 是活跃参与者。目前社区聚集了 140 655 名订阅者，在 技术与应用 类别中位列第 810，并在 意大利 地区排名第 88 位。
📊 受众指标与增长动态
自 невідомо 创建以来，项目保持高速增长，吸引了 140 655 名订阅者。
根据 25 八月, 2026 的最新数据，频道保持稳定运转。过去 30 天订阅人数变化为 -760，过去 24 小时变化为 -64，整体触达仍然可观。
- 认证状态： 未认证
- 互动率 (ER)： 平均受众互动率为 7.67%。内容发布后 24 小时内通常能获得 1.74% 的反应，占订阅者总量。
- 帖子覆盖： 每篇帖子平均可获得 10 784 次浏览，首日通常累积 2 454 次浏览。
- 互动与反馈： 受众积极参与，单帖平均反应数为 15。
- 主题关注点： 内容集中在 sellerflash, github, developer, pricing, waybienad 等核心主题上。
📝 描述与内容策略
作者将该频道定位为表达主观观点的平台：
“Channel specialized for advanced topics of:
* Artificial intelligence,
* Machine Learning,
* Deep Learning,
* Computer Vision,
* Data Science
* Python
Admin: @otchebuch
Memes: @memes_programming
Ads: @Source_Ads,
https://telega.io/c/computer_sc...”
凭借高频更新（最新数据采集于 26 八月, 2026），频道始终保持新鲜度与高覆盖。分析显示受众积极互动，使其成为 技术与应用 类别中的关键影响点。
140 655
订阅者
-6424 小时
-2217 天
-76030 天
数据加载中...
相似频道
标签云
进出提及
---
---
---
---
---
---
吸引订阅者
八月 '26
八月 '26
+207
在17个频道中
七月 '26
+177
在21个频道中
Get PRO
六月 '26
+84
在10个频道中
Get PRO
五月 '26
+175
在19个频道中
Get PRO
四月 '26
+164
在20个频道中
Get PRO
三月 '26
+141
在13个频道中
Get PRO
二月 '26
+741
在37个频道中
Get PRO
一月 '26
+1 005
在40个频道中
Get PRO
十二月 '25
+977
在63个频道中
Get PRO
十一月 '25
+1 306
在59个频道中
Get PRO
十月 '25
+593
在20个频道中
Get PRO
九月 '25
+80
在1个频道中
Get PRO
八月 '25
+403
在14个频道中
Get PRO
七月 '25
+738
在8个频道中
Get PRO
六月 '25
+486
在88个频道中
Get PRO
五月 '25
+439
在10个频道中
Get PRO
四月 '25
+757
在3个频道中
Get PRO
三月 '25
+946
在7个频道中
Get PRO
二月 '25
+677
在2个频道中
Get PRO
一月 '25
+236
在4个频道中
Get PRO
十二月 '24
+543
在3个频道中
Get PRO
十一月 '24
+401
在12个频道中
Get PRO
十月 '24
+192
在1个频道中
Get PRO
九月 '24
+1 371
在0个频道中
Get PRO
八月 '24
+1 512
在4个频道中
Get PRO
七月 '24
+1 612
在1个频道中
Get PRO
六月 '24
+2 332
在15个频道中
Get PRO
五月 '24
+2 580
在7个频道中
Get PRO
四月 '24
+1 512
在17个频道中
Get PRO
三月 '24
+1 889
在15个频道中
Get PRO
二月 '24
+1 838
在86个频道中
Get PRO
一月 '24
+1 916
在18个频道中
Get PRO
十二月 '23
+2 106
在25个频道中
Get PRO
十一月 '23
+1 851
在9个频道中
Get PRO
十月 '23
+3 196
在20个频道中
Get PRO
九月 '23
+2 927
在0个频道中
Get PRO
八月 '23
+1 557
在0个频道中
Get PRO
七月 '23
+1 520
在0个频道中
Get PRO
六月 '23
+1 005
在0个频道中
Get PRO
五月 '23
+2 425
在0个频道中
Get PRO
四月 '23
+2 588
在0个频道中
Get PRO
三月 '23
+1 970
在0个频道中
Get PRO
二月 '23
+2 358
在0个频道中
Get PRO
一月 '23
+2 768
在0个频道中
Get PRO
十二月 '22
+3 387
在0个频道中
Get PRO
十一月 '22
+2 987
在0个频道中
Get PRO
十月 '22
+2 147
在0个频道中
Get PRO
九月 '22
+2 432
在0个频道中
Get PRO
八月 '22
+1 917
在0个频道中
Get PRO
七月 '22
+1 114
在0个频道中
Get PRO
六月 '22
+1 893
在0个频道中
Get PRO
五月 '22
+1 644
在0个频道中
Get PRO
四月 '22
+1 508
在0个频道中
Get PRO
三月 '22
+3 733
在0个频道中
Get PRO
二月 '22
+5 595
在0个频道中
Get PRO
一月 '22
+2 935
在0个频道中
Get PRO
十二月 '21
+2 333
在0个频道中
Get PRO
十一月 '21
+2 036
在0个频道中
Get PRO
十月 '21
+2 636
在0个频道中
Get PRO
九月 '21
+1 072
在0个频道中
Get PRO
八月 '21
+2 016
在0个频道中
Get PRO
七月 '21
+1 938
在0个频道中
Get PRO
六月 '21
+2 234
在0个频道中
Get PRO
五月 '21
+2 783
在0个频道中
Get PRO
四月 '21
+2 166
在0个频道中
Get PRO
三月 '21
+3 468
在0个频道中
Get PRO
二月 '21
+3 071
在0个频道中
Get PRO
一月 '21
+4 001
在0个频道中
Get PRO
十二月 '20
+78 737
在0个频道中
| 日期 | 订阅者增长 | 提及 | 频道 | |
| 26 八月 | +9 | |||
| 25 八月 | +2 | |||
| 24 八月 | 0 | |||
| 23 八月 | +9 | |||
| 22 八月 | +18 | |||
| 21 八月 | +2 | |||
| 20 八月 | +6 | |||
| 19 八月 | +20 | |||
| 18 八月 | +5 | |||
| 17 八月 | +3 | |||
| 16 八月 | +3 | |||
| 15 八月 | +26 | |||
| 14 八月 | +28 | |||
| 13 八月 | +10 | |||
| 12 八月 | +4 | |||
| 11 八月 | +2 | |||
| 10 八月 | +3 | |||
| 09 八月 | +1 | |||
| 08 八月 | 0 | |||
| 07 八月 | +12 | |||
| 06 八月 | +6 | |||
| 05 八月 | +30 | |||
| 04 八月 | 0 | |||
| 03 八月 | +2 | |||
| 02 八月 | +6 | |||
| 01 八月 | 0 |
频道帖子
Introducing G#: A Go-like language for .NET
G# is a new open-source, Go-inspired programming language that compiles to .NET, targeting systems programming and mobile applications while interoperating with existing .NET libraries and NuGet packages. It supports .NET 8 through 10 (10 preferred), offers a VS Code extension with language server support, and blends .NET-style async/await with Go-like fire-and-forget concurrency and channels via an optional extensions package. The language uses packages, funcs, structs and classes, and features like if let and for in for concise null checks and iteration. Beyond general development, it's positioned as an educational language and a lightweight candidate for WebAssembly and Hyperlight microVM scenarios, useful for developers moving from Swift or Kotlin into the .NET ecosystem.
| 2 |  VoidZero Releases Vite+ Beta: A Unified Web Toolchain Behind a Single Command
VoidZero, the company behind Vite founder Evan You, has launched the beta of Vite+, a unified web toolchain accessible through a single vp command. It bundles Vite, Vitest, Rolldown, tsdown, Oxlint and Oxfmt with a built-in task runner, offering commands like vp dev, vp check, vp test, vp build, vp pack and vp run. Since its alpha, the team has merged over 500 pull requests, expanded vp migrate coverage, and added enterprise features like organisation templates. Over 1,300 public repositories already use it, including Dify, BlockNote and Cloudflare's vinext. Reception on Hacker News was largely positive, though a widely shared GitHub write-up by Jared Wilcurt criticized its vp env Node version manager and warned about ecosystem lock-in and heavy reliance on Rust rewrites of existing tools. | 5 030 |
| 3 |  How MongoDB Reduced PR Review Times with GitDailie
A case study describes how MongoDB adopted GitDailies, a GitHub PR alerting and metrics tool, to help engineering teams meet PR review SLAs. Customizable alerts, Slack integration, and personalized dashboards replaced ineffective existing alerting, reportedly cutting review times by up to 54% for one team and over 28% for nearly half the teams involved. | 7 159 |
| 4 |  Stop burning tokens on code review
An engineering leader shares why AI-based code review tools like Cursor's BugBot and custom Claude code review skills became too slow, noisy, and expensive (hitting $1000/day in one case) for a team producing thousands of PRs a quarter. The fix that worked: converting team-specific coding rules from markdown guidelines into custom linters, which run in seconds, are deterministic, can run in-editor and on pre-commit hooks, and stop agents from ever pushing bad code. Several example custom lint rules are shared, covering design system consistency, logging, testing conventions, and prose quality. | 8 212 |
| 5 |  Does anyone run Postgres without PgBouncer?
Almost every notable managed Postgres provider bundles a connection pooler like PgBouncer, according to a survey of major providers including AWS RDS, Azure, Google Cloud SQL, Supabase, Neon, DigitalOcean, and others. Only IBM Cloud and Oracle OCI lack a managed pooling option, and both are dismissed as unlikely choices outside enterprise sales cycles. The piece argues connection pooling is effectively a mandatory add-on because Postgres itself handles many connections poorly, and contrasts this with MySQL and MongoDB, which don't require a bolted-on pooler. The wasted effort of every provider building homegrown pooling setups and every user having to learn PgBouncer's quirks (like the lack of LISTEN/NOTIFY support) is framed as evidence that native connection pooling in Postgres itself would be a high-impact improvement. | 9 778 |
| 6 |  WebSocket vs SSE vs Long Polling: The Real Cost of 1,000 Events
A hands-on benchmark built with a Node harness and a byte-counting TCP proxy measures the real wire cost of WebSocket, SSE, and long polling delivering 1,000 events. WebSocket used 119,692 bytes, SSE 131,596 (10% more), and HTTP/1.1 long polling 884,698 bytes (7.4x), mostly re-sent headers. On HTTP/2, long polling drops to 182,475 bytes (1.56x payload). Latency differences at low event rates were under 0.3ms across all three; long polling only degrades when events arrive faster than a round trip. Server memory for 500 idle connections favored WebSocket (6.2-6.7MB) over SSE (11MB) and long polling (10.3-10.9MB). Practical failure modes covered include idle timeouts, proxy buffering, and the six-connections-per-origin HTTP/1.1 cap on SSE. The recommendation: build SSE first for server-to-client feeds, move to WebSocket only when upstream or binary data is needed. | 9 517 |
| 7 |  Dark mode toggles: two states are enough • Lea Verou
(Light, Dark, System). The core argument is that users only seek out theme toggles when something is wrong — not to preemptively express intent — making the 'System' state irrelevant at the moment of interaction. Tri-state toggles expose the underlying data model rather than aligning with actual user goals, adding cognitive load and UI friction for an extremely rare use case. A well-implemented two-state toggle can still represent all three underlying states: the first click overrides to the opposite of the current resolved value, and the second click removes the override and returns to system default. Common mistakes include storing a value that matches the system preference (silently pinning the theme) or removing overrides when the OS preference changes. Exceptions where tri-state controls are appropriate include dedicated settings panels and sites that implement meaningfully different color schemes depending on the OS setting. | 10 079 |
| 8 |  No Index GroupBy Optimization
Dolt and Doltgres were using a secondary index for GROUP BY queries even when a full table scan would be faster. By analyzing EXPLAIN output and flame graphs, the team discovered that when a filter selects more than ~50% of rows, the secondary index lookup overhead outweighs its benefits. They added heuristics to the query coster: secondary indexes are only preferred when they select fewer than 25% of rows, while primary keys and covering indexes are always preferred. Using existing statistics histograms to estimate filter selectivity, this reduced groupby_scan latency by 57% on Dolt (144ms → 62ms) and 44% on Doltgres (147ms → 83ms), making Dolt faster than MySQL on this benchmark. | 9 988 |
| 9 |  DuckDuckGo "Normal F**king Sunglasses" Sold Out In Under a Week
DuckDuckGo partnered with sunglasses brand Knockaround to release "Normal F**king Sunglasses" — a satirical product mocking AI-powered smart glasses. The glasses have no camera, microphone, AI, battery, or electronics of any kind. They sold out in under a week. The collaboration is a commentary on growing surveillance concerns around AI glasses, particularly following Meta's use of Ray-Ban Meta smart glasses footage to train its AI systems and the June 2026 launch of Meta Glasses. | 11 649 |
| 10 |  What's new in PHP 8.6
PHP 8.6, scheduled for release on November 19, 2026, introduces several notable features: partial function application (PFA) for prefilling closure parameters, readonly property defaults (now allowed when implementing interfaces with property hooks), a new low-level Polling API for I/O multiplexing with epoll/WSAPoll backends, a built-in clamp() function, new isReadable/isWriteable reflection methods, function parameter doc comments via ReflectionParameter::getDocComment(), a SortDirection enum, debuggable enums via __debugInfo(), and improved session security defaults (HttpOnly, SameSite=Lax). The release also includes a large set of deprecations covering legacy functions (is_double, is_integer, is_long, doubleval, strcoll, metaphone, spl_classes, spl_object_hash), ArrayIterator methods, SplFileObject CSV methods, returning from finally blocks and constructors/destructors, and reserving keywords like let, is, and namespace for future syntax. | 13 553 |
| 11 |  Retiring the Copilot Billing Preview app
GitHub has retired the Copilot Billing Preview app. Copilot spend can now be managed directly in GitHub billing settings, which offers a more complete view including user-level budgets, cost centers, and usage pool allocation. Users can view AI usage, set spending budgets, access user-level budget controls for organizations and enterprises, and pull raw usage data via usage reports and the billing API. | 12 682 |
| 12 |  Substack writers, you need a website
Writers who rely on Substack as their primary digital home are making a strategic mistake. Substack and similar platforms are distribution tools, not permanent homes — when you build on someone else's platform, you're a tenant, not an owner. The POSSE model (Publish on your Own Site, Syndicate Elsewhere) offers a better approach: publish first to a domain you own and control, then use platforms like Substack purely as distribution channels. John Scalzi's 28-year independent blog is cited as a model of digital sovereignty. Platform algorithms favor dominant narratives, terms can change overnight, and content can be lost — owning your domain protects your long-term visibility and creative independence. | 15 789 |
| 13 |  The Disappearing Senior: AI and Entry Level Jobs
AI is eliminating entry-level developer work, but there's a less-discussed second effect: senior engineers are quietly losing their skills by only approving AI-generated output rather than doing the work themselves. The 'reasoning muscle' atrophies when judgment is never exercised. Meanwhile, no new seniors are being produced because the junior work that used to forge them is gone. Practical countermeasures include deliberately doing one thing the hard way each week, asking AI to defend its choices rather than just accepting answers, keeping a log of AI errors, and giving juniors the 'boring' work instead of offloading it to machines. No systemic fix is coming — individual engineers must maintain their own skills deliberately. | 14 629 |
| 14 |  CVE-2026-59328: Cross-Site Scripting in Eclipse Spring Boot Starter Wizard Dependency Tooltips
A CVE advisory (CVE-2026-59328) has been published for a Cross-Site Scripting (XSS) vulnerability found in the Eclipse Spring Boot Starter Wizard's dependency tooltips. The advisory is hosted on spring.io and relates to the Eclipse IDE plugin used for Spring Boot project setup. | 13 794 |
| 15 |  Announcing DuckDB 1.5.5
DuckDB 1.5.5 has been released as the sixth patch in the 1.5 (Variegata) line. The release includes bugfixes, performance improvements, correctness fixes, crash and internal error resolutions, and security patches. Full release notes are available on GitHub, with v2.0.0 expected in the | 13 364 |
| 16 | Hello everyone some of you may not know but now we started to expand to WhatsApp and we are inviting you to join our WhatsApp channel link here 👇👇👇👇👇
WhatsApp Computer Science and Technology
We welcome you all to be part of this family | 17 731 |
| 17 |  How I Learned to Structure React Projects Around Change, Not Folders
Technical folder structures (components, hooks, services, utils) make React repos easy to browse but hard to change, because a single feature's logic is scattered across unrelated directories. The key insight is organizing code around ownership of change rather than file type. This means colocating a feature's components, state, validation, API calls, and business rules under one feature directory. State placement should reflect lifecycle and source of truth, not convenience. Business rules belong near the feature that owns them, not in generic utils. Shared code should only be extracted when callers truly share the same meaning and change together. Finally, dependency direction matters: features should depend on stable shared primitives, not each other's internals. The real test of an architecture is how confidently a developer can locate the owner of the next change. | 18 617 |
| 18 |  Locally great, globally drifting
An evaluation of AI-generated frontend code in a real product reveals a recurring pattern: AI performs well in isolated, localized contexts but struggles to maintain consistency at the system level. The post argues that AI should be used as a candidate generator and validator rather than as the final decision-maker in code review. | 15 353 |
| 19 | Hello everyone some of you may not know but now we started to expand to WhatsApp and we are inviting you to join our WhatsApp channel link here 👇👇👇👇👇
WhatsApp Computer Science and Technology
We welcome you all to be part of this family | 15 461 |
| 20 |  The Joy of Old-School Coding After a Stupid Mistake
A short personal reflection on the frustration and satisfaction of debugging without AI assistance. The author made a mistake using a collection to map a one-to-one relationship in Entity Framework Core, which only integration tests caught. After resisting the urge to use Copilot, they found the fix themselves — a one-line change — and reflect on the emotional cycle of coding: frustration followed by joy. | 15 440 |
