10 ms·
... I want to stress how important is the concept of simplicity, not just in graphical UIs, but also in UIs designed for programmers. I've always felt sad that
by pavlov 10y ago
... I want to stress how important is the concept of simplicity, not just in graphical UIs, but also in UIs designed for programmers.
I've always felt sad that this dichotomy is so strong in our industry. There are graphical tools for proles and then there are text-based tools for programmers, and never the two shall mix.
It didn't have to be this way. Smalltalk was an integrated graphical system for both programmers and users already 40 years ago. Something like the Smalltalk class browser with visual editing of live code would feel revolutionary even today compared to most of the systems we have.
But we're seemingly stuck with another '70s approach, that of Unix: streams of plain text, UIs based on undiscoverable and inconsistent command line argument arrays, all glued together with a spider's web of incredibly fragile string-replacement tools like shell scripts and templates.
- PaulHoule 10y agoOne area I have been looking at are "business rules" systems which, I think, won't go mainstream until they get facile enough that you can do more ordinary programming tasks with them. A core idea of them has been that the things that make coding hard for business people are different from the things that make coding hard for programmers and I don't believe that at all. (If programmers can't stand to use it to do simple things, how do you expect business people to go anywhere with it?)
- zwerdlds 10y agoIMO, K2 really has a good entry in the business rules engine problem with a solid, kinda-accessible UI. I am confident, having scoped many a project, that often the case is the stakeholder not quite knowing what they want. A good UI then is a good step forward to allowing the stakeholder to iterate on refining their interpretation of their own problem.
- roflc0ptic 10y agoI just went to the k2 website and it looks like I can't get access to the software without buying it? Bummer. I set up a request asking for a demo, but dealing with sales reps is such a PITA. I am in the market for a decent BPM that doesn't want to charge crazy amounts and forcing us to buy support (I'm looking at you, Bonitasoft). Right now we're using Activiti it is awful. It also seems like the least bad of the FOSS offering.
- zwerdlds 10y agoI only dealt with K2 in '10, so things may have changed, but even in the sales process they had engineers on the line. One of the better 'sales' experiences IMO. Oh, and if you are genuinely interested in trying K2 before buying, I'll be they'd set up a VM for you to remote into. They did for me in '10.
- EdHominem 10y agoOverly "helpful" systems are adopted by people who don't bother to learn the domain before they make sweeping business decisions. And, strangely, once people do know the domain the last thing they want is a kindergarten toy where they program by clicking through menus. Imagine a novelist writing by navigating right-click menus of phrases organized by "Prepositional phrases", "Snappy responses", etc. It's not that a GUI can't be helpful, it's that "GUI" isn't a synonym for helpful. If there's a problem that can be solved by looking at a map (perhaps dataflow through components) then yes, it'd be great to present that visually. The problem is that most of the people having this discussion know programming from movies like Hackers. They want a picture of an oil-tanker rolling over despite the fact that the code in question (theoretical code - never shown in the movie) wouldn't know what an oil tanker was, it'd simply react to one number changing by changing another. The meaning is all dependent on what platform it's installed on.
- PaulHoule 10y agoIt is not easy to make GUI systems that are easy to use. Back before people were used to reading help on the internet there used to be a brisk market in 1000 page books with titles like "How to use Microsoft Word". Closer to the domain my favorite example of malware is the ontology editor protoge. Every day I see freshers who are highly confused getting started with protoge who are then blown away with how easy it is to write an RDFS ontology in a few lines of Turtle with an ordinary text editor.
- IshKebab 10y agoAgreed. Mostly a result of "if I had to learn it so should you" and stuck-in-the-mud attitudes. Look at the Linux systemd / init debate. Despite the fact that sysvinit is clearly ancient, awful technology there are still people who have spend time learning it and don't want something better. Another example: bash. Clearly an awful awful language/shell but it sticks around because too many people can't admit that the thing they know is rubbish.
- zenlikethat 10y agoThere are lots of reasons people resisted systemd initially that had nothing to do with resisting learning a new system. Likewise with bash, what's the better alternative? And don't say fish. Just because it bills itself as such doesn't make it an improvement. All tools have some overhead to learning them.
- JdeBP 10y agoWe don't need to hypothesize an answer. We live in a world where we can see an answer, if we know our history. People decided almost 10 years ago that there was a better way to do certain things than use the Bourne Again shell, and switched to using the Debian Almquist shell. * http://unix.stackexchange.com/a/250965/5132 http://unix.stackexchange.com/a/250965/5132
- zenlikethat 10y agoInteresting bit of history, I had assumed the parent was complaining about bash interactive shells with the usual "they're hard to use for humans" position. The link suggests that the major gain of Debian Almquist was performance.
- philh 10y agoThis feels like bulverism: you've decided that people are wrong, and now you've come up with a fully general explanation for why they're wrong. https://en.wikipedia.org/wiki/Bulverism https://en.wikipedia.org/wiki/Bulverism If you ask people why they use bash, and why they don't like systemd, you get perfectly reasonable answers. (I'm not going to go into them here for obvious reasons.) You can't just dismiss these people as stick-in-the-muds.
- azernik 10y agoI'm actually okay with text-based systems; good UI can be implemented in that format too. For example, the principle of least surprise has clearly NOT been followed by lots of utilities in defining the "recursive" option - is it capital R or lowercase r? And do you use single-dash for long options or double-dash? And there are advantages to text-based UIs (scriptable, composable, copy-pastable) that I think would be hard to reproduce in graphical UIs.
- dredmorbius 10y agoArgument styles are themselves characteristics of systems. There's initial BSD-style arguments. Almost always single-dash and single-letter. Not entirely consistent. There's GNU-style arguments. While (usually) consistent with equivalent BSD-style, there are long args, given by double-dash and multi-character arguments. Then there are the utilities which eschew either. Single-dash multi-character args, random-character args, alternative delimiters. (dd is a special case: it's derived from the mainframe JCL data-dump command, and syntax.) Recognising these ontologies often helps. The fact that CLIs get incorporated into scripts gives really fucking strong incentive to upstream devs not to randomly change shit. It breaks fucking everything, and often will cause users (usually admins or coders themselves) to flee tools which practice this.
- azernik 10y agoAnd that's annoying from a UX perspective; a user should not have to know the genealogy of a particular utility in order to guess at some of its command-line arguments.
- thomasahle 10y agoBut is it really more inconsistent than UI interfaces? It feels like every graphical coding tool I use these days, have the menu in a different corner. Some requires me to use a web browser, others run in heavy virtual machines that take an hour to start up. Is's one thing to keep a consistant UI within your own application, but doing it across a hundred different ones is something I have still to see, in the graphical world as well as the text based.
- the8472 10y agoCLIs can be automated when you need to run things on a server. And CLIs are relatively cheap because calling main() and doing some stuff is just a few extra functions. Graphical tools usually need to hook more deeply into the software to extract the data and transform it into interactive UI components. Eclipse implemented their own java compiler they could instrument for syntax parsing so the IDE has total knowledge of the code for example. Many CLI tools are also non-interactive. Adding that interactivity adds complexity.
- blakeyrat 10y agoApple solved the "automating GUI applications" problem decades ago with AppleScript. But of course, this being the IT industry, everything old is forgotten and constantly re-invented as it goes in and out of vogue. > Graphical tools usually need to hook more deeply into the software I don't even know what that means, exactly. You mean they need more dependencies? > Many CLI tools are also non-interactive. Adding that interactivity adds complexity. Most things worth doing are difficult.
- wmccullough 10y ago> Most things worth doing are difficult Complexity does not mean that it's worth doing because it's difficult.
- blakeyrat 10y agoUh... huh? You lost me.
- EdiX 10y agoI tried using AppleScript a couple of times. One of the worst user experiences of my life. Zero documentation for the syntax and semantics of the language, almost no documentation for the library part, the documentation that existed was 7 years out of date (I was on leopard, the documentation still referenced OS 8) and even after those hurdles I was handcuffed to the sparse and poorly designed API that OS X programs had, that was put in as an afterthought. Calling that a "solution"...
- ArkyBeagle 10y agoThe culture that kept Smalltalk alive failed. So it goes. My understanding is that it had schisms. I've worked with Smalltalkers; they talked like conquered people. I PREFER - strongly - text-based because graphical based means some obscure binary protocol/file format that bitrots into obscurity. You can always learn to do hardcore text manipulation. You can't necessarily reverse-engineer, say, a Word 1.0 document. Text is the cockroach format.
- TeMPOraL 10y ago> Text is the cockroach format. I.e. ugly and hard to get rid of? ;). The problem with Unix isn't text - it's unstructured text. Every utility needs to implement its own copy of ad-hoc, bug-ridden parsers to operate on the same data - and if you want to string some of those utilities together, you often end up writing ad-hoc parsers too. The sad thing is that we knew how to work with structured text. Then the Unix came and ignored all that experience.
- unimpressive 10y ago>The sad thing is that we knew how to work with structured text. Which is?
- TeMPOraL 10y agoS-expressions for instance, which were popular back then. JSON is a modern reinvention of that particular wheel.
- thomasahle 10y agoYup, having more structure and types would be nice. However, that would require effort from all application writers, where as unstructured text is what they'd naturally output, and it works well enough for most things.
- ArkyBeagle 10y agoHere, let me show you my ASN.1 ... :) Or worse, my TL1. :)
- blakeyrat 10y agoAnother example, and one almost as old: HyperCard.
- madvoid 10y agoI'm slightly digressing, but I always thought it was interesting how the printed circuit board software Eagle was a combination of a graphical and text based tool. You can use the buttons like any other CAD program or you can enter commands into a limited command line. I like that UI but I've not seen other programs like it.
- tonyarkles 10y agoAnd you can turn those commands into scripts if you'd like with the ULP language. It's not necessarily pretty, but it's a straightforward way to automate repetitive tasks without requiring the authors of Eagle to figure out every possible use case. There's a lot of things that I dislike about Eagle, but I definitely miss those things when I'm using other CAD packages.
- zrail 10y agoAutodesk CAD has had a command line since the very beginning.
- Animats 10y agoWe were on DOS back then. Doing a GUI was hard. Compare Autodesk Inventor. No command line, and it doesn't need one. All the new Autodesk tools (Fusion, etc.) are based on Inventor. It's very hard to do a GUI for an elaborate 3D program, because you need to select multiple objects, talk to the GUI, and change the viewpoint, all within one operation. Yet it's been done successfully. Inventor doesn't even use hotkeys much; you can do almost everything with the mouse except enter numeric values.
- baddox 10y agoIt's pretty common in 3D modeling software. I've always liked how Rhino 3D integrates the command line with the GUI, allowing you to use pretty much any combination of the two for most functions. Here's a screencast showing some basic functionality: https://youtu.be/As0WUtBV3NQ?t=66 https://youtu.be/As0WUtBV3NQ?t=66
- gregw134 10y agoI think you'd like Apache Nifi. It has a drag and drop interface for building ingest and transformation pipelines. Everyone I've talked to that's used it says it makes them 10x more productive for ingest problems.
- jameshart 10y agoCuts both ways, of course. The expressiveness programmers enjoy by manipulating a directory-structure full of files using a syntax-highlighting text editor with autocompletions and a version control system to create a description of a complex set of interrelated entities, which they then process with toolchains to produce the real artifacts of their trade, is a powerful capability which for some reason we rarely try to offer to non programmers. With the right DSLs, almost anything could be 'programming'.
- jrapdx3 10y agoI completely agree with the idea of simple, flexible tools for interacting with programs and providing good tools for users. A while back I was putting together a DB query tool for volunteer staff to use. I deliberately made it simple and as unambiguous as I could within the limits of "simple". For example, allowing a free form search of principle database fields, I set up a very basic regular expression syntax, just substring match, and optionally '*', '+', '|', and '.'. This part of the interface is 3 text entry fields, with a nicely worded help message right next to the entries. In person, I showed the primary users how the interface worked and demoed the simplified regex. Months later there are sometimes still questions like "how do I find somebody named 'John Q. Smith'?" ("Just enter 'smi' and pick the name off the list of names sent back.") I don't mind going over it again, especially for someone new, but I think it shows it may be harder than we anticipate to introduce "programming-like" methods to typical users.
- lmm 10y agoIt's worth thinking about the reasons Unix beat Smalltalk. Interoperability is important. Being able to use the same tools on everything is important.