I could see an argument that Sway could do better to advertise that it is not for casual users.
If sway chooses to be a toy for basement nerds that is absolutely fine.
> However, it is designed for me: a professional, expert-level Linux user. I am under no illusions that it is suitable for my grandmother
I don't object to this level of user hostility since it is, after all, free software and he has no obligation to me. If he writes it just for himself thats absolutely fine. I'm not aggrieved.
I just found it a tad ironic that he is lecturing us on UX for grandmas given the level of user hostility his own software exhibited to experts.
(That is, assuming it's not a way out of date version or a debian bug or something that caused this - im trying to be generous here)
Maybe as a minimum it could have a display showing some sort of quickstart guide even if it was just 50 lines of text showing how to get a terminal and a browser and a link to more docs.
I pretty much only write software for expert consumption and I consider my software deficient without a quickstart. Onboarding matters.
>The most frustrating moments for a user is when the software they’re using does something inexplicable
Lol, speaking of... I tried installing sway a few weeks ago on ubuntu because I thought it sounded cool and because I still get somewhat nostalgic for ion.
It logged in to a blank screen with zero indication about what to do next. I guess it expected me to already have all of its keybindings memorized? Or maybe I was supposed to write a config file first? Was it a bug? Maybe I was supposed to already be an i3 user who knew what to do next?
I kind of expected it to do something.
I quickly lost interest.