4 ms·
While there are times where that quote applies, in the vast majority of cases, that's the programmer's cop-out upon discovering that the feature they thought wa
by paledot 6y ago
While there are times where that quote applies, in the vast majority of cases, that's the programmer's cop-out upon discovering that the feature they thought was done is in fact broken and obtuse, and they don't care to take the time to understand their customer.
I don't want my email client automatically attaching files from my computer, period. I don't care how well or poorly it displays that fact. There's no use case important enough to warrant that kind of intrusion.
- netsharc 6y agoImagine you want to send a few photos - currently stored on your disk - to your mom. File manager, select a few files, right click, "send via e-mail". Or a letter you're typing, to some company: in your word processor, File -> Send as E-Mail. For these features to be able to work, the email client would need to have an API so it can create an e-mail with attachments directly attached. Sure they're not important, but they're convenient. You might not like them, but hey am I glad you're not a product owner of a mail software.
- paledot 6y agoYes, of course you should be able to do that using an internal API. Maybe even an internal mailto: link, in the interest of interoperability. But no mail client should ever respect attachments requested by a mailto: link followed by a browser.