TypeScript private vs # Fields: Choosing the Right Encapsulation in 2026

·1 views

TypeScript offers two distinct encapsulation models — the compile-time private modifier and ECMAScript # hard-private fields — which are fundamentally incompatible and not interchangeable. The private keyword provides no runtime protection, as it disappears after transpilation and leaves fields accessible as plain JavaScript properties. ECMAScript # fields enforce true runtime privacy through WeakMap storage, making fields inaccessible to any external code even after compilation. Developers are advised to use private for type safety within controlled TypeScript-only codebases, and # when building libraries, handling sensitive data, or operating in untrusted environments. Mixing both patterns without clear conventions can silently break encapsulation and cause reflection-based tooling to fail.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

GLP-1 Drugs Like Ozempic Linked to Reduced Risk of Serious Infections Including TB

GLP-1 receptor agonist drugs, including popular medications like Ozempic, are showing a potential association with lower rates of serious infections, including tuberculosis. Researchers have begun linking these widely used diabetes and weight-loss drugs to unexpected immune-related benefits beyond their primary metabolic effects. The findings suggest GLP-1 drugs may have broader health implications than previously understood. Scientists are investigating the mechanisms behind this possible protective effect, though the research is still in early stages.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

How One AI Firm Cut Model Spend by Routing Tasks Away From GPT-4o

An AI company discovered that GPT-4o was handling 77% of its production traffic while consuming 97% of its total model spend, revealing a costly imbalance in how tasks were assigned to language models. The disparity arose not from deliberate choices but from three systemic forces: demos built on the strongest model becoming permanent defaults, no per-task cost visibility in monthly bills, and asymmetric blame that punished cheap-model failures but never questioned frontier-model overuse. To address this, the company introduced a written routing policy that reserves frontier models for open-ended, high-stakes, or judgment-heavy tasks, while directing structured, verifiable work to cheaper alternatives. The key distinction driving the policy is whether a task executes an existing plan — which cheaper models handle well — or requires deciding the plan, where errors are costly to detect and reverse. The company also cautions that the right success metric is cost per completed task, not cost per call, since a cheaper model requiring multiple retries can negate its savings.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Models Don't Go Rogue

Article URL: https://mail.cyberneticforests.com/models-dont-go-rogue/ Comments URL: https://news.ycombinator.com/item?id=49557988 Points: 3 # Comments: 0

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Developer Builds Confidence-Gated Image Recognition System Using Five Specialized AI Models

A developer has built TargetV1, a personal image recognition pipeline that uses five specialized AI models — DINOv3, SAM, Moondream2, CLIP, and BLIP — each assigned a distinct task rather than relying on a single model to handle everything. The system is designed to acknowledge uncertainty and self-verify instead of producing confident but incorrect outputs. Development hit an early roadblock when PyTorch lacked compiled CUDA kernels for the new NVIDIA Blackwell GPU architecture, which was resolved by installing a newer PyTorch build targeting the cu128 runtime. A second setback arose from manually cloning model repositories, which caused Windows path conflicts, corrupted weight downloads, and mismatched layer names, problems that were ultimately bypassed by switching to Hugging Face's transformers library. The project highlights practical challenges developers face when working with cutting-edge hardware and fragmented model tooling outside mainstream tutorials.

0 comments Read more at DEV Community