I picked up the HTC One M7 when it was new, and the Sense 5.0 is a drastic, drastic improvement over the previous iterations. Plus more recent updates (up to 6.0 now, I think) you can even disable Blinkfeed completely and the like, giving it a feel very close to stock. I've been fairly happy with it. The only thing really making me consider upgrading now is the terrible camera.

Here's a real answer for you - Naval ships are generally designed and built as a unit. The base hull, the systems involved, propulsion, electrical, power generation, etc all are tailored for one another. Once you have all this together, making wholesale changes to it can be tricky without basically redesigning the whole thing anyway. New technology, new efficiency-improving designs, better designs based on things learned can really only be done with new designs. It's like a car chassis - at some point, you have to redesign the underpinnings to make a more efficient and better car. You can't take a 1957 Chevy and tear it down to the chassis and rebuild it with modern technology and have it be as safe, efficient, or whatnot as a car designed and built from the ground up with the new technology, and certainly not at a price point close to a new car. To say nothing of issues like metal fatigue, corrosion, brittleness from age, etc. Likewise, even though it's somewhat counter-intuitive, it's often more economical to build a modern ship from the keel up than to, say, gut a carrier and retrofit new tech in.

The Nook Simple Touch uses zForce Infrared, which is pretty much which this describes. Reviews at the time mentioned it, which links to here to describe it. I have NST too and it works fairly well, most of the time.

I've read articles (about spam, but this is similiar) that talk about how they don't *want* it to be especially believable. It's harder for them to try to be believable and have smart people drop out as soon as they realize it's a scam. On the other hand, if they're blatantly obvious, the people they manage to net will likely be the most gullible and most likely to actually follow through with a scam.

This. I work at a telecom company, and we just got a new area code allocated in my area recently. People are getting virgin phone numbers that have never been used, and we've already had them calling asking for new numbers because they're getting so many scam and junk calls.

I'd guess the intersection between users who require 64-bit Windows on a processor that supports VT-x and users who require the use of 16-bit programs that won't work in a virtualized environment is pretty small. Plus I suspect Microsoft likes the reduction in attack surface in removing all the old cruft, even if it could technically be reworked to run.

I am not a Windows developer, but I have been a long-time tinkerer and user. The 32-bit versions of Windows, even up to and including the previews of Windows 10, still include the same old NTVDM that provides support for 16-bit DOS and Windows programs. I've personally played around with running completely unmodified copies of MS-DOS Executive from Windows 2.x and 3.0, Program Manager, and various other ancient things with absolutely no trouble. This likely includes some very old code to allow this old stuff to run unmodified. There's been a bug or two in NTVDM that date back to the first versions of NT.

As for early Win32, modern versions of Windows, including 64-bit versions, will still run the early Win32 demos that came with some of the earliest Windows NT 3.1 betas and pre-releases (once the executable format stabilized).

Now whether this means there's actual literal old code still floating around, or just reimplementation of old libraries and APIs is anybody's guess. Based on some of the security flaws that have cropped up that date back to the earliest versions of Windows NT it certainly seems possible that there's some very old code floating around still. As a closed-source project, we'll likely never know. Though it'd be interesting to poke around in the leaked NT4/Win2k source from several years back and see if there's any clues. In general, rewriting tested, vetted code is a bad idea unless there's a good reason to rewrite it, so I'd bet there's plenty of old code kicking around in Windows in driver handling, kernel memory management, etc.

OS X is somewhat different since it was more or less reimplemented from the ground up rather than evolutionary from existing Mac OSes - though it'd be interesting to see what might be left over from NeXT or BSD. I believe Carbon is still part of the OS, even if its deprecated; I'm even less of a Mac dev guy than I am a Windows dev, so I can't speak to the existence of old code in that.

I used to keep several fingers at several options, although mostly it was to avoid having to go back through the early options over and over. Some of those books packed at least 20 endings into it. Sometimes I'd end up struggling to actually read it trying to keep all the places marked. Good times.

They do allow outbound transfers (it's a requirement of being an accredited registrar) but it's a giant pain in the ass. I used to do customer domain management for my company and getting the auth code and domain unlocked from these guys was an exercise in frustration. Took several calls and emails to "authorize". This was several years ago; maybe they have an online portal now.

I love that Dogecoin is apparently a big enough thing now to be mentioned in the same breath as Bitcoin and Litecoin.

My wife's 2003 Grand Am has two levels - light on solid means you can keep driving until you get it looked at, flashing means pull over immediately. I've only seen it flashing once - when the engine stripped a rocker arm and started flailing bits around in the head. This is an OBD II standard across all cars with the system.

Incidentally, they sell a cheap ($20, and often $15) bluetooth- or wifi-enabled plug that links up to a cell phone app to read codes and other OBD II info. It's been a godsend when I was trying to diagnose a couple issues with that car.

Microsoft released Windows for Pen Computing somewhere around Windows 3.1 (1991ish?). The Pen addons continued through the 9x releases. Granted it's not really a tablet initiative by Microsoft personally, but they dabbled in it. It worked reasonably well, and was a full real copy of Windows. They pretty much suffered the same limitations as later Tablet PCs (and today's tablets), though. Mousing was great, any sort of data input was a giant pain and pretty much required an addon keyboard.

This was where they failed for me. I had a couple different Fujitsu Stylistics, and overall I loved it. OneNote was great for notes, and had pretty decent handwriting recognition. I could run any Windows application, and overall it did great. I could sync notes across devices and access them anywhere. It was pretty impressive stuff for ~2000. But the big downfall was the jet engine fan and battery life. I'd be in a quiet classroom or office meeting, and the fan would kick on. I'd get That Look from people and it got old. I also usually only managed to get 2-3 hours out of it, although I did have a spare battery I'd carry around for it. I usually had enough juice to last a whole day of college classes, but sometimes not.

It'd also get pretty darn hot when I was doing anything that ran it very hard, but note-taking didn't usually do that.

My wife and I just last week did a marathon watching of all six. She hasn't historically been a Sci Fi fan, and she thinks she saw ANH as a child but didn't really remember it. Overall, she enjoyed all six fine. She recognized some of the stilted handling of the romance and such, but in general she liked it fine. She had no preconceived notions or expectations going in.

She'll admit the original trilogy are better movies, but she liked them all fine. As a lifelong Star Trek/Star Wars fan myself, it's interesting seeing her perspective on it all since for her, they're just more movies. She doesn't have a lifetime of expectations or fandom or anything.

The reviews on the Play store are showing a fairly high possibility of a bootloop. While I'm all for open source and public patches where appropriate, I expect I'll be passing on this one for now.