simulo

»Should users give up complete control of their interaction with interfaces? Will users want to risk depending on “agents” that learn their likes and dislikes and act on a user’s behalf?« from November 1997, Interactions Magazine

Penpot took it from CSS.

Oh, good to know that it depends on locale, I always wondered about that behavior!

If you are interested in TypeScript for the browser, you might also like --erasableSyntaxOnly option of typescript >5.8. The only tool needed for it is the typescript compiler itself, so toolchain is kept to a minimum.

Bruno Latour’s "The Pasteurization of France" is about Louis Pasteur and the creation and success of germ theory. It does explain it not by focussing on Pasteur per se, but by showing how different groups of people adapted it for different goals.

> Not because I think it's helping him in the long run, but because it could help him feel better now.

Very much this: The long run is vague, and the only sure thing is that we will be dead. But this is a small thing one can do now.

These examples (dogs,cars...) are badly used in most programming books, but they can make sense if you show them in context of a small game or whatever else actually draws you an (inter) active virtual car or animal (which made OOP click for me, using processing). Printing "meow" and "woof" in the terminal, however, only makes sense as a demonstration if you already know what it should demonstrate.

That's a terrific track. Awesome intro riff, too.

For learning about the basics of statistics, my go-to resource is "Discovering Statistics using [R/SPSS]" (Andy Field). "Improving Your Statistical Inferences" (Daniel Lakens) needs some basics, but covers a lot of intesting topics, including sequencial testing and equivalence tests (sometimes you want to know if a new thing is equivalent to the old)

I second both resources!

No, afaic it does not.

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’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.

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.)

> Just send them an email from the contact link?

I guess – this is what I did.

that would be fitting, I thought the same.

That is sad. She was with the web from its early days (her first book on the subject is from 1996), taught a lot of people, and bridged several communities: design, web standards, and accessability

I vaguely remember even seeing Chrome distributed as bundleware.

I'm fascinated by the very mid-90s graphic design and typography.

> tries to deliver video heavy content

Video content seems not to be its main concern, but I can imagine that it is hard to scale if people want to use it to deliver video.

David Graeber on "Tyranny of Structurelessness": "[Many] completely misread Freeman’s essay, and interpret it not as a plea for formal mechanisms to ensure equality, but as a plea for more transparent hierarchy."

Yes, that section seemed to be a bit incoherent to me. However, it was only a brief comment, not even on data science rather but rather the strong confidence in a picking-the-winning version idea of design via A/B tests.

I agree with the "single people can create good software without involvement of a UX expert". That does not only apply to UX experts, but any other expert role (You do not even need a person who sees themselves as a programmer; a person using Excel, Access, Godot… might create something useful).

A lot of roles and best practices are for making software creation work in large organizations.

I disagree with the "dumbing down" idea: "old UX" (90s, early 2000s) focussed a lot on beginner-friendlieness and at this time a lot of people might have seen this sofware as being "dumbed down" from its predecessors. Menus e.g. are a staple of making GUIs more discoverable than command line interfaces, and at that time there were already criticism that urged for building more efficient text based interfaces (See "canon cat" and the "anti mac interface")