3 ms·
>What Google wants to do is bridge that moat, essentially to allow applications to run inside emails, limited ones to be sure, but by definition the kind of thi
by bob_theslob646 9y ago
>What Google wants to do is bridge that moat, essentially to allow applications to run inside emails, limited ones to be sure, but by definition the kind of thing that belongs on the other side of the moat.
How is this bad?
I do not understand the hate?
If you do not like the product then move on.
I can see this working well on a mobile devices, not sure how it will work on other platforms, but I'm definitely open to giving it a shot.
The best part about this is if I don't like it I can always switch.
- ucaetano 9y ago> I do not understand the hate? Oh, the hate is just the new version of the ASCII ribbon against HTML email...
- PeterisP 9y agoThe problem is that in this scenario someone else (i.e. the sender) is choosing the product/application they want to run on my device in my app. Unlike a web page, where I (hopefully) intend to use it and "pull" the app, this is designing a system where arbitrary apps and interfaces can be pushed to me by others, often not with my best interests in mind. I don't want my email client to be part of such a system. If I want to follow the advice of "if you do not like the product then move on", then it's not sufficient for me to simply not use this feature in messages I send, this requires that messages I receive don't/can't use this feature.