11 ms·
It's not about the touch screen, the UI, the hardware or "casual" vs "professional" users, but simply about the ability to create(!) and combine small specializ
by flohofwoe 5y ago
It's not about the touch screen, the UI, the hardware or "casual" vs "professional" users, but simply about the ability to create(!) and combine small specialized tools into something that's bigger than the sum of its parts.
The "walled garden app ecosystem" is exceptionally bad for this, and the UNIX shell is exceptionally good, but both are extremes. It's hard to imagine how a UNIX-like flexibility can be achieved inside an ecosystem that's optimized for passive media consumption and online shopping though.
- Glide 5y agoCounterpoint to this, is that I’ve seen people be reluctant to click where they are not reluctant to touch. That barrier is vital for people who did not grow up with tech to interact and experiment with it. Here’s one question: hover on focus vs click to focus? Hover makes sense if you think of the pointer as a finger.
- mhuffman 5y ago>That barrier is vital for people who did not grow up with tech to interact and experiment with it. Who are you talking about? Senior citizens? Or maybe people outside of the US in developing countries? Because anyone under 50 in the US has grown up around tech.
- gjsman-1000 5y agoDon't just assume that default. Remember more than 10% of the US still doesn't have internet, and a shocking portion of the US has smartphones as their only method of computing and would be dumbfounded at a PC.
- mhuffman 5y agoYeah, I don't buy that, unless you are talking about the Amish or someone willfully avoiding technology. And in that case, we are not really losing "future techies" are we? Regarding the smartphone point, again, you might be talking about elderly people or self-isolated people. Otherwise all people under 50 have used computers in their school classes and would not be dumbfounded at a PC.
- flohofwoe 5y agoThose are just different input paradigms that have evolved over time, one isn't inherently superior to the others. Cars have a much more difficult UX than kbd+mouse, touch, gamepad or (Wii-style) point-and-wiggle interfaces, yet the relative difficulty of driving a car for "technical" vs "non-technical" people rarely comes up in discussions.
- fallenhitokiri 5y agoThis is IMHO a really good point. Somewhere in between App Groups, Share Extensions and custom URL schemes I really hoped at some point we would see a way to make this happen. My wife is currently using Affinity and Adobe products to work on illustrations. It works mostly the same for her as on her Mac. She does not care about small, specialised tools, she wants one app that does everything she needs. The iPad is doing a great job running those apps. I am not sure how many users (outside of the ones who got used to it) want UNIX-like flexibility vs "give me an app that does everything I need". If the later group keeps getting larger the walled garden approach to apps might actually work.
- vladvasiliu 5y ago> I am not sure how many users (outside of the ones who got used to it) want UNIX-like flexibility vs "give me an app that does everything I need". If the later group keeps getting larger the walled garden approach to apps might actually work. I think this is crux of the matter. Even outside the Apple ecosystem I see a tendency in people to not think about composing multiple tools but to look for an app that does everything. I'm talking about my colleagues, working in IT, but in a Windows environment. And on Windows there's PowerShell, which, although slow and to me not as flexible as bash, still allows one to do quite a lot of things. But people seem to see using it as a last resort, when there's absolutely no way of doing what they want by clicking around some window.
- emodendroket 5y agoIt's hard to remember all the arguments for a passel of command line utils. Discoverablility is much better for a GUI, and only someone who wishes to do something unusual or specialized will chafe against the limitations.
- vladvasiliu 5y agoI agree with you about discoverability, but in practice I find that tasks aren't completely new every time, there usually are common principles. With usage, you kinda get to know what is and isn't possible, even if you don't recall the precise details of each and every command. So you can look them up, knowing more or less what you're looking for. On Linux, `--help` usually... helps. Or there's the man. On Windows, the MS docs are usually usable to find things. Of course, it may not work 100% of the time, but I find it's a question of philosophy. I'm not a Windows user, so I generally approach it with a mentality of "it would be nice to be able to do this, let me check real quick if there's a way". I usually manage to not have to click around for two hours when I have to do something repetitive.
- jon-wood 5y agoAssuming enough apps expose functionality through it, Shortcuts is the bridge between walled garden apps and UNIX pipelines, and Apple made a very clever move in making Shortcuts how Siri discovers functionality.
- walterbell 5y agoIs there a way to version-control shortcuts and import/export them between devices, especially for those unwilling to use iCloud and associated keyring upload and content scanning?
- jon-wood 5y agoNot that I can see, but frankly if you’re not willing to use iCloud, give up on Apple devices because it’s what makes basically all the good stuff work. (This is not an invitation to get into yet another debate on recent events)
- walterbell 5y agoThere are enough good iPhone/iPad apps to use Apple devices with self-hosted storage (WebDAV, CalDAV, SMB/SFTP/DLNA, Git).
- linguae 5y agoI wholeheartedly agree; the app-centric model of today's desktop environments is the antithesis of the Smalltalk vision of composability. In an environment where everything is a live object, programmers can send messages to those objects. Thus, in the Smalltalk environment you end up with something even more powerful than Unix pipes and redirection. Now, Smalltalk provides the infrastructure for composability, but Smalltalk by itself doesn't provide us the full-fledged desktop environment and applications that users have come to expect; they would have to be implemented in Smalltalk. But where things get interesting in a Smalltalk-implemented desktop environment is that the live object environment is still there, leading to interesting possibilities. Imagine being able to control a word processing program through scripts written outside the word processor, without the word processing program itself having to implement something like Visual Basic for Applications? Imagine being able to control a spreadsheet with Smalltalk methods on cells instead of having to learn the spreadsheet's language or having to learn Visual Basic for Applications? The possibilities become even more intriguing when objects can interact with each other in ways that are far more general than Unix pipes. This is the desktop environment I dream of using, the unification of the ease of use of GUIs and the flexibility and programmability similar to the Unix shell. Oddly enough, in the mid-1990's Apple implemented a less-ambitious (but still very ambitious for its time) version of this vision known as OpenDoc (https://en.wikipedia.org/wiki/OpenDoc https://en.wikipedia.org/wiki/OpenDoc). There are some wonderful videos at https://www.youtube.com/watch?v=oFJdjk2rq4E https://www.youtube.com/watch?v=oFJdjk2rq4E (a three minute summary) and at https://youtu.be/2FSFvEIpm5o https://youtu.be/2FSFvEIpm5o (a 50-minute demo). OpenDoc was released in 1996, if I recall correctly, and there were some applications written with OpenDoc, most notably the CyberDog web browser (https://en.wikipedia.org/wiki/Cyberdog https://en.wikipedia.org/wiki/Cyberdog). However, once Apple bought NeXT in late 1996, Apple committed itself to building its next-generation operating system on NeXT, which had its own collection of object-oriented APIs. The cancellation of OpenDoc led to this famous spat during WWDC 1997 when a disgruntled developer questioned Steve Jobs on Apple's decision to cancel OpenDoc (https://www.youtube.com/watch?v=oeqPrUmVz-o https://www.youtube.com/watch?v=oeqPrUmVz-o). Why was OpenDoc cancelled? One can argue that OpenDoc's cancellation was due to Apple needing to have a tight focus during its very vulnerable period in 1997. The proof is in the pudding: mid-1990's Apple before the return of Steve Jobs was an unfocused beacon that was able to produce many interesting technological demos (the Dylan programming language, SK8, OpenDoc), but there was no single coherent vision. The Taligent and Copland projects, which strove to replace the classic Mac OS with then-modern underpinnings, were disasters. OpenDoc was just one out of the many, sometimes competing, visions that Apple had during this time. Steve Jobs was able to turn around Apple's fortunes by having Apple focus on one vision for the Mac. However, another way of looking at the cancellation of OpenDoc is that its success would have completely upended the software industry. Instead of software vendors selling apps, software vendors would sell components, which users can integrate to create custom workflows. While I believe that this would have led to a lot of flexibility and user-empowerment, OpenDoc would have also been seriously challenged by major software vendors like Microsoft and Adobe, whose empires were built on selling large, proprietary software packages. They were not going to give up their moats without a fight. Still, I dream of the modern realization of component-based software, and it's something I've been thinking a lot about for the past few years.
- tomjen3 5y agoThe Unix shell was exceptionally good for its time. Powershell, IMHO, go it right by not sending strings but objects around. This gets you around the issue of spaces and means you can send more than one value. I haven't been able to play with the shortcuts functionality because I don't have an iPhone, but if it is what I think it is it, it is a powerful tool to do things with. We shouldn't fail to acknowledge that most, if not all, spend more time consuming than creating. Then you have the group that isn't served with something as powerful as a real computer. My grandparents would be much better served with an iPad instead of a computer, since all they need is a browser and a system to do video calls.
- flohofwoe 5y agoAnd that's exactly why the "great unification" doesn't make sense.
- amelius 5y agoiOS is also great as a software copy protection scheme. You can't have that in an open OS without compromises.
- amelius 5y agoIt's basically like DRM at the device level.
- simonh 5y agoAre Windows, Linux and MacOS really better platforms for lots of tasks, performed by mainstream and professional users for daily tasks, principally because they are used to pipe text between command line tools? This is delusional. I have good news, iOS user's productivity woes are solved. Using iSH you can pipe text between command line tools all day every day. Finally the power of the iPad is unleashed!
- flohofwoe 5y agoThe text piping is just one small part and not the most important, instead its about sharing and processing any type of data with small tools that can be combined like lego blocks (and if there isn't the right lego block for a problem you can build your own). The UNIX shell is just one very primitive implementation of that idea (and yet it's still much more powerful than anything we have on iOS or Android). In the "mobile app ecosystem", each application is more or less an island. It would be possible to achieve something similar on iOS/Android devices, but the entire "value proposition" of walled garden ecosystems isn't compatibel with this idea of open and creative computing. One prerequisite is that I actually own my device and can do anything I want with it, without the platform owner getting in the way.
- simonh 5y agoOn iOS now we have all the same interchange mechanisms between applications we have on desktop. Decent file management, rich content cut-and-paste, side-by-side applications. Share sheets are great. The main limitation is the interaction model, and that's just down the the mechanics of touch interfaces. Firstly fingers are imprecise big fat squishy blobs. Secondly the tablet form factor doesn't afford a large physical keyboard. These are the impediments and they're just facts of the form factor. the new multi-tasking interface in iPadOS looks like a great step forward, but it's always an issue.
- imiric 5y agoThis must be sarcasm... There's much more to being productive with an OS than piping text on the command line in an emulated and highly restricted environment. The command line is a management interface to the OS, not a sandbox you get to play in with the tools the manufacturer allows you to. I would like seamless interoperability between CLI and GUI apps, a unified file system, the ability to run virtual machines, containers[1] or maybe just nginx[2]. And then you have the usability issues of the iPad(OS) like external displays being mirrored only, or only recently being able to actually access files from a USB drive... The iPad is a great media consumption device, that has some limited professional use (art, video editing maybe), but let's not fool ourselves that it's anywhere near being a replacement for a fully functional computer. [1]: https://github.com/ish-app/ish/issues/63 https://github.com/ish-app/ish/issues/63 [2]: https://github.com/ish-app/ish/issues/137 https://github.com/ish-app/ish/issues/137
- adrusi 5y agoThat's just it. The future is very likely most people using iPad-like devices. They will need some kind of keyboard, so I'm not sure it's going to be tablets mostly, but the software will resemble that of smartphones. But no desktop operating systems are well suited to being used primarily by professionals, not even Linux. The desktop paradigm is fine, but it was designed with the idea of making computers more accessible, and it inhibits composing different pieces of software together, which is what a professional-first operating system should optimize for. I'm not sure how viable a good professional OS is. It would arguably require graphical software vendors through the biggest design paradigm shift in their history, to serve a relatively small market. The transition to the desktop paradigm wasn't as demanding — you just switched from taking control of the graphics hardware and controlling the entire screen to doing basically the same thing, just with the OS as a proxy so that you're rendering to a smaller rectangle. Composable graphical interfaces means abandoning the idea of having complete control over your rectangles.
- f6v 5y ago> But no desktop operating systems are well suited to being used primarily by professionals I love macOS and I’m a professional. I mean, I get paid for what I do. I’m a professional, right?
- adrusi 5y agoWell it's roughly as good as your other two options, none of which are terrible. I'm not trying to insult the people who use.. literally any operating system available today. But surely you can imagine ways that macOS could be better suited to your needs. Why (to give an example that's easy to explain briefly, not necessarily the most important one) are the various things you have open organized primarily by which application can open them, instead of which task they're relevant to? You can organize your browser tabs by task by using multiple windows, but why can't those windows hold anything relevant to the task they represent except browser tabs? Why can't you have your terminal and text editor grouped with your webpages? It's because less sophisticated users expect each window to belong to exactly one "application," and because software vendors assume that their job is to make self contained "applications," and not composable graphical components.
- zepto 5y ago> The "walled garden app ecosystem" is exceptionally bad for this, and the UNIX shell is exceptionally good, but both are extremes. Very true. > It's hard to imagine how a UNIX-like flexibility can be achieved inside an ecosystem that's optimized for passive media consumption and online shopping though. Unix-like flexibility is also extremely insecure and easy to screw up. It’s fairly obvious that the App Store ecosystem can and is becoming increasingly flexible. Things like shortcuts and safari extensions are obvious examples. Unix-like flexibility will likely never come to iOS, nor should it, but it’s easy to imagine a steady drumbeat of easy to use managed points of flexibility that ultimately provide 80% of what people use Unix-flexibility for but without the insecurity or brittleness. It’s not so easy to imagine how ease of use, security and robustness can be retrofitted to unix any other way. Remember iOS is Unix. It’s just a matter of what they build for end users.
- ratww 5y ago> the ability to create(!) and combine small specialized tools into something that's bigger than the sum of its parts Funny, the possibility to do that currently exists in a walled garden, for audio apps: https://audiob.us https://audiob.us . This is used by creators and live performers, exclusively. I don't think anyone uses applications in this ecosystem for "consumption" purposes. The problem was never was the current OSs, it was just about app makers not willing or not knowing how to collaborate amongst themselves. It was also never about open vs closed, since AudioBus is proprietary and 99% of the apps that support it are also proprietary. The thing about UNIX pipes is that they use plain text. AudioBus uses audio. Those are two things that naturally impose limitations. Developers seem ok with those "natural limitations" but whenever you want to impose limitations to something else you immediately get pushback. You wouldn't be able to do that in a business CRUD app for example. The amount of wheel-reinvention is too big on those, compared to audio/video/unix-tools.
- musicale 5y agoYou can automate and glue iOS apps together using Shortcuts, script them with Scriptable or Pythonista, etc.. It's somewhat analogous to using Automator and/or macOS' Open Scripting Architecture.
- _fat_santa 5y agoYeah but to even try and compare that to the power of the UNIX shell is silly.