29 ms·
Excellent, this will surely cause no confusion with macOS executables.
by dmart 8y ago
Excellent, this will surely cause no confusion with macOS executables.
- ryannevius 8y agoI'm not sure how a .app TLD could be mistaken for a .app executable.
- sakuronto 8y agoYou severely overestimate the technical skill of the average user. And even people who know their way around computers rely heavily on patterns in order to identify relationships, so a strong pattern without an underlying relationship is, of course, going to lead to confusion.
- untog 8y agoThe average user has no idea that the .app file extension even exists. macOS does not expose it in Finder.
- gsich 8y agoAverage user is able to learn.
- JeremyBanks 8y agoReferring to Mac applications as "Mail dot app" is a thing that only geeks do in the first place.
- sam_goody 8y agoApple Finder (magnify glass in top right) by default will search both local executables on your computer, and (as a second best option) the net. If a user sees *.app in finder, they might be very well getting something they don't expect.
- hyder_m29 8y agoJust like .com and windows executables, eh?
- sinatra 8y agoJust like .com didn’t cause confusion with DOS and Windows .com executables.
- raimue 8y agoJust like .sh didn't cause confusion with the .sh extension for shell scripts.
- adtac 8y agoExcept, .sh means nothing in particular in Linux. It just so happens people use .sh for shell scripts.
- cat199 8y agoIt just so happens people unnecessarily use .sh for shell scripts.
- gsich 8y agoFiles vs. URLs. Windows-Users had it similar with .com.
- aussieguy123 8y agoevil.co/malware.app