Longform articles, the best of what the Hackaday writing crew has to offer.
In 1983, the Lisa was supposed to be a barnburner. Apple’s brand-new computer had a cutting edge GUI, a mouse, and power far beyond the 8-bit machines that came before. It looked like nothing else on the market, and had a price tag to match—retailing at $9,995, or the equivalent of over $30,000 today.
It held so much promise. And yet, come 1989, Apple was burying almost 3,000 examples in a landfill. What went wrong?
Continue reading “Why Apple Dumped 2,700 Computers In A Landfill In 1989”
So far in the “Field Guide” series, we’ve mainly looked at critical infrastructure systems that, while often blending into the scenery, are easily observable once you know where to look. From the substations, transmission lines, and local distribution systems that make up the electrical grid to cell towers and even weigh stations, most of what we’ve covered so far are mega-scale engineering projects that are critical to modern life, each of which you can get a good look at while you’re tooling down the road in a car.
This time around, though, we’re going to switch things up a bit and discuss a less-obvious but vitally important infrastructure system: the cold chain. While you might never have heard the term, you’ve certainly seen most of the major components at one time or another, and if you’ve ever enjoyed fresh fruit in the dead of winter or microwaved a frozen burrito for dinner, you’ve taken advantage of a globe-spanning system that makes sure environmentally sensitive products can be safely stored and transported.
Continue reading “A Field Guide To The North American Cold Chain”
If you grew up in the middle of the Cold War, you probably remember hearing about the Distant Early Warning line between duck-and-cover drills. The United States and Canada built the DEW line radar stations throughout the Arctic to detect potential attacks from the other side of the globe.
MIT’s Lincoln Lab proposed the DEW Line in 1952, and the plan was ambitious. In order to spot bombers crossing over the Arctic circle in time, it required radar twice as powerful as the best radar of the day. It also needed communications systems that were 99 percent reliable, even in the face of terrestrial and solar weather.
In the end, there were 33 stations built from Alaska to Greenland in an astonishing 32 months. Keep in mind that these stations were located in a very inhospitable environment, where temperatures reached down to -60 °F (-51 °C). Operators kept the stations running 24/7 for 36 years, from 1957 to 1993.
The DEW line wasn’t the only radar early-warning system that the US and Canada had in place, only the most ambitious. The Pinetree Line was first activated in 1951. However, its simple radar was prone to jamming and couldn’t pick up things close to the ground. It was also too close to main cities along the border to offer them much protection. Even so, the 33 major stations, along with six smaller stations, did better than expected. Continue reading “The DEW Line Remembered”
After the fire and fury of liftoff, when a spacecraft is sailing silently through space, you could be forgiven for thinking the hard part of the mission is over. After all, riding what’s essentially a domesticated explosion up and out of Earth’s gravity well very nearly pushes physics and current material science to the breaking point.
But in reality, getting into space is just the first on a long list of nearly impossible things that need to go right for a successful mission. While scientific experiments performed aboard the International Space Station and other crewed vehicles have the benefit of human supervision, the vast majority of satellites, probes, and rovers must be able to operate in total isolation. With nobody nearby to flick the power switch off and on again, such craft need to be designed with multiple layers of redundant systems and safe modes if they’re to have any hope of surviving even the most mundane system failure.
That said, nobody can predict the future. Despite the best efforts of everyone involved, there will always be edge cases or abnormal scenarios that don’t get accounted for. With proper planning and a pinch of luck, the majority of missions are able to skirt these scenarios and complete their missions without serious incident.
Unfortunately, Lunar Trailblazer isn’t one of those missions. Things started well enough — the February 26th launch of the SpaceX Falcon 9 went perfectly, and the rocket’s second stage gave the vehicle the push it needed to reach the Moon. The small 210 kg (460 lb) lunar probe then separated from the booster and transmitted an initial status message that was received by the Caltech mission controllers in Pasadena, California which indicated it was free-flying and powering up its systems.
But since then, nothing has gone to plan.
There are a lot of benefits to writing for Hackaday, but hands down one of the best is getting paid to fall down fascinating rabbit holes. These often — but not always — delightful journeys generally start with chance comments by readers, conversations with fellow writers, or just the random largesse of The Algorithm. Once steered in the right direction, a few mouse clicks are all it takes for the properly prepared mind to lose a few hours chasing down an interesting tale.
I’d like to say that’s exactly how this article came to be, but to be honest, I have no idea where I first heard about the prison camp lathe. I only know that I had a link to a PDF of an article written in 1949, and that was enough to get me going. It was probably a thread I shouldn’t have tugged on, but I’m glad I did because it unraveled into a story not only of mechanical engineering chops winning the day under difficult circumstances, but also of how ingenuity and determination can come together to make the unbearable a little less trying, and how social engineering is an important a skill if you want to survive the unsurvivable.
Continue reading “Hacking When It Counts: DIY Prosthetics And The Prison Camp Lathe”
My first encounter with C++ was way back in the 1990s, when it was one of the Real Programming Languages™ that I sometimes heard about as I was still splashing about in the kiddie pool with Visual Basic, PHP and JavaScript. The first formally standardized version of C++ is the ISO 1998 standard, but it had been making headways as a ‘better C’ for decades at that point since Bjarne Stroustrup added that increment operator to C in 1979 and released C++ to the public in 1985.
Why did I pick C++ as my primary programming language? Mainly because it was well supported and with free tooling: a free Borland compiler or g++ on the GCC side. Alternatives like VB, Java, and D felt far too niche compared to established languages, while C++ gave you access to the lingua franca of C while adding many modern features like OOP and a more streamlined syntax in addition to the Standard Template Library (STL) with gobs of useful building blocks.
Years later, as a grizzled senior C++ developer, I have come to embrace the notion that being good at a programming language also means having strong opinions on all that is wrong with the language. True to form, while C++ has many good points, there are still major warts and many heavily neglected aspects that get me and other C++ developers riled up.
Continue reading “Dearest C++, Let Me Count The Ways I Love/Hate Thee”
Immutable distributions are slowly spreading across the Linux world– but should you care? Are they hacker friendly? What does “immutable” mean, anyway?
Immutable means “not subject or susceptible to change” according to Merriam-Webster, which is not 100% accurate in this context, but it’s close enough and the name is there so we’re stuck with it. Immutable distributions are subject to change, it’s just that how you change them is quite a bit different than bog-standard Linux. Will this matter to you? Read on to find out! (Or, if you know the answers already, read on to find out how angry you should be in the comments section.) Continue reading “Personal Reflections On Immutable Linux”
