42 karma · joined April 8, 2016
OpenSSL can have this kind of UI. Its just a matter of understanding user requirements.
It's not my hobby anymore to spend time around this. I just use the app provided by my telecom provider to send SMS, i haven't configured an obscure TUI tool to interface my local 4G antenna to just tell my wife i'm well. Email is the same. Life is short hence the idea that using mutt is just a nerd hobby today. You can't advocate common mortal to go this way it's just outdated and overall ridiculous.
If its your hobby, well, i'm happy for you
Email today should be a no-brainer really. Its a hobby to configure mutt.
Not to speak about real life use case were the email is HTML formatted with images.
mutt, as far as i know is rooted to Unix local email handling. Which is not very friendly when used with common web providers 99% people use today
In 2022, I love linux and command line. But mutt is outside the limit i can tolerate about this dogma.
Please note i'm not bashing mutt, its a great peace of code
That's interesting i was not aware of this project. I'll take a further look asap. Is there some feature/comparison sheet with Kryoflux available ?
Kryoflux is great for that. https://www.kryoflux.com/?page=kf_features
Seems the opposite, first (short without sound) was on WGN around 9:15 pm and second (longer) on WTTW after eleven
Conventions are really important to speed up the basic usage understanding of a tool, both cli and gui applications. In my memory ESR did a good job at explaining cli applications Unix conventions (defaults arguments, configuration file locations etc.) in is book "The Art of Unix Programming".
But the complexity of a tool depends on the domain it covers and targeted users. In fact i disagree with the conclusions of the coffee machine analogy. One machine is for professional user the other not.
I disagree with the "no documentation" argument too. "Understand by intuition" paradigm works for basic scenarios from domains understund by anyone (music player, email) but it has its own limits when the software involves complex concepts sometimes inherent to the domain covered. In theses cases, a well written documentation is far more useful to understand theses concepts than clicking everywhere like a monkey ihmo.