Thought:

"Design" as practiced today by computer people tends to be heavily based on the idea of negative space: that good design is what's NOT in a system, and by extension, what is NOT ALLOWED TO BE ADDED to the system by a user.

A "design-heavy" system, then, is inevitably highly restrictive about user actions, lest they "ruin the cool design" by adding their own desired features that "make it messy".

But users WANT control over their own space.

Is there a "design" that empowers users?

@pnathan Sadly the CLI concept didn't extend even as far as the X Windowing System.

There may be a reason for that.

@natecull @pnathan What of stuff like Applescript?

(NB: I'm aware it exists. I've not used it myself and don't know its capabilities. A point which might factor into any possible response.)

@dredmorbius @natecull I would say the ergonomics of applescript are such that it's not full of use.

I didn't dink much with it because it didn't relate to the GUI paradigm that I worked in too well and I could already write bash etc by the time I encountered it.

@pnathan @natecull @dredmorbius hypercard was one of my early inroads to building software, so i used hypertalk some - similar vibes, i think?

hypercard was an amazing thing and i still miss aspects of it, but language-wise hypertalk suffered a lot from mistaken ideas about english-like ergonomics, i think.

@dredmorbius @natecull @pnathan
re: X, many (most?) of the linux desktop users i know use it to multiplex a bunch of terminals, and people tend to script things within the environment, so i'm not sure it's accurate that the cli didn't carry over.

@brennen @pnathan @dredmorbius

right, but that's not using X *as X* or to interact *with* CLI. It's using X just as a set of terminals for CLI that's completely unaware of X.

X, the system (as I understand it), does not use CLI. It sends and receives messages of its own devising and format but doesn't expose these to the user or use the CLI or pipe system to do it (except for some command options for programs which are mostly now ignored)

Tcl/tk, though, I think does use Unix pipes?

@natecull @dredmorbius @pnathan i mean, X is a windowing environment, so i dunno how using it to contain a bunch of windows isn't using it as that.

and yeah, X is a giant weird beast and i've never actually written code against it in any meaningful way, but i use stuff like xclip, wmctrl, dmenu, rofi, etc., to control facets of it pretty routinely, so it's at least situated in a cli & scripting-driven environment that i use to control my own space.

@brennen @pnathan @dredmorbius

Well, because X is about *graphical components* of which 'windows' are just one tiny, tiny subset

Like you might want your program to accept input from and send data to buttons? Grids? Charts? Images? Textboxes?

etc

None of that is even really possible with the 'a simulated VT-100 running just inside a window' use case of X.

So CLI is not interfacing with X 'as X', just X 'as a VT-100'.

@dredmorbius @pnathan @brennen all of that though is probably possible with Tcl/tk and maybe with some of the oldschool CLI tools you mention? (which really, really don't get much press at all even among hardcore Linux fans)

like to properly represent the state of X as CLI I think you'd need at least an object model? cos things on the screen ARE objects, they have persistence and state

Maybe all I want is a modern Tcl/tk that works with all the shiny GUI toolkits and OOP systems?

@natecull @pnathan @brennen NB: I'm massively hampered in all this discussion principally by /never having really grokked GUI application design in the first place/. My sense of "application" has always been "something that works on a stream of inputs or polls regularly for state", but not "and presents this with a bow and cherry on top".

I could use pointers on some good books on GUI UI/UX. Don Norman seems to be one source. Brett Victor another.

@dredmorbius @natecull @pnathan modulo a handful of toy projects and tiny utilities, every "GUI" i've ever built has lived inside a web browser, so i s'pose i'm in much the same boat.

@brennen @natecull @pnathan I ... have markedly better CSS chops than I care to discuss in polite, or impolite, society. No JS though. Yet.

@pnathan @natecull @brennen Virtually all of that picked up out of necessity trying to salvage my sanity and/or vision from the present state of HTML maldesign.

@dredmorbius @pnathan @brennen

It seems quite hard to think of how to encapsulate the IO flow and state of a GUI component.

ie the input stream could be a stream of events (mouse/keyboard or underlying widgets, data model) and a similar output stream... but it all seems a bit confused and intertwined compared to a simple script that reads a stream of records and writes a stream of updated records.

Could *maybe* separate the IO flow into 'channels' like 'standard output' and 'standard error'

@natecull @pnathan @brennen Interesting case in point: I've always found awk scripts far more intuitive than Excel spreadsheets. Even for simple stuff.

For sufficiently simple stuff, I write utilities that I'd otherwise use a spreadsheet for. E.g., summing a sequence, or generating univariate moments.

@dredmorbius @natecull @pnathan @brennen see, people are REALLY underestimating excel here

excel is a funcprog environment that

1., normal people use, and normal people use to great effect to get things done

2. actually offers a non-linear way to do programming; instead of a linear program, you operate on cells of a 2D space containing either data or formulae, and operating on ranges is easy

adding VBA was a terrible mistake that added complexity and inelegance

@calvin @natecull @pnathan @brennen I'm not contesting that Excel /isn't/ a functional programming environment.

I'm contesting that it's a /good/ FPE.

It is *VASTLY* too error-prone and difficult to debug. Not to mention awkward. OTOH, *it is often the only tool available since "real" programming tools are denied to front-office workers.*

(Including awk.)

Ray Panko, Univ. Hawaii, has studied Excel errors since the 1990s:
panko.shidler.hawaii.edu/SSR/M

@dredmorbius @calvin @pnathan @brennen

I suspect this is because spreadsheets don't offer *grouping* constructs, which are pretty important for humans to organise information.

A 2D grid gets you a long way, but not really far enough.

If you had a sort of web of nodes which you could expand or shrink, and had a natural mapping TO a 2D grid if you wanted it...

brennen
Follow

@natecull @pnathan @calvin @dredmorbius a spreadsheet is a shittier-than-average database with what is a better-than-average representation layer for a whole bunch of people to be able to grasp it.

the achilles heel is how bound the physical structure of the data is to the representation & interface, but maybe that's what makes it approachable. there has to be some way for a serious db to be as approachable as excel is, but i don't know what it'd be.

@brennen @natecull @pnathan @calvin And yes, the notion that Excel integrates data storage, data manipulation, and data output, is pretty key.

MS Access took that a slight level higher, though it also had a remarkable propensity to suddenly detonate and destroy entire city blocks, without warning.

Sign in to participate in the conversation
Mastodon

Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!