Moore’s Law states the number of transistors on an integrated circuit will double about every two years. This law, coined by Intel and Fairchild founder [Gordon Moore] has been a truism since it’s introduction in 1965. Since the introduction of the Intel 4004 in 1971, to the Pentiums of 1993, and the Skylake processors introduced last month, the law has mostly held true.
The law, however, promises exponential growth in linear time. This is a promise that is ultimately unsustainable. This is not an article that considers the future roadblocks that will end [Moore]’s observation, but an article that says the expectations of Moore’s Law have already ended. It ended quietly, sometime around 2005, and we will never again see the time when transistor density, or faster processors, more capable graphics cards, and higher density memories will double in capability biannually.
We humans like to think of ourselves as the pinnacle of evolution on the planet, but that’s just a conceit. It takes humans roughly twenty years to reproduce, whereas some bacteria can make copies of themselves every 20 minutes. Countless generations of bacteria have honed and perfected their genomes into extremely evolved biological machines.
Most bacteria are harmless, and some are quite useful, even tasty – witness the lactofermented pickles and sauerkraut I made this summer. But some bacteria are pathogenic nightmares that have swarmed over the planet and caused untold misery and billions of deaths. For most of human history it has been so – the bugs were winning. Then a bright period dawned in the early 20th century – the Era of Antibiotics. At last we were delivered from the threat of pestilence, never more to suffer from plague and disease like our unfortunate ancestors. Infections were miraculously cured with a simple injection or pill, childhood diseases were no longer reaping their tragic harvest, and soldiers on the battlefield were surviving wounds that would have festered and led to a slow, painful death.
Now it seems like this bright spot of relief from bacterial disease might be drawing to an end. Resistant strains of bacteria are in the news these days, and the rise of superbugs seems inevitable. But is it? Have we run out of tools to fight back? Not quite yet as it turns out. But there’s a lot of work to do to make sure we win this battle.
On the far side of the Boso peninsula lies Kamogawa. This isn’t the Japan of LEDs, Otaku and maid cafes, or that of wage slave salarymen collapsing from exhaustion. This is the Japan of rice farmers and fields, fresh fish and wild boar, electron microscopes and gigabit fiber, SMD assembly and 500Mhz 5 Gigasample oscilloscopes.
The world has changed. In the 20th century the life of a rural hacker was a constant hunt for technological innovation. We scratched around for whatever we could find. A (usually national) periodical would give its monthly injection of technological curios. And knowledge was locked tight within expensive textbooks, which even if you could afford them might take weeks to arrive.
So, as had been the case for the preceding 1000 years, innovation clustered around technological hubs, San Francisco, Cambridge, and Tokyo among others. And Hackers flocked to these centers where innovation flourished while Hackers exchanged knowledge and tools.
But then the world of the rural Hacker began to expand. The technological hubs that so many rural hackers had migrated to began to connect the world. Young Hackers could learn to program (as I learned C) from textfiles posted on BBSs and exchange knowledge linking national communities. Shortly after that the Internet came bringing its Eternal September. Hackers across the world, regardless of location could communicate.
On the flip-side tech centers were changing too. Venture capital, rather than bootstrapping became the norm. With the influx of cash the demand for skilled Hackers rose, increasing wages and further focusing tech talent around these hubs. But rents and expenses rose too. And Hackers became locked into their expensive lifestyles; eyes firmly focused on the promised million dollar payoff and the eternal dream of an “exit”.
For some though, the freedom to Hack is more important than that million dollar exit and so a new model is emerging. Groups of Hackers in rural communities with low cost lifestyles and access to the world’s best technical talent and equipment that would put the best startups to shame.
Buzzword technology has two possible fates: they fail and disappear or they succeed and disappear. Remember at one time “multimedia” and “networking” were buzzwords. They succeeded and now they’ve vanished into ubiquity. Of course, there are plenty of failed buzzwords (like telecosm) that you probably don’t even remember. They just vanished into obscurity.
Unless you’ve been living under the CNC mill in your local hackerspace, you’ve probably heard or read about the “Internet of Things” (IoT). Companies big and small have realized that getting in early on The Next Big Thing is good for share prices and, right now, IoT is where everyone is trying to make a play.
There’s two things I’d observe, though: First, IoT is far from new. Connecting embedded systems to the Internet is old hat (I even wrote a book called Embedded Internet Design way back in 2003). Second, the way it is going, IoT–in its current incarnation–is doomed.
Every year, more than 30,000 people are killed in motor vehicle accidents in the US, and many many more are injured. Humans, in general, aren’t great drivers. Until dependable self-driving cars make their way into garages and driveways across the country, there is still a great amount of work that can be done to improve the safety of automobiles, and the best hope on the horizon is Vehicle to Vehicle communications (V2V). We keep hearing this technology mentioned in news stories, but the underlying technology is almost never discussed. So I decided to take a look at what hardware we can expect in early V2V, and the features you can expect to see when your car begins to build a social network with the others around it.
With the summer’s big security conferences over, now is a good time to take a look back on automotive security. With talks about attacks on Chrysler, GM and Tesla, and a whole new Car Hacking village at DEF CON, it’s becoming clear that autosec is a theme that isn’t going away.
Up until this year, the main theme of autosec has been the in-vehicle network. This is the connection between the controllers that run your engine, pulse your anti-lock brakes, fire your airbags, and play your tunes. In most vehicles, they communicate over a protocol called Controller Area Network (CAN).
An early paper on this research [PDF] was published back in 2010 by The Center for Automotive Embedded Systems Security,a joint research effort between University of California San Diego and the University of Washington. They showed a number of vulnerabilities that could be exploited with physical access to a vehicle’s networks.
A number of talks were given on in-vehicle network security, which revealed a common theme: access to the internal network gives control of the vehicle. We even had a series about it here on Hackaday.
The response from the automotive industry was a collective “yeah, we already knew that.” These networks were never designed to be secure, but focused on providing reliable, real-time data transfer between controllers. With data transfer as the main design goal, it was inevitable there would be a few interesting exploits.
For many hardware enthusiasts, it’s hard to stop imagining the possibilities of an almighty fablab in our garage — a glorious suite of machines that can make the widgets of our dreams. Over the years, many of us start to build just that, assembling marvelous workbenches for the rest of us to drool over. The question is: “how do we get there?”
Ok, let’s say we’ve got a blank garage. We might be able to pick up a couple of tools and just “roll with it,” teaching ourselves the basics as we go and learning from our mistakes. With enough endurance, we’ll wake up ten years later and realize that, among the CNC mill, lathe, o-scope, logic analyzer, and the graveyard of projects on the shelves–we’ve made it!
Image Credit: [Rupunzell] on EEVBlog
“Just rolling with it,” though, can squeeze the last bits of change out of our wallets–not to mention ten years being a long journey while flying solo the whole time. Hardware costs money. Aimless experimentation, without understanding the space of “what expectations are realistic,” can cost lots of money when things break.
These days, the internet might do a great job of bringing people together with the same interest. But how does it fare in exchanging the technical know-how that’s tied directly to tools of the trade? Can we get the same experience from a chatroom as we might from a few minutes with the local ‘CNC Whisperer’ who can tell us the ins-and-outs about tuning the machine’s PID controllers?
I’d say that we just can’t. “Getting started” in any subject often seems daunting, but we’re at a compounded disadvantage in that the gurus on the forum have some shared implicit knowledge and jargon on the subject that we wont have if we truly are taking our first steps. (Not to fear, though; none of us were born with this stuff!)
Ruling out forums for taking our first baby steps, where can we find the “seasoned gurus” to give us that founding knowledge? It’s unlikely that any coffee shop would house the local hardware guru sippin’ a joe and taking questions. Fear not, though; there are places for hackers to get their sustenance.
![Image Credit: [Rupunzell] on EEVBlog](https://hackaday.com/wp-content/uploads/2015/08/eevblogrupunzel.jpg)
