The problem is you when you need to specify a filename and the displayed value is different that the true value, causing any number of errors, for unexplained reasons. That's the worst kind of simplification in my opinion.
Reminds me of other bad decisions from older Windows versions. Instead of a proper filesystem permissions, Explorer would tell you "Don't look in here, you could break something." I like to call it the "Band-aid over a gaping wound" model.
I think they're pretty great at it, actually. I'm fully used to them, and I like them.
The problem is you when you need to specify a filename and the displayed value is different that the true value, causing any number of errors, for unexplained reasons. That's the worst kind of simplification in my opinion.
Not a problem for the casual user, which is the majority of people using Windows.
Reminds me of other bad decisions from older Windows versions. Instead of a proper filesystem permissions, Explorer would tell you "Don't look in here, you could break something." I like to call it the "Band-aid over a gaping wound" model.
Why not? It doesn't cost Microsoft anything, and it doesn't harm anyone using Windows.
Further, there’s no point in hobbling a general purpose device anymore as those folks have moved on to tablets etc. The division between workstations and appliances is a good one imho. Mixing metaphors has a poor track record.
Normally I agree with this point of view, but file extensions don't make sense for what's probably the most common use-case: people clicking on a file, and waiting for it to do something.
If they get a mail attachment that's something like `week04.xlsx`, they aren't going to be right-clicking and opening in Excel, they're just going to click twice on it. The type of file doesn't really matter to them, they just want it to open in the right program. The extension probably just serves to confuse most users.