It's a little difficult to prove direct correlation, as is the usual case with Apple product releases, but if you recall the original announcements for iPhone specifically called for it to run only Web 2.0 applications through Safari. For example. It wasn't until after the first jailbreaks and unofficial third party apps that the App Store came along after weathering objections from Jobs. It's hard to conclusively say whether it was directly in response to jailbreakers or not, but it's likely it sped up their plans.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
The closest to bad I can think of was the time they produced keyboards in the Natural line with the cursor keys in a + instead of inverted T. Had one at work many years ago and hated it enough to buy my own different one.
Fun Fact: Susan Kare also designed many of the icons used in early versions of OS/2, as well as Windows 3.0. Basically the entirety of popular early GUI computing was designed by her.
So also did the graphic design of Solitaire that was included with Windows through XP (though I think XP redesigned the card backs), so her work might be the most seen graphic design in computing history.
Windows has had the ctrl-alt-del to log in/unlock since literally the first version of Windows NT, 3.1, in 1993. That's a long time to have feature envy, though I suppose it's possible. I generally wonder if the average user is clever enough to understand the implication anyway - if you put up a fake login dialog on Windows just past the ctrl-alt-del, I bet most users would just fill it out and go with it rather than think they're under attack.
It depends on the part and the popularity of the model. For things like Mustangs, Camaros, Firebirds, etc there's lots of aftermarket options for all sorts of things. Fenders, door panels, door skins, bumper covers... you could probably build a whole vintage Mustang from the frame up with non-Ford-OEM parts. Likewise with parts that are widely shared across models and are generally considered consumable - brake pads, clutches, alternators, etc. Readily available third party. On the other hand, if you need something random like a bit of interior molding or a random knob or door panel for, say, a 1991 Toyota MR2 you're going to have a harder time avoiding dealer parts or a couple expensive specialist makers. Body parts will almost certainly be OEM if they're even available at all, outside of something like custom carbon fiber. There's been some experimentation done in the MR2 community to 3D print a replacement for a little plastic slider that often breaks, leaving the climate control temperature slider hard to use or inoperative all together. Durability and tolerances have been problems so far, but it's the perfect example of the kind of little thing that 3D printing could open up for very cheap that would otherwise require a $100+ entire new climate control head unit.
They got the supply part of it, but they needed the knowledge and price competitiveness of it. I got into doing some Arduino stuff awhile ago, and when I was a noob I stopped by just to look at their various shields and options. One of the employees asked if I needed help and I asked a couple questions about the compatibility and features and he had no idea about any of it. If they'd prepared their employees to answer at least basic questions about them, and not had them priced 30-40% higher than online, it might have worked better. Not everyone in the maker movement is an expert; being able to get someone nudged in the right direction could have made a bigger impact and been a driver to the store.
I'm 34 and even I can only count the numbers of times I've actually used a typewriter for something other than messing with with on one hand. Granted my family was an early adopter of computers - I'm pretty sure I was the only fourth grader in my school turning in computer printed things instead of typewriter things, but still. I keep thinking it'd be fun to pick up an old manual typewriter, and they show up in thrift stores reasonably often, I just don't know what I'd do with the thing. I already have enough random computer stuff sitting around taking up space. Exposure in movies and media is completely different than actually using something and understanding its operation, so I could understand someone 24 being unaware of the details.
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.
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.