Urgent.News

What's breaking now, across thousands of outlets.

Tech

From 10 µm to 3 nm: how chips got so small (and why 3 nm isn't 3 nm)

In 1971 Intel's first microprocessor, the 4004 , was built on a 10 micrometre process and held about 2,300 transistors . Today's leading chips are marketed as 3 nm and hold tens of billions of transistors. The largest packages pass 100 billion. Shrinking transistors lets you fit more onto the same silicon, which means more parallel work, more cache and more specialised hardware. The catch: "3 nm"…

From 1971 to today, semiconductor chips have shrunk dramatically, transitioning from a 10-micrometer process to the current 3-nanometer generation. The journey of shrinking transistors has enabled more powerful, energy-efficient, and specialized computing capabilities. However, the term "3 nm" is now a marketing label rather than an accurate measurement of physical dimensions.

Shrinking transistors has become increasingly challenging, as engineers face issues such as leakage, heat generation, and variations at the atomic scale. To overcome these challenges, the industry has continually innovated, developing new transistor architectures like FinFETs and gate-all-around structures, and employing advanced manufacturing techniques such as extreme ultraviolet lithography.

As a result, modern chips represent a far cry from their early 1970s counterparts, with modern fabrication processes and materials science enabling unprecedented levels of miniaturization and performance.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Trust does not carry forward

DeepSeek V4 Pro runs 1.6 trillion parameters, 49 billion of them active, and scores 44 on the Artificial Analysis Intelligence Index.

  • DeepSeek V4 Pro has 1.6 trillion parameters
  • Model scores 44 on Artificial Analysis Intelligence Index
  • 86% of answers fabricated when unanswerable

Writing Knowledge-Base Entries an Auto-Responder Can Actually Quote

A knowledge base can read well to a person and still fail an auto-responder. People skim, infer, and jump around a document; a responder quotes.

  • Auto-responder quoting can lose context from knowledge base entries.
  • Entries for auto-responder should be granular, quotable units.
  • Breaking down information into atomic fact cards improves maintainability.

I Built db-migrator to Move Data Between Databases and Validate the Results

Database migrations always sound easy on paper. Read data from one database, transform it, and write it somewhere else. Simple enough, right? Well, not always.

  • Fatih developed db-migrator to simplify database migrations and validate results.
  • Features include job scheduling, schema drift detection, rollback, and exportable reports.

How I got my first pull request merged into LiteLLM

My first contribution to LiteLLM , the open-source LLM gateway, was PR #38591 . It fixed a bug where content an agent had retrieved was compressed again and lost, which made agents loop.

  • First contribution to LiteLLM was PR #38591
  • Fixed bug causing agents to loop due to re-compression
  • Learned project standards through CI/CD processes

More from Thursday 5 November →