SShortSingh.
Back to feed

The 90-Year History Behind Coin-Operated Binoculars at Scenic Overlooks

0
·1 views

Coin-operated binoculars, a familiar fixture at scenic viewpoints, have a history spanning roughly nine decades. These mounted viewing devices became widespread at tourist destinations across the United States and beyond, offering pay-per-view magnified sightseeing. The article, published on DPReview, traces the evolution of the technology and the companies behind its development and distribution. Over the years, the design and coin mechanisms have changed, though the core concept has remained largely the same. Despite the rise of smartphones and digital photography, these bolted binoculars continue to endure at popular overlooks worldwide.

Read the full story at Hacker News

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

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Meta Faces FTC Trial With Echoes of Historic Big Tobacco Cases

Meta is currently embroiled in a major antitrust trial brought by the Federal Trade Commission. The case has drawn comparisons to landmark litigation against the tobacco industry, suggesting potentially far-reaching consequences. The Economist reported on the trial on August 18, 2026, highlighting the high-stakes nature of the proceedings. The outcome could have significant implications for Meta's business structure and the broader tech industry.

0
ProgrammingDEV Community ·

How to Properly Benchmark a Unified LLM API for Invoice Data Extraction

Developers building Node.js invoice-extraction backends that route requests through a unified LLM API — supporting OpenAI, Claude, or Gemini via a single credential — must benchmark the full pipeline against both field-level quality thresholds and latency budgets before relying on it in production. A curated acceptance corpus of around 20 labeled documents, paired with reviewed expected outputs, can expose critical extraction failures that aggregate scores alone would obscure. Exact fields like invoice numbers and currency codes require normalized value comparisons, while latency should be measured at a percentile level rather than just an average to avoid masking slow outliers that could bottleneck support queues. Benchmark runs must use identical inputs, schema instructions, and retry policies across all candidate paths, and evaluators must distinguish between syntactically valid JSON and genuinely correct field extraction. The key takeaway is that a unified gateway's convenience — one API key and a clean interface — does not substitute for rigorous, representative testing against the actual documents a team processes.

0
ProgrammingDEV Community ·

How to Recover a Bricked Framework Laptop Using Built-In Tools

A Framework laptop that won't boot is often caused by BIOS corruption, a failed update, or misconfigured settings rather than permanent hardware damage. Framework laptops include a built-in recovery mechanism that can be triggered by holding a pinhole button on the device's underside while plugging in the charger, allowing the system to reflash the BIOS from a backup chip. If the built-in recovery fails, users can manually flash the BIOS by creating a bootable FAT32 USB drive using BIOS files and a flashing tool available on Framework's official support site. When software recovery methods are exhausted, reseating the RAM and storage modules is recommended, as loose components can also prevent the laptop from booting. Framework's user-serviceable design and support team provide additional options for diagnosing and resolving persistent hardware issues.

The 90-Year History Behind Coin-Operated Binoculars at Scenic Overlooks · ShortSingh