Sorry to reply to my own post; but here is a citation for Safari beats Chrome, which is just as relevant as Chrome beats Edge; since both Safari and Edge are single-platform browsers:
That's why iOS' "kludgy" Back Button at the top left is apparently far superior to what Android does. In iOS the "button" says "Back to Safari", "Back to Mail", etc., so there is ZERO ambiguity as to what will happen when tapping it.
... and totally unreachable using your thumb without stretching it... or using two hands (unless you want to risk dropping your slippery expensive iDevice). Yeah, FAR superior....
Why don't just complain about the font size and color while you're at it; since you apparently don't have any SUBSTANTIVE arguments to make.
People want to be able to run whatever software they like.
Some people obviously do. But iOS is also highly successful.
But, there's a difference. Actually two:
1. the iOS App Store is likely VAST compared with the WIndows 10 App Store. That makes a VAST difference.
2. People who own iPhones/iPads understand the reasoning behind, and are used to, the App Store Restriction (which really isn't a restriction anymore, since iOS 8).
I once read that automatic takeoff is possible but unwanted, as airlines don't want a plane taking off if there's no pilot on board who can manage a good takeoff.
This has also been true for Microsoft's Windows interface standards for I-don't-know-how-long. More specifically, anything that you can do with a mouse has to be doable from the keyboard. The right click context menus are generally items pulled from the app's main menu system, accessible via the "Alt-" key combinations.
And yes, I've seen my share of mouse-centric apps - especially in Excel - which violate those standards. But that is a fault in the apps, not the OS.
I agree about the "App vs. OS" violation-thing.
Not to turn this into an OS-War (at all!); but I always liked the fact that OS X/macOS even has a "Keyboard Shortcut EDITOR", where you can define and bind keystrokes either App or System-Wide, to Menu Commands. I'm surprised that Windows has never really copied that Mac feature. Just like I've always been surprised that Apple has never copied the Windows Audio "Mixer". That's really quite nice to have once in awhile.
If it's "Far from autonomous", they shouldn't be calling it autopilot.
Seems like an appropriate name, actually. A plane on autopilot also just keeps course and altitude, but doesn't fly around storms, or start an automatic landing procedure when fuel is running low.
If you'd like to try an experiment and you work in a reasonably large office, pick 10 of your co-workers at random and ask them to explain to you what autopilot on a plane does. I bet that at least 7 out of 10 will claim that autopilot can land the plane and possibly other things that it doesn't really do. Given how the average person probably doesn't actually understand the name correctly, it wasn't a good choice.
Actually, some Autopilot systems CAN land. I think the Airbus 380 and Boeing 777 both have Autopilots that can (and often do) land the plane.
And in fact, they are used routinely when conditions are such that a pilot would have difficulty landing manually. So, in the case of airplanes, the Autopilot is actually BETTER than a human "driver".
And when you engage autopilot in the left lane of a 5 lane freeway? What, it's supposed to signal and get over 4 lanes before pulling to the side of the road (where the shoulder may be closed or nonexistent alongside a concrete wall or rock embankment and stopping may be forbidden by law) and stopping?
Actually, I would expect the car to use its mapping to realize it is in the left-most lane, and its vision system to determine whether there is a sufficient shoulder on the LEFT side to pull over safely.
And if there is no sufficient left-hand shoulder, then yes, I expect it to be able to use its driving skills to navigate safely to the right-most lane, flip on the emergency flashers, and attempt to pull-off on the right side. If it still couldn't raise the driver, and can't pull-over, the car should enter "limp home", call 911 (if Tesla's can do that) and continue at minimum speed (e.g. 40 mph) in the far-right lane until it can safely exit or pull-over.
Yes, this should be within the car's capabilities at this point.
What else would you suggest? It just disable the Autopilot and shut off the car in whatever lane it happens to be in?
Since this would be a bona-fide emergency, any laws against pulling-over would likely not apply.
Why would the car continue to operate for 37.5 minutes of the trip if the driver didn't have his hands on the steering wheel? If that's a requirement, why didn't the car just pull over and shut off? It seems like Tesla failed to implement some common sense safety protocols here.
Because they trusted that the owner of an $80,000 car had at least some minimal intelligence and even if the driver had blind trust in the car, that when the car says "put your hands on the wheel and pay attention", that the driver would listen.
Yet this driver has demonstrated that people are about as dumb as you think they can be, so now they've implemented a 3 strikes policy that disabled autopilot after 3 reminders.
"Open With" does appear under "File" in the menu at the top of the screen, when Finder is active. There may be some other example of Apple breaking their own rules, though.
Sorry. I was at work, away from my Mac.
Thanks for the correction.
And yes, there are other examples; but I've already embarrassed myself once today, thank you!
Either that or they're going to start publishing a newspaper that contains news aimed at both Trump supporters and everyone else, making 50% of it fake news. Hence "mixed reality"
Their Catchphrase: "Nothing but the Alternate Facts"
Can you really blame him? iSheeps are not known for their intelligence. So yes, a back button or a menu would explode their brains.
Ya know, it really doesn't do you any favors to attempt to insult others' intelligence, while creating such unintelligent blunder like saying "iSheeps".
Not having a dedicated back button (even if it were part of the touch screen) is what drives me crazy about the iPhone. I do think this was a mistake. The notion of "back" makes perfect sense. Even outside of Android's Intent-app-mixing UI. I want to go back to where I was. Imagine not having a back button on your browser!
That's probably why iOS now has a Back Button.
But unlike Android's it has a consistent, and "Titled" behavior. Actually, there are two types of Back-Buttons in iOS. When down in a sub-view inside of an App, there is a " Level-Above" button at the top-left of the screen that let's you "pop-up" to the previous level in the same App. If you are already at the Top-Level in an App, iOS places a "Back to (previousAppName)" Button (more like a "Link"), again at the top-left of the screen.
So there you go: All the functionality you'd want in a Back Button, with none of the Ambiguity of Android's implementation.
Doesn't work very well, especially when you have a case on (which you MUST, if you want the darn expensive thing to retain any resell value). Either it does it half-way and snaps back, or doesn't register the wipe correctly at all (and depending on the actual UI displayed, might do something destructive).
Having a separate and easily accessible 'back' soft button at the bottom (like most Android devices have) is both simpler to activate, and more logical and obvious to use (doesn't require any 'discovery' at all, and no 'reaching' to the opposite of the screen to activate it).
Except for that whole teaching about "There's no way to really know what that button will do at any one time" thing...
The app drawer in Android is part of the launcher, which can be replaced by the user. Different launchers have different behavior, including how they decide to sort apps in the app drawer.
The double-click on the single IOS button and the swipe to close a running app are NOT obvious. I had several iPhone users complain about how slow and sluggish their iPhone would run because they had no idea that they had tons of running programs open and if they did how they could close them.
If I understand correctly, "Suspended" Apps in iOS aren't REALLY running. They are "in stasis", with a "Poster Screen" the only thing actually consuming resources.
I completely disagree. I've been impressed with some of the Samsung and Motorola phones hardware. But every time I try to use one, I have no idea where most of the features and functions are. I think the Android UI are collectively terrible. Something as simple as finding the apps can take multiple taps. Keep in mind, I'm extremely technology literate by any objective measure. I've designed and implemented user interfaces for a variety of control systems. I've trained end-users in how to use technically advanced systems. If it's hard for me to 'find stuff', then it's surely difficult for a large portion of the potential user base. Contrast that with iOS. My 90+ grandmother struggled to do anything with PC/laptops that she was shown repeatedly how to operate. We got her an iPad, and she used it almost everyday for hours with relatively few questions. I've had an iPhone since gen. 1 and the simplicity of the iOS UI has been consistent enough for my kids to have grown up using it from age 2. Again, contrast that with Android devices we've had access to, and all off us struggle to find basic functions. The Android back button is a perfect example. It's context-sensitive, but without any visual clue as to what the context is. Sometimes it's back in an app, sometimes it's back to a different app, sometimes it's back to the previous screen, sometimes it's back to the app selection screen, and occasionally it's even back to the home screen. All without any indication about which one is going to happen when you push the button. Maybe if I used it everyday for a few weeks, I'd get used to where everything is, but there is no such learning curve with iPhone/iOS.
That's why iOS' "kludgy" Back Button at the top left is apparently far superior to what Android does. In iOS the "button" says "Back to Safari", "Back to Mail", etc., so there is ZERO ambiguity as to what will happen when tapping it.
And I believe the Apple Human Interface Guidelines state that Contextual Menus (which have existed in MacOS since System 8.1, IIRC) should contain ONLY Items that are accessible in other places. However, (or course) Apple themselves breaks that "rule" whenever it is convenient, like in the Finder, where Right-Clicking on a Document Icon will give you a Contextual Menu that includes "Open WIth...". I haven't scoured the Finder's Menu Bar; but I'm pretty sure that command doesn't exist up there.
They still don't (or do, depending on your perspective) - the command ("Splat") key (also seen on the Mac Plus keyboard) is the equivalent of Ctrl for Macs. And is the same key if you're using a USB or Bluetooth keyboard, just with the label changed.
Wrong.
Although several Command-Key Keyboard Shortcuts got translated to Control-Key Keyboard Shortcuts when Microsoft stole them from macOS, the Mac has always recognized the Command and Control Keys separately.
Intuitive really doesn't exist in the computing world. It's all about familiarity.
How are you meant to know that moving the plastic thing with a wheel corresponds to moving pixels on a screen? Or caressing the touchpad on your laptop. You only know about the F/J keys because you were told (in some way).
The Mac and PC HIDs are sufficiently different enough that PC people really struggle with Mac keyboard/Mouse shortcuts and use (and vice-versa).
Actually, the hardest thing to get used to going back and forth between Windows and macOS is to remember CONTROL-C/X/V/Z vs. COMMAND-C/X/V/Z, depending on which system you are using at any one time.
Slashdot Mirror
Used to be beta testers were the ones getting paid.
But then you suckers decided to support companies like Apple and Google with their shit release and testing practices.
Ever hear of "Fuzzing"?
There is only so much one can learn from test scripts and even a limited pool of human alpha and beta testers.
To really find MOST (nothing ever finds ALL) of the most obscure errors, nothing beats a huge base of random user setups and user actions..
Sorry to reply to my own post; but here is a citation for Safari beats Chrome, which is just as relevant as Chrome beats Edge; since both Safari and Edge are single-platform browsers:
See, esp. Footnote 2.
https://daringfireball.net/201...
Safari beats Edge on the latest versions of macOS.
And I'm DAMN sure it beats resource-hogging Chrome.
That's why iOS' "kludgy" Back Button at the top left is apparently far superior to what Android does. In iOS the "button" says "Back to Safari", "Back to Mail", etc., so there is ZERO ambiguity as to what will happen when tapping it.
... and totally unreachable using your thumb without stretching it... or using two hands (unless you want to risk dropping your slippery expensive iDevice). Yeah, FAR superior....
Why don't just complain about the font size and color while you're at it; since you apparently don't have any SUBSTANTIVE arguments to make.
Are Darwin-based OSes, such as macOS and iOS, affected by this?
And if so, any information as to whether it is being, if has been, patched in those OSes?
...(and 1985), And they want their Interactive Titles "The Case of the Missing Yolks" and "Eat or Be Eaten" back.
http://www.firesigntheatre.com...
http://www.gamesetwatch.com/20...
contact censorship should not be part of an app store if any thing apple can have an adults only one and and an open politics ones
In Your Not So Humble Opinion, of course.
Which part of "People who own iPhones/iPads understand the reasoning behind, and are used to, the App Store Restriction" didn't you understand?
Question: Doesn't "Freedom of Choice" INCLUDE the "right" to join a "Members Only" Club? Afterall, no one FORCES you to buy an iPhone/iPad.
People want to be able to run whatever software they like.
Some people obviously do. But iOS is also highly successful.
But, there's a difference. Actually two:
1. the iOS App Store is likely VAST compared with the WIndows 10 App Store. That makes a VAST difference.
2. People who own iPhones/iPads understand the reasoning behind, and are used to, the App Store Restriction (which really isn't a restriction anymore, since iOS 8).
I once read that automatic takeoff is possible but unwanted, as airlines don't want a plane taking off if there's no pilot on board who can manage a good takeoff.
I can't say as I blame them!
This has also been true for Microsoft's Windows interface standards for I-don't-know-how-long. More specifically, anything that you can do with a mouse has to be doable from the keyboard. The right click context menus are generally items pulled from the app's main menu system, accessible via the "Alt-" key combinations.
And yes, I've seen my share of mouse-centric apps - especially in Excel - which violate those standards. But that is a fault in the apps, not the OS.
I agree about the "App vs. OS" violation-thing.
Not to turn this into an OS-War (at all!); but I always liked the fact that OS X/macOS even has a "Keyboard Shortcut EDITOR", where you can define and bind keystrokes either App or System-Wide, to Menu Commands. I'm surprised that Windows has never really copied that Mac feature. Just like I've always been surprised that Apple has never copied the Windows Audio "Mixer". That's really quite nice to have once in awhile.
If it's "Far from autonomous", they shouldn't be calling it autopilot.
Seems like an appropriate name, actually. A plane on autopilot also just keeps course and altitude, but doesn't fly around storms, or start an automatic landing procedure when fuel is running low.
If you'd like to try an experiment and you work in a reasonably large office, pick 10 of your co-workers at random and ask them to explain to you what autopilot on a plane does. I bet that at least 7 out of 10 will claim that autopilot can land the plane and possibly other things that it doesn't really do. Given how the average person probably doesn't actually understand the name correctly, it wasn't a good choice.
Actually, some Autopilot systems CAN land. I think the Airbus 380 and Boeing 777 both have Autopilots that can (and often do) land the plane.
And in fact, they are used routinely when conditions are such that a pilot would have difficulty landing manually. So, in the case of airplanes, the Autopilot is actually BETTER than a human "driver".
I think that Auto Takeoff is also possible, IIRC.
http://www.askcaptainlim.com/f...
https://en.wikipedia.org/wiki/...
And when you engage autopilot in the left lane of a 5 lane freeway? What, it's supposed to signal and get over 4 lanes before pulling to the side of the road (where the shoulder may be closed or nonexistent alongside a concrete wall or rock embankment and stopping may be forbidden by law) and stopping?
Actually, I would expect the car to use its mapping to realize it is in the left-most lane, and its vision system to determine whether there is a sufficient shoulder on the LEFT side to pull over safely.
And if there is no sufficient left-hand shoulder, then yes, I expect it to be able to use its driving skills to navigate safely to the right-most lane, flip on the emergency flashers, and attempt to pull-off on the right side. If it still couldn't raise the driver, and can't pull-over, the car should enter "limp home", call 911 (if Tesla's can do that) and continue at minimum speed (e.g. 40 mph) in the far-right lane until it can safely exit or pull-over.
Yes, this should be within the car's capabilities at this point.
What else would you suggest? It just disable the Autopilot and shut off the car in whatever lane it happens to be in?
Since this would be a bona-fide emergency, any laws against pulling-over would likely not apply.
...not to mention using incorrect verb-tenses.
Why would the car continue to operate for 37.5 minutes of the trip if the driver didn't have his hands on the steering wheel? If that's a requirement, why didn't the car just pull over and shut off? It seems like Tesla failed to implement some common sense safety protocols here.
Because they trusted that the owner of an $80,000 car had at least some minimal intelligence and even if the driver had blind trust in the car, that when the car says "put your hands on the wheel and pay attention", that the driver would listen.
Yet this driver has demonstrated that people are about as dumb as you think they can be, so now they've implemented a 3 strikes policy that disabled autopilot after 3 reminders.
This is (one reason) we can't have flying cars...
"Open With" does appear under "File" in the menu at the top of the screen, when Finder is active. There may be some other example of Apple breaking their own rules, though.
Sorry. I was at work, away from my Mac.
Thanks for the correction.
And yes, there are other examples; but I've already embarrassed myself once today, thank you!
Either that or they're going to start publishing a newspaper that contains news aimed at both Trump supporters and everyone else, making 50% of it fake news. Hence "mixed reality"
Their Catchphrase: "Nothing but the Alternate Facts"
Can you really blame him? iSheeps are not known for their intelligence. So yes, a back button or a menu would explode their brains.
Ya know, it really doesn't do you any favors to attempt to insult others' intelligence, while creating such unintelligent blunder like saying "iSheeps".
The plural of "sheep" is... "sheep".
Moron.
Not having a dedicated back button (even if it were part of the touch screen) is what drives me crazy about the iPhone. I do think this was a mistake. The notion of "back" makes perfect sense. Even outside of Android's Intent-app-mixing UI. I want to go back to where I was. Imagine not having a back button on your browser!
That's probably why iOS now has a Back Button.
But unlike Android's it has a consistent, and "Titled" behavior. Actually, there are two types of Back-Buttons in iOS. When down in a sub-view inside of an App, there is a " Level-Above" button at the top-left of the screen that let's you "pop-up" to the previous level in the same App. If you are already at the Top-Level in an App, iOS places a "Back to (previousAppName)" Button (more like a "Link"), again at the top-left of the screen.
So there you go: All the functionality you'd want in a Back Button, with none of the Ambiguity of Android's implementation.
Doesn't work very well, especially when you have a case on (which you MUST, if you want the darn expensive thing to retain any resell value). Either it does it half-way and snaps back, or doesn't register the wipe correctly at all (and depending on the actual UI displayed, might do something destructive).
Having a separate and easily accessible 'back' soft button at the bottom (like most Android devices have) is both simpler to activate, and more logical and obvious to use (doesn't require any 'discovery' at all, and no 'reaching' to the opposite of the screen to activate it).
Except for that whole teaching about "There's no way to really know what that button will do at any one time" thing...
The app drawer in Android is part of the launcher, which can be replaced by the user. Different launchers have different behavior, including how they decide to sort apps in the app drawer.
The Google Now Launcher is the default on stock Android devices, with the Pixel Launcher being installed by default on the Pixel line of phones. Plenty of non-Google alternative launchers exist, including Nova Launcher, ZenUI Launcher (by ASUS), and even Arrow Launcher, made by Microsoft.
No WONDER no one knows how to navigate in Android! It's nothing more than an inconsistent clusterfuck!
The double-click on the single IOS button and the swipe to close a running app are NOT obvious. I had several iPhone users complain about how slow and sluggish their iPhone would run because they had no idea that they had tons of running programs open and if they did how they could close them.
If I understand correctly, "Suspended" Apps in iOS aren't REALLY running. They are "in stasis", with a "Poster Screen" the only thing actually consuming resources.
I completely disagree. I've been impressed with some of the Samsung and Motorola phones hardware. But every time I try to use one, I have no idea where most of the features and functions are. I think the Android UI are collectively terrible. Something as simple as finding the apps can take multiple taps. Keep in mind, I'm extremely technology literate by any objective measure. I've designed and implemented user interfaces for a variety of control systems. I've trained end-users in how to use technically advanced systems. If it's hard for me to 'find stuff', then it's surely difficult for a large portion of the potential user base. Contrast that with iOS. My 90+ grandmother struggled to do anything with PC/laptops that she was shown repeatedly how to operate. We got her an iPad, and she used it almost everyday for hours with relatively few questions. I've had an iPhone since gen. 1 and the simplicity of the iOS UI has been consistent enough for my kids to have grown up using it from age 2. Again, contrast that with Android devices we've had access to, and all off us struggle to find basic functions. The Android back button is a perfect example. It's context-sensitive, but without any visual clue as to what the context is. Sometimes it's back in an app, sometimes it's back to a different app, sometimes it's back to the previous screen, sometimes it's back to the app selection screen, and occasionally it's even back to the home screen. All without any indication about which one is going to happen when you push the button. Maybe if I used it everyday for a few weeks, I'd get used to where everything is, but there is no such learning curve with iPhone/iOS.
That's why iOS' "kludgy" Back Button at the top left is apparently far superior to what Android does. In iOS the "button" says "Back to Safari", "Back to Mail", etc., so there is ZERO ambiguity as to what will happen when tapping it.
PERFECT example!
And I believe the Apple Human Interface Guidelines state that Contextual Menus (which have existed in MacOS since System 8.1, IIRC) should contain ONLY Items that are accessible in other places. However, (or course) Apple themselves breaks that "rule" whenever it is convenient, like in the Finder, where Right-Clicking on a Document Icon will give you a Contextual Menu that includes "Open WIth...". I haven't scoured the Finder's Menu Bar; but I'm pretty sure that command doesn't exist up there.
They still don't (or do, depending on your perspective) - the command ("Splat") key (also seen on the Mac Plus keyboard) is the equivalent of Ctrl for Macs. And is the same key if you're using a USB or Bluetooth keyboard, just with the label changed.
Wrong.
Although several Command-Key Keyboard Shortcuts got translated to Control-Key Keyboard Shortcuts when Microsoft stole them from macOS, the Mac has always recognized the Command and Control Keys separately.
Intuitive really doesn't exist in the computing world. It's all about familiarity.
How are you meant to know that moving the plastic thing with a wheel corresponds to moving pixels on a screen? Or caressing the touchpad on your laptop. You only know about the F/J keys because you were told (in some way).
The Mac and PC HIDs are sufficiently different enough that PC people really struggle with Mac keyboard/Mouse shortcuts and use (and vice-versa).
Actually, the hardest thing to get used to going back and forth between Windows and macOS is to remember CONTROL-C/X/V/Z vs. COMMAND-C/X/V/Z, depending on which system you are using at any one time.