-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dangerously user-friendly, yet no GUI? #3
Comments
Isn't double-clicking an application that requires no further configuration more user friendly than forcing the user to learn what configuration options mean? Seriously. QuickServ is designed to work on Windows and MacOS without the user ever touching the command line (though QuickServ will work fine from I did consider having a special route on the server to configure values within QuickServ from a graphical web interface, but in the end, the meager four command line configuration options didn't justify the added complexity to me. Hopefully this addresses your concern? I really do appreciate you bringing this up, and would be curious to hear your thoughts, given my perspective. |
Yes.
Surely you will add more features over time right? A GUI makes sense to me in that case. User-friendly to me means never having to touch a command line or edit any file by hand for any reason. |
seriously bruH? |
It is the easiest |
@gpetersson your point is well taken :) But actually, I don't really plan to add more features over time, which may help clarify my decision not to add a GUI. I'm a proponent of having "complete" or "finished" software in the sense that I'll continue to maintain it, but don't need to keep expanding it and letting features creep along. Maybe I'll add something if someone makes a suggestion I can't stop thinking about, or if I'm really in the mood, but it's not likely. I had fun building this, and I use it all the time, but I don't feel that it would benefit from more features at the moment. Hence the few command line arguments not justifying the complexity of a GUI. Note that the above is as much documentation of my current attitude for this project (that I can point to if this sort of thing comes up in the future) as it is a part of our discussion, so not everything in this reply is totally GUI-relevant. |
Seriously.
The text was updated successfully, but these errors were encountered: