3 ms·

> But I think "real work" is a bad criticism. For the third time, "real work" is not the actual criticism. It's inexact language used by a frustrated person, a

by ohazi 7y ago

> But I think "real work" is a bad criticism. For the third time, "real work" is not the actual criticism. It's inexact language used by a frustrated person, and you're taking it literally when you shouldn't be. > If the kind of work it can do is the problem with the iPad Nobody is saying this. The kind of work you can already do on an iPad is great. We're just frustrated because with a little bit of thought at the operating system level, the device would also be capable of doing a lot of other things well, without any sacrifice to the all of the existing apps and workflows that make the device popular.

jader201 7y ago
> We're just frustrated because with a little bit of thought at the operating system level, the device would also be capable of doing a lot of other things well, without any sacrifice to the all of the existing apps and workflows that make the device popular. I wonder how true this really is? Removing the need for files or composability was a “feature” of the iPad from the beginning. To simplify things. For example, add in more native support for a real file system from the beginning, and many of the apps that were designed without a file system /composability in mind now is designed completely differently, and may no longer work as well/simply as the current users experience them today. I don’t pretend to have a crystal ball and know how things “might’ve been”, but I think saying that by supporting a native file system/composability, things would be “the same but better” may be a bit naive.
brianpan 7y ago
You're saying that the iPad could do these additional Mac-like things with a few tweaks or additions. I'm saying the sweet spot is in the other direction. You want it to do more (essentially 'real work'). The device that's doing better is the one that's just like it, but is smaller and does less. That's why "real work" is a bad criticism. I put it in quotes, because yes, I read what you wrote and you're frustration. It sucks but I don't think the iPad is ever going to be that. It would be better for you, but it won't make the iPad a more popular product.

by ohazi 7y ago

jader201 7y ago

> We're just frustrated because with a little bit of thought at the operating system level, the device would also be capable of doing a lot of other things well, without any sacrifice to the all of the existing apps and workflows that make the device popular. I wonder how true this really is? Removing the need for files or composability was a “feature” of the iPad from the beginning. To simplify things. For example, add in more native support for a real file system from the beginning, and many of the apps that were designed without a file system /composability in mind now is designed completely differently, and may no longer work as well/simply as the current users experience them today. I don’t pretend to have a crystal ball and know how things “might’ve been”, but I think saying that by supporting a native file system/composability, things would be “the same but better” may be a bit naive.

brianpan 7y ago

You're saying that the iPad could do these additional Mac-like things with a few tweaks or additions. I'm saying the sweet spot is in the other direction. You want it to do more (essentially 'real work'). The device that's doing better is the one that's just like it, but is smaller and does less. That's why "real work" is a bad criticism. I put it in quotes, because yes, I read what you wrote and you're frustration. It sucks but I don't think the iPad is ever going to be that. It would be better for you, but it won't make the iPad a more popular product.