1995 SGI Paper by John Mashey Explored the Case for 128-Bit Processors

·1 views

A 1995 technical paper by John Mashey of Silicon Graphics Inc. (SGI) examined the potential prospects for 128-bit processor architectures. The document, recently surfaced on Hacker News, discusses the theoretical and practical considerations around moving beyond 64-bit computing. Mashey was a prominent computer scientist and architect who played a significant role in RISC processor development during that era. The paper offers a historical perspective on how engineers of the mid-1990s envisioned the long-term future of processor design. It has resurfaced as an archival reference, drawing renewed interest from the computing community.

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)

Open-Source Framework Offers Structured Testing Methodology for AI Agents

A developer has released an open-source, framework-agnostic testing methodology designed to rigorously evaluate AI agents beyond basic response checks. The project includes a 61-source benchmark map referencing standards such as BFCL, GAIA, SWE-bench, and WebArena, along with 58 universal test blocks organized across seven tiers. It also incorporates the full OWASP Top 10 for Agentic Applications 2026 and aligns with regulatory frameworks including NIST AI RMF, MITRE ATLAS, the EU AI Act, and ISO/IEC 42001. A real-world macOS agent called PheronAgent, equipped with over 50 tools, is included as a reference implementation with documented bugs and actual test runs. The repository is publicly available on GitHub, with documentation licensed under CC BY 4.0 and templates under MIT.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

One Follow-Up Prompt Can Catch the Data Bugs Your Code Review Misses

A piece published on DEV Community argues that data engineers routinely skip a critical step when using AI coding assistants: asking the model to critique its own output. The author illustrates the risk with an incremental load scenario, where an engineer catches two obvious flaws through self-review but misses a third — an unstable business key assumption — that later causes unexplained duplicate rows in production. The core argument is that prompting an AI to find problems generates fundamentally different output than prompting it to solve one, because the tasks are shaped differently. The recommended follow-up prompt — 'Critique this. What breaks first? What did you assume that I didn't tell you?' — is designed to surface hidden assumptions the engineer never explicitly provided. The author notes this habit is most absent among intermediate engineers, who have learned to question AI output but still treat the entire review process as solely their own responsibility.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer finds iOS app invisible to App Store search after months of flawed keyword tracking

An indie iOS developer discovered that their app ranked for only 2 of 59 tested keywords across six App Store storefronts, with both matches consisting solely of words already in the app's title. Critical search terms like 'app blocker' and 'digital detox' returned no results for the app in any country. The developer also found that their keyword-tracking script used a browser-style User-Agent header, which returned artificially optimistic rankings compared to neutral HTTP clients, making months of recorded data unreliable. A separate SEO check using the 'site:' search operator was similarly compromised, as it was returning unrelated results from Chinese Q&A sites rather than the developer's own domain. The developer concluded that the app's stagnant download count stemmed from indexing and measurement failures rather than a lack of demand or a marketing shortfall.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

React Custom Hooks Explained: How to Reuse Stateful Logic Across Components

Custom Hooks in React are JavaScript functions prefixed with 'use' that encapsulate reusable stateful logic, allowing developers to share it across multiple components without duplicating code. Common use cases include API data fetching, window resize detection, online/offline status monitoring, and form validation. Unlike copying logic into each component, Custom Hooks keep codebases cleaner and easier to maintain by isolating functionality in a single reusable function. Importantly, while the logic is shared, each component instance gets its own independent state, meaning two components using the same Hook do not share data. This concept is part of Day 18 of the React Mastery Series on DEV Community, which has been progressively covering advanced React patterns.

0 comments Read more at DEV Community