After going through the original quick list we tossed together, people were chiming in like crazy. We felt another 10 might help satiate the desire to smirk at the silliness of tech portrayed in movies and TV. Gathering examples from your comments, we have compiled part 2. While I would have loved to narrow this down to a specific item like incorrect lingo or screen grabs, I didn’t quite have enough specific scenes to do it yet. Be sure to keep the comments coming and be specific, I haven’t seen many of these till someone points it out.
Continue reading “Top 10 Hacking Failures in movies: part 2”
It had been requested that we make a short video covering the top worst hacks in movies. Being the community that we are, it seemed like an interesting request. We asked for your input, and you were happy to deliver! However, the proposition of creating a “top 10” list turned out to be quite difficult. There were just SO MANY horrible scenes that I started thinking about how to even categorize them. We could probably to a “top 10” in any of the following categories without even having to dig too deeply:
- hacker lingo
- mocked up interfaces
- fake input devices
- virus screen-takeover moments
- access denied messages
- hardware taped together
Honestly, after breaking it down in such a manner, making the top 10 movie hacking failures, felt painfully general. It is like making a list of “top 10 animals that ever existed”. The state of technology portrayal in movies is frankly abysmal. It is obvious that the only people who know less about tech than “hollywood” are the people making laws about it.
Continue reading “Top 10 hacking failures in movies”
Most microcontroller manufacturers give you some kind of free development toolchain or IDE with their silicon products. Often it’s crippled, closed source, and a large download. This is pretty inconvenient when you want to have firmware that’s easy to build and distribute. I’ve found many of these toolchains to be annoying to use, and requiring closed source software to build open source firmware seems less than desirable.
It’s possible to build code for most microcontrollers using command line tools. You’ll need a compiler, the device manufacturer’s libraries and header files, and some method of flashing the device. A lot of these tools are open source, which lets you have an open source toolchain that builds your project.
Setting up these tools can be a bit tricky, so I’m building a set of templates to make it easier. Each template has instructions on setting up the toolchain, a Makefile to build the firmware, and sample code to get up and running quickly. It’s all public domain, so you can use it for whatever you’d like.
Currently there’s support for AVR, MSP430, Stellaris ARM, and STM32L1. More devices are in the works, and suggestions are welcome. Hopefully this helps people get started building firmware that’s easy to build and distribute with projects.
We received a tip from [Fabien] that Texas Instruments had posted a set of IDEs for the Stellaris Launchpad on their download page. At first we skipped right over the link, but then decided to take a look and see if things had changed any since the MSP430 Launchpad had been released. As we expected, there’s really no help on this page if you’re looking to develop for the hardware without using one of these IDEs.
Why would we want to forego the preconfigured development environments TI supplies? For one thing, they offer only trial licenses. When you go to download one of the packages you have to wade through a eyebrow-raising non-export agreement. When we made it that far, the ~500 MB Sourcery package we downloaded was quite slow. And we don’t see any option for installing any of these on a Linux machine. No matter what OS you choose, we think you should be able to develop for any architecture using the same development environment — be it Eclipse, GNU Emacs, Notepad, or whatever . We don’t want to download a huge package just to try out a new chip.
We know you can develop for Stellaris ARM chips using a vanilla cross compiler like arm-none-eabi (we use Sourcery CodeBench Lite — formerly CodeSourcery G++ lite). We hope that TI is planning on adding a barebones package that supplies a simple Makefile, Linker Script, and base libraries for the hardware. But we won’t hold our breath. After all, it is an industry standard to leave out Linux support.
I have often sat, gazing at my aquarium, wondering what life is like for those critters I keep captive. Are they bored and yearning to be set free? Are they content with their gluttonous lifestyle and constant pampering?
This is a question that is often raised with animals of a higher order, like pachyderm in the zoo, or chimpanzee. Those are easier to personify and to debate, but those are also, not often in our homes.
I keep my aquariums overgrown with actual live plant life. I have a flourishing ecosystem of natural plant filtration and invertebrates that I truly enjoy watching as they pick at the debris and bustle throughout the day. I test my water regularly to make sure it is optimal for the health of all involved. But my fish, well, as I said, I wonder about them.
Continue reading “Should we make games for fish?”
“Nothing happens in the midwest”. I won’t say who said it, but it absolutely makes my blood boil. I’ve heard this several times during my time at Hackaday. Aside from being so insanely arrogant and dismissive, it is also completely inaccurate.
Some people believe you absolutely have to be on a coast to be part of anything interesting. In the modern age of the internet, geographical location is becoming less and less of an issue. People are collaborating on projects that span the world. Here at hackaday we see projects quite daily that are spawned from a forum linking hackers to a common theme with virtually no central geographical point. Robots, video games, open source software, tools, and art installations have all sprung from the diaspora that is the hacker culture without any necessity for being located on a coast.
With tools like 3d printers becoming common in hackerspaces collaboration on physical design is even being spread geographically. You could be in your garage in Arkansas, assembling a machine that was designed by someone in Minnesota, and inserting code that was uploaded by someone in Kansas!
Sure, we all know the coasts are great. High concentrations of like minded people as well as the culture you can find anywhere near the ocean. But please, don’t ignore the middle, it makes you sound like antiquated ass.
Batman’s ability to fly is a falsehood. Or at least so says science. We didn’t know science was into disproving super-hero movies (that’s a deep well to drink from) but to each his own. But back in December the Journal of Physics Special Topics took on the subject with their scholarly paper entitled Trajectory of a Falling Batman. The equations presented in the two-page white paper may be above your head, but the concepts are not.
It’s not that Batman can’t fly in the way explained in the film. It’s that he can’t land without great bodily harm. By analyzing the cape in this frame of the film, researchers used Batman’s body height to establish wing span and area. The numbers aren’t good. Top speed will reach about 110 km/h with a sustained velocity of 80 km/h. That’s 80 mph at top speed and just under 50 mph when he comes in for a landing.
Oh Batman, how you’ve let us all down. If you liked this paper, you should dig through the archives. We always wondered if [Bruce Willis] could have actually saved the world from an asteroid.