I guess mainly recreation and, particularly, teaching.

I read his "learning processing" many years ago. It was the book that made programming made sense to me. The explanations are excellent, the outcomes interesting and it helped me to see why object orientation makes sense after fruitless attempts of understanding it using examples of different types of cars that print "wrooom wroom" to the terminal.

I knew the linked-in-the-article https://lindeloev.github.io/tests-as-linear/ which is also great. A bit meta on the widespread use of linear models: "Transcending General Linear Reality" by Andrew Abbott, DOI:10.2307/202114

I read this article when I was in grad school 5 years ago. Absolutely love it and talk about it to this day.

It really makes me frustrated about the ways I was introduced to statistics: brute force memorization of seeming arbitrary formulas.

Here is the Python port of test-as-linear developed by George Ho (eigenfoo): https://github.com/minireference/tests-as-linear/blob/bugfix...

I'm linking to my fork of it because I've added some fixes and filled in some of the missing parts (e.g. Welch's t-test).

I’m pretty happy with kdenlive, too.

You could ask for feedback on https://discourse.opensourcedesign.net/ where quite some UX designers in open source projects hang out. I personally remember nokias flowella fondly, but I do not know if it does the same as wireflow.

Since some comments point out that the design looks old: I agree.

However, the framework’s author describes the usecase as building simple UIs for what otherwise would be used via the command line or for building UIs for cases when people can't or don’t want to learn a more complex framework (this could include HTML/CSS/JS, which is quite complex, if you do not know it yet!).

I also throught of ART as a fork of RawTherapee, also forked with the aim to make it easier to use.

I wondered if that is something hard to avoid: Over time features get added, usability worsens. This might be general, but it could apply to FOSS in particular, which often takes a modular approach (cue UNIX philosophy) and rarely includes structures where potentially useful features are rejected in order to keep the whole experience simple.

Yeah, I guess there's a point where starting afresh is beneficial to refocus. A bit different, but it's the same for institutions too. I know some countries have "sundowner" clauses on every institution, where they need to apply for a permit to continue operating every 10 years or so. Provides a good point to think "is this working and still serving its original purpose?".

Depends on perspective - graphic designers and typographers might find "Frutiger" to be the obvious part and wonder what "Aero" means.

Yes, I loved that, too. More abstract, also short, no pressure: Proteus.

This is very similar to what Grudin suggests in his HCI history "From tool to partner": Apple used to be very usability and research focussed in the 80s and early 90s, but turned away from it with Jobs and went more look-driven — and had great success with it. Other companies followed. (Which does not mean that companies ignored graphic design before, but it was the more utilitarian parts of graphic design that were important focussing on distinct shapes, readability etc.)

True but I don’t think this gets it quite right.

The big problem with classic Mac was the cooperative multitasking weird OS and the unstylish and clunky hardware. The UI needed polish and modernization but was not fundamentally bad.

The complete loss of OS coherence has a lot more to do with the web than anything else.