Language Selection

English French German Italian Portuguese Spanish

Forty years of Moore's Law

Filed under
Hardware
Misc

The article outlined what became known as Moore's Law, the observation that the number of transistors--tiny on/off switches that churn out electrical signals that get represented as 1s and 0s--on a chip can be doubled in a short period of time. Adopted as a yardstick by the tech industry, the concept is one of the reasons the industry evolved into a high-growth, but high-risk, affair.

This FAQ explains the impact and consequences of the principles set down in the April 19, 1965, article.

When writing the article, Moore noted that the number of devices (which then included transistors and resistors) inside chips was doubling every year, largely because engineers could shrink the size of transistors. That meant that the performance and capabilities of semiconductors was growing exponentially and would continue to. In 1975, Moore amended the law to state that the number of transistors doubled about every 24 months.

When the paper first came out, chips sported about 60 distinct devices. By contrast, Intel's latest Itanium chip comes with 1.7 billion silicon transistors.

As monumental as the article has become, it wasn't a big deal then. It started on page 114 of the magazine.

"It wasn't something you expected to join the archives," Moore said in a recent gathering with reporters. "I didn't think it would be especially accurate."

Full Story.

More in Tux Machines

Android Leftovers

The Licensing and Compliance Lab interviews AJ Jordon of gplenforced.org

So basically Bradley Kuhn gave a talk at FOSDEM '17 about GPL enforcement and I was like, wow, it sucks how many companies and people think that enforcing the GPL is a bad idea. I mean, if you disagree with copyleft that's fine (though I personally would argue with that position), but then you should use a suitable license. Like MIT. The very idea that we shouldn't enforce the GPL just doesn't make sense to me because it suggests that the text of the license is watery and unimportant. I don't know about you, but when I say I want my programs to respect users' freedom, I mean it. So GPL enforcement is important. It seemed to me that there are probably a lot of developers out there who want to support GPL enforcement but don't have a good way to voice that support. gplenforced.org is essentially a quick and dirty hack I wrote to make that dead-simple. Read more

Red Hat General and Financial News

today's howtos