Common editors, don't turn this into buzzfeed...
Common editors, don't turn this into buzzfeed...
You don't need a hacker to disable a Jeep's transmission, it does that on its own every few thousand miles.
Doesn't work with the current US tax structure - sales taxes are only collected on end-user purchases. Businesses do not pay sales taxes on business-to-business transactions in the US. It would create an accounting nightmare for most businesses.
The problem is that turn signals are a premium option on BMWs, it's not your average beemer driver's fault they can't afford them.
There are many standardization initiatives in progress. Adoption of standards in the embedded space takes years as code evolves MUCH more slowly than in the web world, and for good reason.
One of the major ones is AUTOSAR:
Since embedded programming is open to liability, it already has coding standards that are orders of magnitude higher than any web developer would ever reach. So yes, this particular case there was a failure, but on the whole, you don't have lowest-bidder outsourced programmers doing your powertrain code development.
For most serious work, you'll need a proper keyboard. Once you add a keyboard, you might as well just grab an ultraportable laptop (e.g. MB Air or Thinkpad X-series).
Nearly all sodas contain caffeine. Caffeine, like most psychoactive drugs, has effects proportional to body weight.
A can of coke has about 40 mg of caffeine. For standard 180 lb adult, that gives you a nice little wake-me-up. But put that much drug in a 40lb kid, and you'll see the effects similar to a healthy adult slamming back 2 cans of Red Bull.
Couple that with the lack of self-control of kids, and it's no wonder they're bouncing off the walls.
Let a 40-lb kid have 4 cokes in a day? When's the last time you put back a 8-pack of Red Bull? Of course they're going to raise hell.
"Black box" is a misnomer. All of the powertrain and safety ECUs in the car (there's over a dozen in modern vehicles, not including the several dozen other miscellaneous ECUs) have had the functionality built into their software as part of OBD-II compliance since 96. Airbag ECU, Traction control, Anti-lock brakes, Transmission, Engine, power steering, etc. All of them record data upon a sensor fault (e.g. Impact in a collision).
Fun fact: nearly half of the software in some ECUs is dedicated to OBD-II compliance.
Congress has REQUIRED black boxes in every vehicle since 1996 with the introduction of OBD-II. In particular, the freeze frame functionality, which captures all the data leading up to an accident. Ugh.
Only if your time is worth nothing. Mindstorms takes out all of the headaches and lets you focus on the fun parts of robotics. If you go the arduino route, be prepared to spend hours figuring out how to get things up and running, soldering, messing up things, breaking them, and scrounging for mechanical parts.
Do you work at the DMV?
While some "neat to have" features, you cobbled together your feature list without considering the tradeoffs they bring. All of these features have been considered by product managers and cut for good reason.
Since you haven't owned an iPad, I'm guessing you're more price sensitive. Most of your features will add cost, size, reduce battery life, and will give you little daily benefit.
- Full-sized USB ports - tablet is too thick, heavy and added cost. Also, to support devices like USB sticks, you have to add USB Host support to the device, which requires adding a 5V power supply output to the device, most expensive/power hungry USB host silicon/IP, and a large USB host driver stack that requires lots of software maintenance.
- Full-sized HDMI connector - added cost and thickness.
- Stereo Mics - nobody cares, added cost, and they don't work well in a thin form factor - generally for field recording you want cardioid-type mics which are larger, but more directional.
- Hardware radio toggles - nobody cares, added cost, confusion (which switch does what by feel?!) and the functionality is already deployable through corporate policies on some ecosystems.
- Offline maps - There are plenty of offline GPS apps available for existing ecosystems - TomTom, NavFree, and Garmin come to mind without even searching. This feature is best left to companies who know what they are doing in this space. If it's standard, you have to have more storage standard on your device which raises cost. Whatever you deploy won't be nearly as good as Google Maps anyway and will be useless in a few years once the data goes stale and you are too lazy to do the update process.
- Pixel Qi or whatever screen tech du jour - These will come naturally once they are better, cheaper, more manufacturable, and lower power than the existing crop of LCD displays. The current crop of screens, at least on the high end devices like iPad are readable enough in full sunlight so it's not a big pain point.
- Alternative OS support - Who cares? Tablets are not computers. Apple was the first company to understand this and this is why the iPad was so devastatingly successful. They are devices that perform functions. Use a computer if you need something that's flexible and programmable. Adding alternative OS support adds MILLIONS in software support costs, and you're not going to sell that many more tablets as a result.
The original iPad, when it was released in 2010, didn't have earth-shattering specs compared to the field at the time. They were good, maybe better in some areas. But iOS was like nothing the tablet market had ever seen before. It was good, fast, easy-to-learn, and reliable software that actually worked with fingers, and lo and behold, it turned out that's what the tablet market was missing.
Sure, Apple's marketing machine helped, but one could argue Microsoft or HP has (had?) just as much marketing budget as Apple and they failed to push tablets into the mainstream for years.
So call them "fanbois" all you want, but face reality - they make up the majority of the market. They are busy people who do not have time to put up with shitty software. Sure, there are aging nerds out there that refuse to let go of the hardware spec chase. If you think about it, they care about it because back in the day, that's what made the big difference in software performance. I know because I used to be that way. Nowadays, hardware is a commodity, cycles and RAM and plentiful, and the only differentiator is which ecosystem can actually deliver good software that takes advantage of the hardware.
It looks like Android is making good strides in this area, and hopefully the competition will continue to force all the tablet manufacturers to deliver better software for everyone across all platforms.
Nobody cares about tablet specs outside of screen size, battery life, and price. It's all about the software. Is it fast, responsive, and usable?
Is it easy to develop for? Will it be around for a while to justify developers investing in it? Does the company have a history of keeping platforms around?
"The most important thing in a man is not what he knows, but what he is." -- Narciso Yepes