Samsung's packaging for the Galaxy S3 is very slick. Also, Dell's origami packaging for their 4k displays is absolutely brilliant.
Yeah, SVG renderers have more chance of being around in 50 years than WMF or PICT. But you still need to actively go through your data archives, find things in "endangered" formats, and migrate them to more future-proof formats. This requires substantial effort that increases as the collection grows. Then there's verifying that nothing was lost in the conversion to consider.
ImageMagick doesn't support PICT with vector information. I'm just trying to make a point that even if a format seems to be widespread now, it may become effectively useless in the future. Believe me PICT files were everywhere in the classic Mac days.
You're picking easy formats. What about Macintosh PICT, including vector information (not just a bitmap PICT)? What about WMF? I could see both those formats becoming effectively unusable within a decade, as they effectively depend on the drawing API/environment of ancient operating systems (classic MacOS and Windows 3).
But seriously, JPG is everywhere now but how long will it last? Could you read pre-JPEG image formats? Do you have software that will open PhotoCD, or PBM, or XBM or IFF in all their variants? I expect some formats like DNG will be around for a while, but the XMP processing instructions contain a "process version", and how long will software continue to support the process versions we use today? Data security really isn't straightforward when you don't know what the future holds.
JPEG wasn't standardised until 1992. THere are no 25-year-old JPEG files. Things have changed a lot since 1989.
Because you can see the doors being operated out the windows of the departure lounges as the ground crew load and unload baggage.
All fuel injectors for gasoline-powered road cars (mechanical injectors were used in racing for a while and were used for many years in diesel engines) are controlled by an ECU.
That's not quite true. There were mechanical fuel injection systems for petrol cars, e.g. the Lucas system in some of the Triumphs. They weren't known for being particularly reliable - EMP resistance would be the least of your worries.
Yes, S-beam is great. The phones exchange some information, set up a one-time WiFi Direct connection and transfer the file. No messing with Bluetooth pairing or any crap like that, authentication is provided by proximity.
US NFC payment system is apparently completely incompatible with the systems used in the rest of the world. The US system emulates swiping the magstrip while the European and Australian systems use some kind of PKI challenge/response.
I fly on 737-800 all the time and they definitely have outward-opening cargo doors.
If it's patented, you're compelled to publish your method. Are you confusing patents with trade secrets?
I can send money from my GMail account.
Well I don't know whether the Amazon one worked outside the US, but the Google one definitely doesn't. But given a choice between Google and Amazon, I'd take Amazon. I find them slightly less intrusive and pervasive.
Yeah, but very basic functionality like actually being able to type your name if you happen to be Japanese requires you to install the OS, then get a combination of strangely-named packages like ibus, im-chooser, anthy, some font packages, etc. and then screw around getting it configured. None of this is documented clearly. Windows or OSX lets you choose a language from a list at install time. Which do you think is easier?
Device drivers are another issue. Linux is simpler if there's a driver in the kernel tree and it works adequately. If there isn't, then it's far more trouble than Windows to find a driver and get it to work. Also, drivers often lack functionality on Linux. For example the Wacom tablet drivers aren't adequately configurable. There are some options in obscure text files that you need root to edit, but there's no simple way to switch mapping on-the-fly or reconfigure your buttons per application. This is all dead easy on OSX or Windows.
Linux may be easier for you, but there are far more use cases than "person with no exotic hardware speaking a language using Latin script".
It definitely doesn't just work if you need Japanese language support. You need to find the necessary packages, install them, configure ibus... Seriously it's a nightmare. On Windows or OSX you just choose it from the dropdown during installation. Every time I do a distro upgrade I have to go through this stupid pain-in-the-arse procedure again, trying to work out exactly which packages I need with no help from any documentation.