4 ms·
It's time to cook something! How about an omelette? You need to scramble the eggs first-- thankfully, there's a tunnel between your fridge and the scrambler. Yo
by pfraze 14y ago
It's time to cook something! How about an omelette? You need to scramble the eggs first-- thankfully, there's a tunnel between your fridge and the scrambler. You press the button, and 4 eggs roll into the bowl.
While that scrambles, it's time to chop vegetables. You'd like to do onions, but the tube from the fridge to the chopper only fits carrots and asparagus. Not great for an omelette, but good enough.
Time to cook. Unfortunately, your chopper is out of date, and it doesn't work with your pan model. The scrambler, well, it's actually a mixer and was only meant for cakes, so it goes directly into the oven.
So you put special bowls in the fridge, suck the scrambled eggs and vegetables back through the tubes, take the bowl out, store it on dropbox, and give your pan a link.
God, this sucks.
- ori_b 14y agoI'm not sure how this really addresses anything in the parent post. Sure, interoperability sucks, but surely you're not suggesting that the solution is to glom everything together into a single monolithic app that does everything? By all means, fix the fact that tools are painful when you want them to work together. Maybe unify a few of those communications tools.
- jdbernard 14y ago> Let me communicate with a unified UI and unified contacts. This was from the top comment. It is suggesting the solution is to glom everything together. I think the comment you are responding to is concurring with their parent comment by providing an illustration of the concerns raised.
- freehunter 14y agoI think a better example is how WebOS and Windows Phone handle communication. They treat communication like it's between two people, rather than between two applications. Text messages and Facebook messages are combined into one, so you can continue the conversation from anywhere. Facebook and Twitter posts are added together to show what the person is doing, rather than what accounts on disparate are doing. These aren't huge monolithic apps, they're more like feeds from services all tied to a single person. Both WebOS and Windows Phone allow you to combine multiple accounts for contacts together into one person. Basically, it shouldn't matter what service someone is using. What really matters to people is people. If someone is at their computer, they might want to use Facebook messenger. If they're away, they'll want to use text. Barring that, they might rather use email. The point is, someone shouldn't have to open the Facebook app, find they're not online, send a text only to wait for a response and assume they do or do not have their phone on them, then send an email. If they can do it with one app, the app telling them the best way to contact someone, it makes communication much easier. No one has gotten it right yet, but I feel WebOS and Windows Phone are closer than the traditional discrete applications.
- pfraze 14y agoNo, there just needs to be interoperation layers like file systems, sockets, stdio, etc. In the kitchen metaphor, it's your hands.